Incidents | Serverside.com Incidents reported on status page for Serverside.com https://status.serverside.com/ https://d1lppblt9t2x15.cloudfront.net/logos/3f124c5348be83cb59f015420543bb3b.png Incidents | Serverside.com https://status.serverside.com/ en Chicago (Netrality CH1) recovered https://status.serverside.com/ Mon, 01 Dec 2025 15:05:55 +0000 https://status.serverside.com/#112a496c31468e91cd2513c50c46988f5325b6099ba85e10f8dce087527474ab Chicago (Netrality CH1) recovered Chicago (Netrality CH1) went down https://status.serverside.com/ Mon, 01 Dec 2025 15:04:34 +0000 https://status.serverside.com/#112a496c31468e91cd2513c50c46988f5325b6099ba85e10f8dce087527474ab Chicago (Netrality CH1) went down Serverside.com Public API recovered https://status.serverside.com/ Tue, 25 Nov 2025 03:47:51 +0000 https://status.serverside.com/#b839d6af2cd8f73c95a3a3374863ea0ca1a0b5f7193e4fd89f160c920e35a8eb Serverside.com Public API recovered Serverside.com Public API went down https://status.serverside.com/ Tue, 25 Nov 2025 03:45:51 +0000 https://status.serverside.com/#b839d6af2cd8f73c95a3a3374863ea0ca1a0b5f7193e4fd89f160c920e35a8eb Serverside.com Public API went down Amsterdam (Digital Realty AMS3) recovered https://status.serverside.com/ Tue, 18 Nov 2025 16:16:42 +0000 https://status.serverside.com/#b1bb4a57d89780c2e8b2ce10603ec919a1f7bd87fd2da67d2d36e7b65810768b Amsterdam (Digital Realty AMS3) recovered Amsterdam (Digital Realty AMS3) went down https://status.serverside.com/ Tue, 18 Nov 2025 16:11:17 +0000 https://status.serverside.com/#b1bb4a57d89780c2e8b2ce10603ec919a1f7bd87fd2da67d2d36e7b65810768b Amsterdam (Digital Realty AMS3) went down Billing Area (billing.serverside.com) recovered https://status.serverside.com/ Tue, 18 Nov 2025 12:00:37 +0000 https://status.serverside.com/#65497ce74f3a40794ededd25cd8ac5daffbdbafb49d508e622da374aea412184 Billing Area (billing.serverside.com) recovered Billing Area (billing.serverside.com) went down https://status.serverside.com/ Tue, 18 Nov 2025 11:41:10 +0000 https://status.serverside.com/#65497ce74f3a40794ededd25cd8ac5daffbdbafb49d508e622da374aea412184 Billing Area (billing.serverside.com) went down Serverside.com Public API recovered https://status.serverside.com/ Fri, 31 Oct 2025 22:43:33 +0000 https://status.serverside.com/#54072fb47409806a1bd3ef90a4d5fcd98df4fa920f04e3a24124182ab8ed03fb Serverside.com Public API recovered Serverside.com Public API went down https://status.serverside.com/ Fri, 31 Oct 2025 22:33:31 +0000 https://status.serverside.com/#54072fb47409806a1bd3ef90a4d5fcd98df4fa920f04e3a24124182ab8ed03fb Serverside.com Public API went down Los Angeles (Digital Realty LAX10) recovered https://status.serverside.com/ Fri, 17 Oct 2025 07:42:45 +0000 https://status.serverside.com/#d263e69982cb2451c1ea5449470b9cd6af598e1df3f24bca2b6b490a3c204a0c Los Angeles (Digital Realty LAX10) recovered Los Angeles (Digital Realty LAX10) went down https://status.serverside.com/ Fri, 17 Oct 2025 07:39:02 +0000 https://status.serverside.com/#d263e69982cb2451c1ea5449470b9cd6af598e1df3f24bca2b6b490a3c204a0c Los Angeles (Digital Realty LAX10) went down Los Angeles (Digital Realty LAX10) recovered https://status.serverside.com/ Thu, 25 Sep 2025 20:19:55 +0000 https://status.serverside.com/#764dba33e6229c76186e499cc51a33de06bb61729e42480ec2045628dab0e7a4 Los Angeles (Digital Realty LAX10) recovered Los Angeles (Digital Realty LAX10) went down https://status.serverside.com/ Thu, 25 Sep 2025 20:18:13 +0000 https://status.serverside.com/#764dba33e6229c76186e499cc51a33de06bb61729e42480ec2045628dab0e7a4 Los Angeles (Digital Realty LAX10) went down Amsterdam (Digital Realty AMS3) recovered https://status.serverside.com/ Tue, 23 Sep 2025 09:10:30 +0000 https://status.serverside.com/#dfe8465bae309324e6d7e64b82323a050128158fb113ff08bd2f8d78dc571eb7 Amsterdam (Digital Realty AMS3) recovered Amsterdam (Digital Realty AMS3) went down https://status.serverside.com/ Tue, 23 Sep 2025 09:03:11 +0000 https://status.serverside.com/#dfe8465bae309324e6d7e64b82323a050128158fb113ff08bd2f8d78dc571eb7 Amsterdam (Digital Realty AMS3) went down EWR20 IP Transit Maintenance https://status.serverside.com/incident/623876 Wed, 23 Jul 2025 11:00:15 -0000 https://status.serverside.com/incident/623876#f98c4dd6a397da12265b2d6c0a04c3231a10c58bccbcbbd36eedd542f8e5e1d4 Maintenance completed EWR20 IP Transit Maintenance https://status.serverside.com/incident/623876 Wed, 23 Jul 2025 03:00:15 -0000 https://status.serverside.com/incident/623876#a00310a4fdda4a2412cffa675b327cf4b9137c0fc9b3ee4a2b458ff46e72770e One of our tier 1 IP transit providers will be performing circuit maintenance in our EWR20 location. To prevent impact, we will be temporarily disabling this provider in our transit blend. Route reconvergence is expected before and after the maintenance window, but we anticipate no impact otherwise. Provider maintenance window: Start time: 07/23/25 at 00:01 - America/New_York (04:01 UTC) End time: 07/23/25 at 06:00 - America/New_York (10:00 UTC) We will place the circuit in maintenance at approximately 11:00 PM EDT this evening, and re-enable before 7:00 AM EDT Wednesday morning. CH1 Connectivity Incident https://status.serverside.com/incident/551295 Fri, 25 Apr 2025 05:27:00 -0000 https://status.serverside.com/incident/551295#6d25e30a8bde9b4825cbe35b3753cb443cf5f74d65162d208e52cf6ff61fe171 Power has been restored to the facility’s “A” side. We will follow up with a post mortem and additional information once we receive further information from the facility. CH1 Connectivity Incident https://status.serverside.com/incident/551295 Fri, 25 Apr 2025 04:08:00 -0000 https://status.serverside.com/incident/551295#6826ec82ef5e888e515ef8063d6bac1c8a57bc6bca491d0f506c240ee8638112 From approximately 9:30 PM to 10:30 PM local time in Chicago, we experienced a period of intermittent network interruption. The root cause of this incident stems from a full loss of power on one feed in our Chicago datacenter. While our equipment is connected redundantly, this power loss event unfortunately sent a critical network device into a reinitialization loop. This resulted in the intermittent loss of connectivity to our core network in Chicago. Corrective actions are being implemented to prevent a recurrence, but a fix has been implemented immediately to ensure no further disruption to connectivity. In the meantime, the facility continues to suffer from this event, which has to do with a UPS failure. Electricians and site engineers are on-site and working to resolve the outage. This incident will be updated once the facility has restored power on the "A" side which is currently offline.