Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article4 min readViews1

Timeweb Cloud Reports Service Restoration: What to Check After the Outage

The provider published the cause of the November 17 network outage and the downtime interval. We analyze the restoration process and how to safely verify your site, orders, and integrations.

Comments 0

A disconnected network cable lies next to an empty port on a metal device.
In this article

On November 17, Timeweb Cloud published an analysis of the network outage: according to the company, part of the cloud services were unavailable from 13:18 to 15:05 MSK. The provider reported that all services were restored within the scope of this incident. A restoration notice does not replace verification of a specific project: the site owner should check their service and zone, and then verify the actual operation of the site and integrations.

Which Services Were Affected

In initial incident reports, the provider named St. Petersburg, Moscow, Germany, the Netherlands, and Kazakhstan; in the subsequent analysis, it clarified that all locations were affected except Novosibirsk. During verification, the official status page showed availability for cloud servers, cloud databases, Kubernetes, App Platform, and load balancers in all zones listed for these services. However, in the Networks section, the Moscow zone msk-1 retained a partial unavailability marker. The connection between this specific marker and the closed incident is not explained in the read message—check the status of the required service and zone separately.

Dedicated servers, domains, SSL certificates, and corporate email were also marked as available on the verified status page. Do not automatically propagate a previous outage or a recovery notice to all services and every client project: you must verify the actual availability of your own system.

A site may depend on an incident indirectly: for example, if its application accesses a database hosted in the affected cloud or an external API. The mere presence of a VPS with another provider does not prove either a dependency on Timeweb Cloud or the absence of such a dependency.

What a site owner should check

  • Clarify with the administrator where the server, database, and critical external integrations are running. Match the service and zone against the official status page.
  • Record the time and nature of errors to correlate them with provider messages and support tickets. Do not publish logs containing passwords, tokens, or customer data.
  • Avoid mass reinstallation and hasty DNS changes. Switching makes sense only if a backup is already prepared and verified, including data currency.
  • After connectivity is restored, check site loading, database connections, order placement, exchange queues, and notification delivery. Before retrying order creation or a payment request, determine the result of the previous operation: a retry may create a duplicate.

This is a safe benchmark for verifying your own project, not a report on testing the provider's infrastructure. The availability of a status page or control panel alone does not confirm that every website, database, and scheduled task is functioning correctly.

Why the failure occurred and what remains to be checked

According to the company's analysis, the failure occurred during an update of the hypervisor network stack to enhance infrastructure security. The dynamic routing service did not restart completely: the hypervisors failed to re-advertise routes to the network equipment, causing some servers to lose network connectivity. However, the virtual servers themselves continued to operate. A full restart of the network stack restored routing. The provider plans to expand checks of individual routing service components, increase intervals between update stages, and accelerate recovery of the network stack in similar failures. These are the stated next steps, not confirmation of their completion. The number of affected clients is not specified in the analysis. The continued operation of virtual servers alone does not prove the absence of data loss or the successful execution of every order, payment, or scheduled task; the message also does not allow a conclusion about a breach.

Information verified on November 17, 2026, at 18:03 MSK. Status may change; current limitations and further updates should be verified with the provider.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.