Beget is down: what happened on November 2 and what to do with your site, VPS and files

Beget has been down since the night of November 2, 2026. According to the hosting provider itself, it was attacked: the attackers gained access to the infrastructure management system and wiped the servers. Beget promises to bring back sites on shared hosting, but says the data on cloud VPS and in S3 storage has been lost.

We were among those affected. Beget hosted the server of our WazzaBee service, our customers' files, the images and videos for our blog, and about 50 other sites that we built and maintain. Below is a breakdown based on Beget's official statements: what happened, what will be restored, what has been lost, what to do right now and how we moved in a single day.

What happened to Beget on November 2, 2026?

According to Beget, the hosting provider was attacked: the attackers got into the infrastructure control plane and ran scripts that wiped the servers. Beget declared force majeure and is restoring the servers manually.

Timeline from Beget's official Telegram channel, Moscow time:

• 01:50. The provider reported a major incident and said all resources had been put on fixing it.
• 03:03. Status changed to "recovery and investigation".
• 05:23. Beget admitted the problem was complex and affected every level of the architecture. Engineers were bringing the infrastructure back up by hand in the data centers.
• 12:15–12:43. A detailed explanation and an official force majeure notice. The provider gave no exact date for full recovery.
• 14:40 and 19:17. DNS management came back through a separate address, domains.beget.ru, first for domains registered with Beget, then for all domains served through the hosting.
• 22:01. Shared hosting servers started coming back. Each server is booted from a separate disk, cleaned of malicious code and checked for data integrity, and only then are the sites switched on.

What will Beget restore and what is lost?

What happens to your data depends on the service you used. Here is what the provider itself says:

Beget service	Status according to the provider
Shared hosting	almost all sites can be restored, servers are checked manually, no dates given
Dedicated servers not managed by Beget	restored on November 2
VPS	binary backups lost, file backups preserved
Cloud: VPS, S3, Kubernetes	data lost, CDN and IP settings too
DNS	servers are working, A, MX and TXT records can be changed via domains.beget.ru
Email	about 80% restored by midday on November 2, the rest promised within 10 hours
Control panel	a limited version promised within 24 hours

In short: if you had regular shared hosting, you will most likely get your site back, but nobody knows when. If you had a cloud VPS or files in S3, do not count on Beget to restore them.

Why is my site on Beget still not opening?

The provider is checking more than a thousand servers by hand, and each one waits its turn. Until your server has been checked, your site will not open, even if the domain and DNS already work.

The second common reason: the site files are in place, but images and videos were loaded from S3 cloud storage. The site opens, but without images. That is exactly what happened to us: our blog post covers and videos were stored in Beget S3 and disappeared along with it.

What should you do if your site was on Beget?

1. Change all passwords and keys. Beget itself recommends changing passwords, access keys and any credentials stored on the servers: database access, API keys, admin panel passwords. Since the attackers were inside, assume this data may have leaked.
2. Check where your copies are. The hosting provider's own backup can disappear along with the servers in an outage like this. Look for your own: on your computer, in your code repository, in your developer's archives, in your designer's working folders.
3. Do not wait if the site makes money. Every day of downtime costs money. Bring the site up on another server from your own copy and switch DNS. When Beget is back, you can take whatever is missing from there.
4. Switch DNS. If your domain points to Beget NS servers, A records are changed via domains.beget.ru, and the confirmation code is sent to the domain administrator's email. If the domain is with another registrar, change the records there.
5. Check your domain email. If your email was hosted on Beget, check the MX records. While email is down, messages from your customers may not arrive.
6. Make a list of what is lost. Images, videos, customer files. With a list it is easier to look for copies and see what will have to be reshot or redrawn.

How did WazzaBee move away from Beget in one day?

We did not wait for the recovery: the provider's first statements made it clear that nobody would name a date. Here is what we did, step by step.

• A new server in Kazakhstan. We took a VPS from the Kazakhstan hosting provider 1host.kz. Our service code is in a repository and the server settings were documented, so we brought everything up from our own copies, not from the hosting provider's backup.
• File storage. We switched customer files to S3 at the same 1host. On the very first day, 1host support enabled public read access to our bucket so that file links would work again.
• DNS. Our domain is with a separate registrar, so we changed the A records in a few minutes, without waiting for the Beget panel.
• CRM integrations. The amoCRM servers kept the old address in their cache. We worked it out with amoCRM support, and they switched the channel to the direct address of our server, so outgoing messages started flowing again the same day.
• Images and videos. What disappeared with Beget S3 we restored from our own working archives: video sources, projects and mockups. Post covers we could not find were redrawn and uploaded to the same addresses so that old links open again.

The main takeaway: what saved us was not the hosting provider's backups but the copies we kept ourselves.

Compensation for WazzaBee customers

While we were moving, some features worked intermittently. As compensation, we added 7 days of subscription to all our customers. You do not need to do anything, the days have already been added.

How to avoid an outage like this next time?

• Keep copies separate from your hosting. A copy on the same hosting will disappear along with it. You need a second one: on another server, in another company's cloud, on your own drive.
• Keep your code in a repository. If your site code is in Git, a new server can be brought up in hours, not weeks.
• Keep your domain with a separate registrar. Then DNS does not depend on your hosting, and you can switch in minutes.
• Write down your server settings. Web server configs, software versions, scheduled jobs. Without them, a move turns into guesswork.
• Test your copies. Once a month, try to deploy the site from a copy. A copy you have never restored from may turn out to be empty.

Where to get a reliable server in Kazakhstan?

We moved to 1host.kz and are happy so far: the servers are in Kazakhstan, support is answered by real people and helped us with the move on the very first day. If you also need a server in Kazakhstan, you can get one here (this is our affiliate link): 1host.kz.

How can WazzaBee help your business?

WazzaBee is a service for businesses that sell through messengers. We work in Kazakhstan, the CIS, Georgia and Turkey.

• Official WhatsApp Business API. Connection takes 15 minutes. One number for all your agents and template broadcasts.
• WhatsApp in Bitrix24 and amoCRM. Conversations with customers go straight into the deal card, and agents reply from the CRM. If you are still choosing, read what amoCRM is and what Bitrix24 is.
• WhatsApp calls. You can call customers and take calls in the dashboard chats, Bitrix24 and amoCRM.
• WazzaBee's own CRM. Pipeline, customer cards and conversations in one window, if you do not need Bitrix24 or amoCRM.
• Menu bots and auto-replies. The bot answers at night and on weekends, collects the request and passes it to an agent.

Outage details are taken from Beget's official Telegram channel as of November 4, 2026. If the provider updates its information, rely on its latest statements.