Cherry Servers Outage History

Cherry Servers had 9 outages in the last 2 years totaling 251h 30m of downtime — averaging 0.4 incidents per month.

There were 9 Cherry Servers outages since May 6, 2026 totaling 251h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cherryservers.com

Minor September 28, 2026

CH2 Lumen ISP issues

Detected by Pingoru: Sep 28, 2026, 08:13 AM UTC
Resolved: Sep 28, 2026, 08:38 AM UTC
Duration: 24m

Affected: NetworkInfrastructure (Chicago (US))

Timeline · 5 updates

identified Sep 28, 2026, 08:13 AM UTC

CH2 location lost one of its redundant ISP connections to Lumen. Other providers are taking over; some path changes may occur. Contacting Lumen and investigating the core issue. September 28, 2026 11:22 EEST
identified Sep 28, 2026, 08:13 AM UTC

CH2 location lost one of its redundant ISP connections to Lumen. Other providers are taking over; some path changes may occur. Contacting Lumen and investigating the core issue.
identified Sep 28, 2026, 08:22 AM UTC

Unreported maintenance event by Lumen. Gathering details on why Lumen did not inform us. September 28, 2026 11:38 EEST
identified Sep 28, 2026, 08:22 AM UTC

Unreported maintenance event by Lumen. Gathering details on why Lumen did not inform us.
resolved Sep 28, 2026, 08:38 AM UTC

Lumen link fully restored. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor September 22, 2026

Routing instability in module 6 in our Lithuanian DC

Detected by Pingoru: Sep 22, 2026, 12:25 PM UTC
Resolved: Sep 24, 2026, 10:44 AM UTC
Duration: 1d 22h

Affected: NetworkInfrastructure (Lithuania)

Timeline · 3 updates

identified Sep 22, 2026, 12:25 PM UTC

During the migration from old equipment, we have observed unexpected behaviour. Configuration is reverted. Clients, which are still experiencing issues, shold contact our support team, requests will be forwarded to our networking team. September 24, 2026 13:44 EEST
identified Sep 22, 2026, 12:25 PM UTC

During the migration from old equipment, we have observed unexpected behaviour. Configuration is reverted. Clients, which are still experiencing issues, shold contact our support team, requests will be forwarded to our networking team.
resolved Sep 24, 2026, 10:44 AM UTC

The issue has been located and resolved. However, maintenance work was not completed and will have to be rescheduled for a later date. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor August 8, 2026

Website is atttack

Detected by Pingoru: Aug 08, 2026, 08:37 AM UTC
Resolved: Aug 08, 2026, 09:45 AM UTC
Duration: 1h 7m

Affected: WebsiteAPI (Global)

Timeline · 3 updates

investigating Aug 08, 2026, 08:37 AM UTC

The website is being attacked to overload it. August 8, 2026 12:45 EEST
investigating Aug 08, 2026, 08:37 AM UTC

The website is being attacked to overload it.
resolved Aug 08, 2026, 09:45 AM UTC

The attack has been mitigated. All traffic is now flowing normally, and we're continuing to monitor for recurrence. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Major July 24, 2026

Portal and API return HTTP 404

Detected by Pingoru: Jul 24, 2026, 04:56 PM UTC
Resolved: Jul 24, 2026, 05:12 PM UTC
Duration: 15m

Affected: Customer PortalAPIAPI (Global)

Timeline · 3 updates

investigating Jul 24, 2026, 04:56 PM UTC

Both portal and API return HTTP error 404. July 24, 2026 20:12 EEST
investigating Jul 24, 2026, 04:56 PM UTC

Both portal and API return HTTP error 404.
resolved Jul 24, 2026, 05:12 PM UTC

Resolved by upgrading involved load balancers. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Major July 22, 2026

Some servers in Module 2 are experiencing issues

Detected by Pingoru: Jul 22, 2026, 04:54 PM UTC
Resolved: Jul 23, 2026, 03:57 AM UTC
Duration: 11h 2m

Affected: InfrastructureInfrastructure (Lithuania)

Timeline · 3 updates

investigating Jul 22, 2026, 04:54 PM UTC

