Servers.com Outage History

Servers.com is up right now

Servers.com had 3 outages in the last 2 years totaling 18h 12m of downtime — averaging 0.1 incidents per month.

There were 3 Servers.com outages since May 5, 2026 totaling 18h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status-servers.com

Minor June 11, 2026

Power issues in our datacenter

Detected by Pingoru
Jun 11, 2026, 07:35 PM UTC
Resolved
Jun 11, 2026, 10:51 PM UTC
Duration
3h 15m
Affected: Power systemCooling system (SJC3)
Timeline · 3 updates
  1. investigating Jun 11, 2026, 07:35 PM UTC

    The datacenter has detected a power feed issue in the listed location. The equipment in the racks has been transferred to generator power. Currently, datacenter engineers are diagnosing the source of the issue. We will update the status as soon as we get more 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 Jun 11, 2026, 07:35 PM UTC

    The datacenter has detected a power feed issue in the listed location. The equipment in the racks has been transferred to generator power. Currently, datacenter engineers are diagnosing the source of the issue. We will update the status as soon as we get more information.

  3. resolved Jun 11, 2026, 10:51 PM UTC

    All systems are operating normally now. If you have any questions, please submit a request to our support team. We apologize for any inconvenience.

Read the full incident report →

Minor June 2, 2026

iDRAC VPN issues

Detected by Pingoru
Jun 02, 2026, 02:01 AM UTC
Resolved
Jun 02, 2026, 03:34 AM UTC
Duration
1h 32m
Affected: VPN to DRACCooling system (AMS1)
Timeline · 3 updates
  1. investigating Jun 02, 2026, 02:01 AM UTC

    We have detected temporary issues with our iDRAC VPN service in the listed location. Currently, our engineers are diagnosing the source of the issue. We will update the status as soon as we get more 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 Jun 02, 2026, 02:01 AM UTC

    We have detected temporary issues with our iDRAC VPN service in the listed location. Currently, our engineers are diagnosing the source of the issue. We will update the status as soon as we get more information.

  3. resolved Jun 02, 2026, 03:34 AM UTC

    The operation of the DRAC VPN service in the listed location 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.

Read the full incident report →

Major May 5, 2026

Cooling issues in our datacenter

Detected by Pingoru
May 05, 2026, 12:42 PM UTC
Resolved
May 06, 2026, 02:07 AM UTC
Duration
13h 24m
Affected: Cooling systemCooling system (LUX1)Cooling system (LUX2)
Timeline · 4 updates
  1. investigating May 05, 2026, 12:42 PM UTC

    We have registered an issue with the cooling system in the listed location. Customers may observe alerts about overheating in the iDRAC of the servers . The issue also caused the total shutdown of some equipment. Currently, our engineers are diagnosing the source of the issue. We will update the status as soon as we get more information.

  2. identified May 05, 2026, 02:53 PM UTC

    We are actively working on resolving the issue and mitigating the negative impact. Please note that servers management via the customer portal and OpenStack API is currently unavailable for LUX1 location. Some affected equipment is already available. Please also note that LUX2 location was not affected. Please accept our apologies for the incorrect information. We will update the status as soon as we get more information.

  3. identified May 05, 2026, 05:48 PM UTC

    At 12:34 (UTC), the normal operation of the cooling system was restored. We are actively working on resolving the issues related to the affected network equipment. Please note that server management via the customer portal and OpenStack API is restored for the LUX1 location. Most of the affected network equipment is already available. We will update the status as soon as we get more information.

  4. monitoring May 06, 2026, 12:00 AM UTC

    We restored the network equipment on 5 May, at 23:42 (UTC). We will update the status as soon as we check that the equipment is working correctly.

Read the full incident report →