Didomi Outage History
6 incidents recorded over the last 365 days, 6 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 Didomi Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Delay in Integrations & Webhooks deliveryThis incident has been resolved. | 3h 2m | Resolved |
| Nov 2, 2026 | Platform API degraded performanceSome requests to our Admin API and REST API returned 5xx errors, and the Didomi Console was intermittently unavailable. The cause was a short-lived spike in traffic from a single integration that temporarily saturated… | 1h 13m | Resolved |
| Sep 4, 2026 | Analytics Dashboards and Exports DownThis incident has been resolved. | 3h 14m | Resolved |
| Jul 28, 2026 | Elevated API and Console errorsBetween 19:38 and 20:13 UTC on July 21, 2026, some requests to our Admin API and REST API returned 5xx errors, and the Didomi Console was intermittently unavailable. The cause was a short-lived spike in traffic from a… | -9456 min | Resolved |
| May 19, 2026 | Didomi Console not loadingAccess to the Didomi Console at console.didomi.io has been restored and the Console is operating normally. The issue was related to an incident affecting our hosting provider, Netlify, which has now been resolved. | 1h 47m | Resolved |
| Feb 19, 2026 | Analytics Dashboards DownThis incident was investigated and traced to an upstream issue with our third-party provider, Sigma. | 47 min | Resolved |
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 Didomi 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 Didomi 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 Didomi 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 Didomi outage in this window ran 3h 14m, against a mean recovery of 2h 1m. If you depend on Didomi 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.