Servers in module 1 and 2 ran on UPS power at the following intervals: 5:15 - 5:26 UTC 9:43 - 9:47 UTC 11:00 - 11:09 UTC No servers in the segment lost power. Some servers in module 2 were affected. Our primary suspect for some servers experiencing issues at this point is old server/PSU hardware. July 23, 2026 06:57 EEST
investigating Jul 22, 2026, 04:54 PM UTC

Servers in module 1 and 2 ran on UPS power at the following intervals: 5:15 - 5:26 UTC 9:43 - 9:47 UTC 11:00 - 11:09 UTC No servers in the segment lost power. Some servers in module 2 were affected. Our primary suspect for some servers experiencing issues at this point is old server/PSU hardware.
resolved Jul 23, 2026, 03:57 AM UTC

We believe that all affected servers with faulty PSU's have been addressed. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor June 10, 2026

ISP pathways issue

Detected by Pingoru: Jun 10, 2026, 05:11 PM UTC
Resolved: Jun 11, 2026, 05:59 AM UTC
Duration: 12h 47m

Affected: NetworkInfrastructure (Singapore)

Timeline · 3 updates

monitoring Jun 10, 2026, 05:11 PM UTC

We noticed an outgoing pathways issue with one of our Singapore ISP providers. We migrated traffic to a different provider. Currently, we are monitoring the situation. June 11, 2026 08:59 EEST
monitoring Jun 10, 2026, 05:11 PM UTC

We noticed an outgoing pathways issue with one of our Singapore ISP providers. We migrated traffic to a different provider. Currently, we are monitoring the situation.
resolved Jun 11, 2026, 05:59 AM UTC

The situation with the ISP is resolved. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor May 23, 2026

AM4 rack 15 secondary access switch member issues

Detected by Pingoru: May 23, 2026, 07:55 AM UTC
Resolved: May 28, 2026, 04:56 PM UTC
Duration: 5d 9h

Affected: NetworkInfrastructure (Amsterdam (NL))

Timeline · 3 updates

identified May 23, 2026, 07:55 AM UTC

In rack 15 of AM4 location, one of the redundant access switches failed. Server networking should be operating through the remaining access switch normally. Steps to restore full redundancy are being taken. Affected server customers will be contacted via email. May 28, 2026 19:56 EEST
identified May 23, 2026, 07:55 AM UTC

In rack 15 of AM4 location, one of the redundant access switches failed. Server networking should be operating through the remaining access switch normally. Steps to restore full redundancy are being taken. Affected server customers will be contacted via email.
resolved May 28, 2026, 04:56 PM UTC

Redundancy has been restored Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor May 12, 2026

Access switch failure, Amsterdam Rack 2

Detected by Pingoru: May 12, 2026, 12:33 PM UTC
Resolved: May 14, 2026, 01:58 PM UTC
Duration: 2d 1h

Affected: InfrastructureInfrastructure (Amsterdam (NL))

Timeline · 3 updates

monitoring May 12, 2026, 12:33 PM UTC

Full location: Amsterdam DC, Rack 2. One segment of NL location DC an access switch failed. The switch is redundant, meaning that minimal to no issues are felt. May 14, 2026 16:58 EEST
monitoring May 12, 2026, 12:33 PM UTC

Full location: Amsterdam DC, Rack 2. One segment of NL location DC an access switch failed. The switch is redundant, meaning that minimal to no issues are felt.
resolved May 14, 2026, 01:58 PM UTC

After replacement of stack-unit and extensive monitoring, full redundancy has been restored. Back to current status Status History Report Issue Powered by Status.io Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates via RSS RSS Feed Close

Read the full incident report →

Minor May 6, 2026

ISP issues with one of our providers

Detected by Pingoru: May 06, 2026, 12:21 PM UTC
Resolved: May 06, 2026, 01:31 PM UTC
Duration: 1h 9m

Affected: NetworkInfrastructure (Lithuania)

Timeline · 1 update

identified May 06, 2026, 12:21 PM UTC

One of the core redundant ISPs lost its connection in LT location. We are communicating with the ISP to resolve the issue. The remaining ISP backbones are fully handling all of the traffic, so no immediate routing issues should be visible. Some pathways may have changed.

Read the full incident report →