We started checking Civo on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Civo reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Civo's own status page declared. Below it, any public chatter we saw about Civo and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Civo's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Civo in the last 24 hours, which is not evidence that nothing is wrong.
Civo's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Civo's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Civo next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
584
US-West
99.78%
457
Europe
100.00%
413
Asia-Pacific
100.00%
250
Their declared record
Civo's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Scheduled Maintenance — Public Ingress (LON1, FRA1, NYC1, MUM1)Maintenance
Nov 5, 2026, 6:00 AM UTC to Nov 5, 2026, 4:44 PM UTC (10h 44m)completed
their latest update (Nov 5, 2026, 4:44 PM UTC): This scheduled maintenance is now complete. The public ingress has been updated in all four regions (LON1, FRA1, NYC1 and MUM1) with no customer-impacting issues beyond the brief, expected restarts. Object Storage and the VNC console are fully operational. Thank you for your pati…
Degraded storage and network performance in LON1Minor incident
Jul 28, 2026, 10:55 AM UTC to Jul 29, 2026, 7:00 AM UTC (20h 5m)resolved
their latest update (Jul 29, 2026, 7:00 AM UTC): Storage and network performance in the London (LON1) region has returned to normal levels and the fix has held under monitoring. This incident is now resolved. Thank you for your patience.
Service disruption in FRA1Minor incident
Jun 30, 2026, 7:57 PM UTC to Jul 1, 2026, 9:58 PM UTC (1d 2h)resolved
their latest update (Jul 1, 2026, 9:58 PM UTC): This incident is now resolved. Service was restored at approximately 21:58 UTC on 1 July 2026. Our engineering team has monitored throughout the night and confirmed that compute and Kubernetes cluster instance services in the FRA1 region are operating normally. This incident is n…
Storage and compute instability in FRA1Minor incident
Jun 30, 2026, 9:45 AM UTC to Jun 30, 2026, 2:22 PM UTC (4h 37m)resolved
their latest update (Jun 30, 2026, 2:22 PM UTC): This incident is now resolved. Storage and compute services in the FRA1 region are operating normally.
Civo dashboard & API issues accessing NYC1Minor incident
Jun 26, 2026, 4:00 AM UTC to Jun 26, 2026, 5:50 AM UTC (1h 50m)resolved
their latest update (Jun 26, 2026, 5:50 AM UTC): We are aware of issues accessing the Civo dashboard and API with error pages occurring for some users accessing their NYC1 resources. We are investigating the cause.
Planned Maintenance in FRA1Maintenance
Apr 13, 2026, 12:00 AM UTC to Apr 21, 2026, 9:30 PM UTC (8d 21h)completed
their latest update (Apr 21, 2026, 9:30 PM UTC): This scheduled maintenance is now complete. All FRA1 compute nodes have been successfully upgraded with no customer-impacting issues. Thank you for your patience.
API actions to workloads disrupted in FRA1Minor incident
Mar 24, 2026, 7:07 AM UTC to Mar 24, 2026, 8:31 AM UTC (1h 24m)resolved
their latest update (Mar 24, 2026, 8:31 AM UTC): The issue affecting API actions to workloads in the FRA1 region has been resolved. All services have returned to normal operation.
Partial GPU outage in LON1Minor incident
Mar 14, 2026, 8:40 AM UTC to Mar 15, 2026, 9:00 AM UTC (1d 0h)resolved
their latest update (Mar 15, 2026, 9:00 AM UTC): All services have been restored and are stable. The issue is now resolved.
Service disruption in FRA1Minor incident
Feb 24, 2026, 3:12 PM UTC to Feb 26, 2026, 10:00 AM UTC (1d 18h)resolved
their latest update (Feb 26, 2026, 10:00 AM UTC): This incident is now resolved. The root causes have been identified and fixes have been deployed to the FRA1 region. All services are operating normally and we continue to monitor.
Plannned Maintenance in FRA1 2026-02-09Maintenance
Feb 9, 2026, 12:00 AM UTC to Feb 27, 2026, 9:00 AM UTC (18d 9h)completed
their latest update (Feb 27, 2026, 9:00 AM UTC): The scheduled maintenance for the FRA1 region has been completed successfully. Thank you for your patience during this period.
Showing the 10 most recent of 31 incidents Civo has declared in the history we hold.
These entries are Civo's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Civo's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.