Divio Outage History

9 incidents recorded over the last 365 days, 4 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.

Every Recorded Divio Incident

Divio incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 9, 2026Scheduled maintenance: RabbitMQ / OpenCloud United Kingdom regionWe will be performing scheduled maintenance on the RabbitMQ infrastructure in the OpenCloud United Kingdom (UK) region. During this window, RabbitMQ instances will be restarted, resulting in brief periods of downtime…1h 0mScheduled
Oct 30, 2026Schedule maintenance: RabbitMQ / OpenCloud US regionThe scheduled maintenance has been completed.1h 0mScheduled
Jun 1, 2026Scheduled Maintenance: RabbitMQ Cluster (Exoscale / OpenCloud Swiss Region)The scheduled maintenance has been completed.30 minScheduled
Apr 21, 2026Minor upgrade of PostgreSQL (OpenCloud regions: EU, US, GB)The scheduled maintenance has been completed.30 minScheduled
Apr 7, 2026Scheduled Maintenance: RabbitMQ Cluster (Exoscale / OpenCloud Swiss Region)The scheduled maintenance has been completed.1h 45mScheduled
Mar 18, 2026Availability problem in EuropeThis incident has been resolved.33 minResolved
Mar 5, 2026Availability problem in EuropeThis incident has been resolved.35 minResolved
Feb 10, 2026DNS Service DisruptionDNSimple has confirmed that all systems are operational and we can confirm from our side that domain resolution is working normally for all customers.3h 49mResolved
Nov 18, 2025Cloudflare Global Network issuesService Impact Restored: We have confirmed that the intermittent issues affecting the Divio Control Panel and Media/Asset Delivery are restored.6h 52mResolved

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 Divio 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 Divio 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 Divio 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 Divio outage in this window ran 6h 52m, against a mean recovery of 1h 50m. If you depend on Divio 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.