Cherryservers Outage History

32 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Cherryservers status100.00% uptime history

Every Recorded Cherryservers Incident

Cherryservers incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 5, 2026Access switch uplnk migration to upgraded hardware in our Lithuanian DC: Scheduled Maintenance3h 0mScheduled
Nov 4, 2026Access switch upgrade LT Module 6 Rack43Scheduled Maintenance1h 0mScheduled
Nov 4, 2026Routing change for server segment in our Lithuanian DC: Scheduled Maintenance3h 0mScheduled
Nov 3, 2026Access switch uplnk migration to upgraded hardware in our Lithuanian DC:Scheduled Maintenance3h 0mScheduled
Nov 2, 2026Routing change for server segment in our Lithuanian DC: Scheduled Maintenance3h 0mScheduled
Oct 21, 2026Mitigation of Critical PHP VulnerabilitiesScheduled Maintenance6h 0mScheduled
Oct 3, 2026LT rack 111XX access switch issuesA single rack access switch appears to be experiencing hardware issues. Servers connected to this switch may experience network loss. Investigating.268h 1mResolved
Oct 1, 2026Upstream Provider MaintenanceScheduled Maintenance2h 0mScheduled
Sep 28, 2026CH2 Lumen ISP issuesCH2 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.25 minResolved
Sep 28, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 28, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 22, 2026Routing instability in module 6 in our Lithuanian DCDuring 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…46h 18mResolved
Sep 22, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 22, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 22, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 22, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance3h 0mScheduled
Sep 21, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance1h 0mScheduled
Sep 21, 2026Planned router upgrade in our Lithuanian DC.Scheduled Maintenance3h 0mScheduled
Sep 10, 2026Emergency network segment throughput upgrade.Scheduled Maintenance1h 0mScheduled
Sep 10, 2026Emergency network segment throughput upgrade.Scheduled Maintenance1h 0mScheduled
Sep 10, 2026Access switch upgrade AM4 Rack1Scheduled Maintenance1h 0mScheduled
Sep 9, 2026Access switch upgrade AM4 Rack2Scheduled Maintenance1h 0mScheduled
Sep 9, 2026Access switch upgrade AM4 Rack3Scheduled Maintenance1h 0mScheduled
Sep 9, 2026Access switch upgrade AM4 Rack4Scheduled Maintenance1h 0mScheduled
Sep 8, 2026Access switch upgrade AM4 Rack5Scheduled Maintenance1h 0mScheduled
Sep 8, 2026Access switch upgrade AM4 Rack6Scheduled Maintenance1h 0mScheduled
Sep 8, 2026Access switch upgrade AM4 Rack7Scheduled Maintenance1h 0mScheduled
Aug 26, 2026ERP infrastructure maintenanceScheduled Maintenance1h 0mScheduled
Aug 18, 2026Network backbone capacity upgradeScheduled Maintenance1h 0mScheduled
Aug 14, 2026Access switch upgrade LT Module 6 Rack45Scheduled Maintenance1h 0mScheduled
Aug 13, 2026Access switch upgrade LT Module 1 Rack 171Scheduled Maintenance1h 0mScheduled
Aug 12, 2026Access switch upgrade LT Module 1 Rack 176Scheduled Maintenance1h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Cherryservers incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Cherryservers Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Cherryservers acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Cherryservers outage in this window ran 11d 4h, against a mean recovery of 11h 18m. If you depend on Cherryservers in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.