Servers.com experienced a critical incident on June 29, 2026 affecting Public network and Cooling system (MIA1), lasting 13d 12h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 29, 2026, 09:45 PM UTC
We have detected a failure at one of the public network core routers. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. Our engineers are carrying out diagnostics and emergency recovery works. We don't expect any downtime. We will update the status as soon as we get any new information. Back to current status Status History Subscribe to receive status updates via RSS RSS Feed Close Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription Servers.com by Nexcess | Privacy | Legal
- investigating Jun 29, 2026, 09:45 PM UTC
We have detected a failure at one of the public network core routers. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. Our engineers are carrying out diagnostics and emergency recovery works. We don't expect any downtime. We will update the status as soon as we get any new information.
- investigating Jul 09, 2026, 08:44 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 19:44 (UTC) . Customers could have observe RTT deviations and packet loss on this direction. At 19:53 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- investigating Jul 09, 2026, 08:44 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 19:44 (UTC) . Customers could have observe RTT deviations and packet loss on this direction. At 19:53 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- investigating Jul 10, 2026, 01:26 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 12:09 (UTC) . Customers could have observe packet loss on this direction. At 12:36 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- investigating Jul 10, 2026, 01:26 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 15:09 (UTC) . Customers could have observe packet loss on this direction. At 15:36 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- investigating Jul 10, 2026, 01:50 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 13:31 (UTC) . Customers could have observe packet loss on this direction. At 13:32 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- investigating Jul 10, 2026, 01:50 PM UTC
During recovery works, we have detected a failure at the network core router in the listed location at 13:31 (UTC) . Customers could have observe packet loss on this direction. At 13:32 (UTC), our engineers have fixed the issue. All customer servers are available via the public and private network, but redundancy has been temporarily lost at some segments of our network. We will update the status as soon as we get any new information.
- resolved Jul 13, 2026, 09:50 AM UTC
The public network core router is operating normally and network redundancy has been restored. If you have any questions, please submit a request to our support team or contact us via chat on Servers.com website. We apologize for any inconvenience.