Companies / Doppler / changes

Doppler change history

25Major incident
When (UTC)ChangeKind
Major incident: Background job delays impacting sync, webhook and email delivery
Doppler reported a major incident delaying integration sync, webhooks and email delivery, starting at 2025-11-20 15:55 UTC and resolved at 2025-11-20 19:46 UTC; the reported duration was 3 h 50 min. A fix was implemented by 18:54 UTC, but no cause or fix details were stated.
Major incident
Critical incident: System Outage
Doppler reported a critical outage affecting Dashboard and API access due to an ongoing Cloudflare outage; direct API requests were unreliable, while integrations accessing secrets were expected to remain unaffected. It started at 2025-11-18 11:48 UTC and was resolved at 2025-11-18 14:59 UTC, lasting 3 h 11 min.
Major incident
Critical incident: Background job delays impacting sync and email delivery
Doppler reported a critical background-job degradation from 2025-08-20 18:52 UTC to 2025-08-20 19:58 UTC, lasting 1 h 6 min. Integration syncs showed failed with "Out of sync", while email, activity log, and webhook delivery were delayed. A fix was implemented and all unprocessed jobs were processed by 19:38 UTC; the incident was resolved at 19:58 UTC.
Major incident
Major incident: System Outage
Doppler reported a major system-wide outage affecting API (api.doppler.com) and Dashboard (dashboard.doppler.com), from 2025-06-12 18:29 UTC to 2025-06-12 21:07 UTC, lasting 2 h 38 min. Doppler linked the outage to GCP and Cloudflare disruptions; services were partially restored as those providers recovered, and the incident was resolved.
Major incident
Critical incident: Extended Maintenance
Doppler reported critical downtime affecting API (api.doppler.com) and Dashboard (dashboard.doppler.com) due to extended database maintenance. The incident started at 2025-04-11 02:15 UTC and was resolved at 2025-04-11 02:33 UTC, lasting 17 min.
Major incident
Major incident: Unable to fetch secrets from the Doppler dashboard and API
Doppler reported a major outage preventing customers from fetching secrets through the dashboard and API, starting 2023-08-04 22:28 UTC and resolved at 2023-08-04 22:50 UTC (22 min). The vendor attributed the incident to a faulty Kubernetes NetworkPolicy change and said it would evaluate deployment procedures to catch such changes.
Major incident
Major incident: Unable to sync secrets, webhooks, and activity log notifications
Doppler reported a major partial outage blocking secret syncs, webhooks, activity-log notifications, and API-client secret updates. Records list a start of 2023-01-16 20:37 UTC and resolution at 2023-01-16 19:11 UTC, while the postmortem reports 2023-01-16 19:11 UTC to 2023-01-16 20:04 UTC; duration is unknown.
Major incident
Major incident: Heroku sync integrations are failing
Doppler’s major Heroku sync outage ran from 2023-01-05 00:48 UTC to 2023-01-05 18:23 UTC (17 h 34 min), blocking new and existing syncs while previously synced secrets remained available. Resolution required all workplaces to reconnect Heroku integrations from workplace Settings, triggering pending changes to sync.
Major incident
Critical incident: Secrets unable to be read
Doppler reported a critical outage preventing secrets from being read via the API and Dashboard, starting 2022-08-29 00:38 UTC and resolved at 2022-08-29 01:38 UTC (59 min). A Redis server ran out of memory; Doppler increased its allotted memory and said it would add resource-usage alerting.
Major incident
Critical incident: Services responding with 500 Internal Server Error
Doppler’s API (api.doppler.com) and Dashboard (dashboard.doppler.com) returned 500 Internal Server Error responses during a critical outage from 2022-06-21 06:33 UTC to 2022-06-21 07:22 UTC, lasting 49 min. Doppler attributed the issue to a widespread Cloudflare outage and reported implementing a fix before resolution.
Major incident
Critical incident: Unable to connect to the Doppler dashboard and API
Doppler reported a critical outage preventing connections to its API (api.doppler.com) and Dashboard (dashboard.doppler.com), starting at 2021-12-22 16:50 UTC. A fix was implemented by 2021-12-22 16:54 UTC, and the incident was resolved at 2021-12-22 17:08 UTC; the computed duration was 17 min.
Major incident
Major incident: Reading/writing secrets intermittently failing due to an outage at our tokenization provider
Doppler reported a major outage causing intermittent failures reading and writing secrets in the API (api.doppler.com) and Dashboard (dashboard.doppler.com). It started at 2021-12-08 02:20 UTC and was resolved at 2021-12-08 10:20 UTC, lasting 8 h 0 min; Doppler attributed it to its tokenization provider being impacted by the AWS us-east-1 outage.
Major incident
Major incident: Reading/writing secrets failing due to an outage at our tokenization provider
Reading and writing secrets failed across Doppler’s API and Dashboard in a major-impact outage from 2021-12-07 18:32 UTC to 2021-12-07 19:01 UTC (28 min). Doppler attributed the failure to its tokenization provider being impacted by the AWS us-east-1 outage; all services were operational by 2021-12-07 18:45 UTC.
Major incident
Major incident: Dashboard intermittently returning bad gateway errors
Doppler’s Dashboard (dashboard.doppler.com) intermittently returned bad gateway errors in a major-impact incident starting 2021-11-19 23:48 UTC, resolved at 2021-11-20 00:58 UTC (1 h 9 min). API and CLI usage were unaffected. Doppler suspected connectivity between Cloudflare and its hosting provider and reported identifying and resolving the issue before monitoring the fix.
Major incident
Critical incident: All services returning 404
Doppler reported a critical outage with all services returning 404, affecting the API (api.doppler.com) and Dashboard (dashboard.doppler.com). It started at 2021-11-16 17:39 UTC and was resolved at 2021-11-16 18:19 UTC, lasting 39 min. Doppler said it appeared related to a larger Google outage; services were coming back online by 18:09 UTC.
Major incident
Major incident: Users getting rate limited when hitting API
Doppler reported a major API (api.doppler.com) degradation affecting Service Tokens, which were being rate limited. The incident started at 2021-11-15 22:14 UTC and lasted 27 min, resolving at 2021-11-15 22:41 UTC after Doppler rolled back the code change causing the issue.
Major incident
Major incident: API unavailable due to contention over database locking
Doppler reported a major API outage caused by database lock contention on its Workplace table. Recorded start: 2021-10-01 19:34 UTC; resolution: 2021-10-01 09:00 UTC; computed duration unknown (vendor reported 11 minutes). Service recovered when locks expired; Doppler refactored the affected component to avoid locking.
Major incident
Major incident: Workplace admins, viewers and collaborators unable to login via CLI
Doppler reported a major API incident preventing workplace admins, viewers and collaborators from logging in via CLI. It started at 2021-09-23 17:08 UTC and was resolved at 2021-09-23 19:12 UTC, lasting 2 h 4 min. Doppler fixed an erroneous permission check that blocked lower privilege users from authorizing the CLI.
Major incident
Major incident: Secrets storage is unavailable
Doppler reported a major secrets-storage outage affecting API (api.doppler.com) and Dashboard (dashboard.doppler.com), starting 2021-04-28 03:15 UTC and lasting 11 min until resolution at 2021-04-28 03:26 UTC. Doppler said the incident involved a third-party vendor; a fix was implemented and all secrets access was restored.
Major incident
Major incident: CLI Tokens Authentication Issues
Doppler reported a major API (api.doppler.com) incident: CLI token authentication failed with "Invalid CLI Token" errors. It started at 2021-04-14 04:38 UTC and was resolved at 2021-04-14 05:44 UTC, lasting 1 h 5 min. Affected users could work around it by re-logging in with 'doppler login'; Doppler confirmed tokens were functioning again.
Major incident
Critical incident: DNS resolution failure
Doppler reported a critical DNS outage affecting doppler.com and all subdomains, including API, Dashboard, Deploy, documentation and status-page endpoints, from 2020-07-17 21:20 UTC to 2020-07-17 22:05 UTC (45 min). DNS resolution returned to normal; Doppler initially suspected a Cloudflare outage and reported no data loss.
Major incident
Critical incident: Downtime due to migration script
Doppler reported a critical outage starting 2020-07-10 03:38 UTC, lasting 28 min and resolved at 2020-07-10 04:07 UTC. All primary and failover production servers went down, disabling dashboard and API access; Deploy was also listed as affected, with no data loss reported. The incident title attributed the downtime to a migration script; a fix was implemented.
Major incident
Critical incident: Migration Script Race Condition
Doppler reported a critical outage starting and resolved at 2020-02-06 23:43 UTC (computed duration: 0 min; vendor reported approximately 2 minutes of downtime). A migration failed to run before deployment, causing services to crash because a critical database table lacked a column; the deployment orchestrator reverted to the previous build.
Major incident
Critical incident: Restricted API Key authentication is down
Doppler reported a critical Restricted API Key authentication outage affecting API (api.doppler.com) and Deploy (deploy.doppler.com), starting 2019-12-09 05:00 UTC and resolved 2019-12-09 07:38 UTC (2 h 38 min). An authentication-revamp logic bug blocked project access with “User must be provided.” Doppler deployed a fix and reported no data loss.
Major incident
Critical incident: Users are unable to connect to Doppler servers
Doppler reported a critical outage preventing connections to its API (api.doppler.com), Dashboard (dashboard.doppler.com), and Website (doppler.com), disrupting customer access. It started at 2019-03-06 23:45 UTC and was resolved at 2019-03-07 00:50 UTC, lasting 1 h 5 min. Doppler implemented fixes and reported no data loss.
Major incident