Doppler status history

Current state: operational — “All Systems Operational” per https://www.dopplerstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days

1incidents, last 90 days

4incidents on record

Incidents per week, last 12 weeks:

Get Doppler alerts in your Slack — free template RSS for Doppler

How long do Doppler incidents last?

2.1 hmedian incident duration4 measured

3.8 h90th percentile1 in 10 ran longer

3.2 hmedian, major/critical only3 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Background job delays impacting sync, webhook and email delivery — 3.8 h (2025-11-20 15:55 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (4)

Started	Incident	Status	Impact	Duration
2026-07-17 00:03 UTC	CLI Downloads failing	resolved	none	5 min
2025-11-20 15:55 UTC	Background job delays impacting sync, webhook and email delivery	resolved	major	3 h 50 min
2025-11-18 11:48 UTC	System Outage	resolved	critical	3 h 11 min
2025-08-20 18:52 UTC	Background job delays impacting sync and email delivery	resolved	critical	1 h 06 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Doppler with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "doppler"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}