Skip to content

Outage tracker

Doppler: incident history

The last 24 hours in detail, Doppler's declared incident record, and our regional check results beside it.

← Back to Doppler's check readings

We started checking Doppler on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Doppler reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Doppler's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Doppler's own status page declared. Below it, any public chatter we saw about Doppler and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Doppler's own status page declared. Three records side by side; none of them changes another.

Our probes, api
Unverified user reportsNo reports about Doppler in the last 24 hours, which is not evidence that nothing is wrong.
Doppler's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Doppler's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Doppler next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%431
US-West99.70%337
Europe100.00%306
Asia-Pacific100.00%186

Their declared record

Doppler's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Elevated timeouts for dashboard, CLI, and APIMinor incident
Oct 27, 2026, 7:26 PM UTC to Oct 27, 2026, 8:25 PM UTC (59 min)resolved
their latest update (Oct 27, 2026, 8:25 PM UTC): This incident has been resolved.
CLI Downloads failingAll systems operational
Jul 17, 2026, 12:03 AM UTC to Jul 17, 2026, 12:08 AM UTC (5 min)resolved
their latest update (Jul 17, 2026, 12:08 AM UTC): This incident has been resolved by our engineering team.
Background job delays impacting sync, webhook and email deliveryPartial outage
Nov 20, 2025, 3:55 PM UTC to Nov 20, 2025, 7:46 PM UTC (3h 51m)resolved
their latest update (Nov 20, 2025, 7:46 PM UTC): This incident has been resolved.
System OutageMajor outage
Nov 18, 2025, 11:48 AM UTC to Nov 18, 2025, 2:59 PM UTC (3h 11m)resolved
their latest update (Nov 18, 2025, 2:59 PM UTC): This incident is now resolved.
Background job delays impacting sync and email deliveryMajor outage
Aug 20, 2025, 6:52 PM UTC to Aug 20, 2025, 7:58 PM UTC (1h 7m)resolved
their latest update (Aug 20, 2025, 7:58 PM UTC): This incident has been resolved.
Elevated error rates for API and DashboardMinor incident
Aug 6, 2025, 3:36 AM UTC to Aug 6, 2025, 5:40 AM UTC (2h 4m)resolved
their latest update (Aug 6, 2025, 5:40 AM UTC): The issue is resolved.
System OutagePartial outage
Jun 12, 2025, 6:29 PM UTC to Jun 12, 2025, 9:07 PM UTC (2h 38m)resolved
their latest update (Jun 12, 2025, 9:07 PM UTC): This incident has been resolved.
Extended MaintenanceMajor outage
Apr 11, 2025, 2:15 AM UTC to Apr 11, 2025, 2:33 AM UTC (18 min)resolved
their latest update (Apr 11, 2025, 2:33 AM UTC): This incident has been resolved.
Partial Personal Config OutageMinor incident
Oct 30, 2024, 10:10 PM UTC to Oct 31, 2024, 12:05 AM UTC (1h 55m)resolved
their latest update (Oct 31, 2024, 12:05 AM UTC): This incident has been resolved.
Splunk Activity Logs Integration OutageMinor incident
May 31, 2024, 6:04 PM UTC to May 31, 2024, 7:51 PM UTC (1h 47m)resolved
their latest update (May 31, 2024, 7:51 PM UTC): A fix has been deployed and we are monitoring reconnections. We will backfill missed Activity Logs as needed after workplaces reconnect Splunk.

Showing the 10 most recent of 38 incidents Doppler has declared in the history we hold.

These entries are Doppler's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Doppler's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.