Doppler Outage History
4 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 Doppler Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 27, 2026 | Elevated timeouts for dashboard, CLI, and APIThis incident has been resolved. | 59 min | Resolved |
| Jul 17, 2026 | CLI Downloads failingThis incident has been resolved by our engineering team. | 5 min | Resolved |
| Nov 20, 2025 | Background job delays impacting sync, webhook and email deliveryThis incident has been resolved. | 3h 50m | Resolved |
| Nov 18, 2025 | System OutageThis incident is now resolved. | 3h 11m | 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 Doppler 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 Doppler 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 Doppler 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 Doppler outage in this window ran 3h 50m, against a mean recovery of 2h 1m. If you depend on Doppler 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.