Dub Outage History
2 incidents recorded over the last 365 days, 2 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 Dub Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 9, 2026 | Increased API latency on api.dub.coThis incident is fully resolved. | -47 min | Resolved |
| Mar 11, 2026 | Intermittent link redirect and API errorsWe've pushed up a long-term fix (multi-tier caching mechanism) to defend against future DDoS attacks. | -281 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 Dub 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 Dub 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 Dub 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.