Servers.com incident

Network connectivity issues

Minor Resolved View vendor source →

Servers.com experienced a minor incident on September 12, 2026 affecting Public network and Cloud servers and 1 more component, lasting 53m. The incident has been resolved; the full update timeline is below.

Started
Sep 12, 2026, 09:14 PM UTC
Resolved
Sep 12, 2026, 10:08 PM UTC
Duration
53m
Detected by Pingoru
Sep 12, 2026, 09:14 PM UTC

Affected components

Public networkCloud serversCloud servers (San Jose)Cooling system (SJC1)Cooling system (SJC2)Cooling system (SJC3)

Update timeline

  1. investigating Sep 12, 2026, 09:14 PM UTC

    We have detected network issues in the listed locations. Customers may observe RTT deviations and packet loss on this direction. Our engineers are carrying out diagnostics and emergency maintenance works. To help us figure out the sources of the issue, send your diagnostic data with the following information: 1. Your current source IP address. 2. Your destination IP address. 3. Output of the traceroute / ping / mtr utility from the location where there are delays to your server. Read more information here: https://www.servers.com/knowledge/linux-administration/how-to-provide-the-technical-support-team-with-network-diagnostic-results 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

  2. investigating Sep 12, 2026, 09:14 PM UTC

    We have detected network issues in the listed locations. Customers may observe RTT deviations and packet loss on this direction. Our engineers are carrying out diagnostics and emergency maintenance works. To help us figure out the sources of the issue, send your diagnostic data with the following information: 1. Your current source IP address. 2. Your destination IP address. 3. Output of the traceroute / ping / mtr utility from the location where there are delays to your server. Read more information here: https://www.servers.com/knowledge/linux-administration/how-to-provide-the-technical-support-team-with-network-diagnostic-results We will update the status as soon as we get any new information.

  3. resolved Sep 12, 2026, 10:08 PM UTC

    Our engineering team has resolved the issue with network connectivity. All systems are operating normally now. If you have any questions, please submit a request to our support team. We apologize for any inconvenience.