Ceros status history
Current state: operational — “All Systems Operational” per https://status.ceros.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Ceros incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: Service Disruption Due to Downstream Provider Outage — 5.3 h (2025-10-20 09:50 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-04-14 12:56 UTC | Degraded Performance with Content Creation | resolved | minor | 2 h 58 min |
| 2025-12-03 13:49 UTC | User Access Disrupted | resolved | major | 3 h 48 min |
| 2025-10-20 09:50 UTC | Service Disruption Due to Downstream Provider Outage | resolved | major | 5 h 17 min |
| 2025-08-21 18:53 UTC | Degraded Performance | resolved | minor | 3 h 11 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Ceros with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ceros"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
