Divio status history
Current state: operational — “All Systems Operational” per https://status.divio.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Divio incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Cloudflare Global Network issues — 6.9 h (2025-11-18 12:43 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 (5)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-03-18 10:30 UTC | Availability problem in Europe | resolved | major | 33 min |
| 2026-03-05 10:20 UTC | Availability problem in Europe | resolved | major | 35 min |
| 2026-02-10 17:25 UTC | DNS Service Disruption | resolved | critical | 3 h 49 min |
| 2025-11-18 12:43 UTC | Cloudflare Global Network issues | resolved | major | 6 h 52 min |
| 2025-10-20 16:31 UTC | Elevated error rate | resolved | major | 1 h 46 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 Divio with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"divio"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}