Doppler

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-17 00:03 UTC

   We've received reports of errors when attempting to download the Doppler CLI. We're currently investigating the issue.

2. resolved 2026-07-17 00:08 UTC

   This incident has been resolved by our engineering team.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Vercel, Dashboard (dashboard.doppler.com), Heroku, AWS Parameter Store, AWS Secrets Manager, Azure App Service, Azure Key Vault, Azure Dev Ops, CircleCI, Codefresh, Fly.io, GCP Secret Manager, GitHub, Laravel Forge, Netlify, Railway, Render, Vercel, AWS IAM Dynamic Secrets, AWS MySQL Rotation, AWS User Key Rotation, SendGrid Rotation, Twilio Rotation, Splunk

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-20 15:55 UTC

   We are currently investigating an issue involving delays impacting integration sync, webhook and email delivery.

2. investigating 2025-11-20 16:43 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-20 18:54 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-20 19:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com), Marketing site (doppler.com), Cloudflare Network

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. monitoring 2025-11-18 11:48 UTC

   Doppler is currently affected by an ongoing Cloudflare outage. This is impacting Dashboard and API access. Services accessing Doppler secrets through an integration (e.g., Kubernetes operator or syncs) should remain unaffected, but direct attempts to access the API will be...

2. identified 2025-11-18 12:51 UTC

   Services are still impacted. Our team is continuing to monitor the situation.

3. monitoring 2025-11-18 13:49 UTC

   Cloudflare identified the issue and has been working on implementing a fix. Our dashboard and API are currently available and we're continuing to monitor the situation.

4. resolved 2025-11-18 14:59 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Vercel, Dashboard (dashboard.doppler.com), Heroku, AWS Parameter Store, AWS Secrets Manager, Azure App Service, Azure Key Vault, Azure Dev Ops, CircleCI, Codefresh, Fly.io, GCP Secret Manager, GitHub, Laravel Forge, Netlify, Railway, Render, Vercel, AWS IAM Dynamic Secrets, AWS MySQL Rotation, AWS User Key Rotation, SendGrid Rotation, Twilio Rotation, Splunk

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-20 18:52 UTC

   We're currently investigating an issue involving delays in background job processing that's impacting integration syncs, email delivery, activity log delivery, and webhook delivery (amongst other things). Impacted integration syncs will show as failed with "Out of sync". If...

2. investigating 2025-08-20 19:15 UTC

   We are continuing to investigate the issue.

3. identified 2025-08-20 19:36 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-08-20 19:38 UTC

   A fix has been implemented and we're monitoring the situation. All unprocessed jobs have now been processed.

5. resolved 2025-08-20 19:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-06 03:36 UTC

   We are currently investigating this issue.

2. monitoring 2025-08-06 04:30 UTC

   We believe the issue is resolved and are monitoring for any additional issues.

3. resolved 2025-08-06 05:40 UTC

   The issue is resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare, Google Cloud.

1. investigating 2025-06-12 18:29 UTC

   We're currently investigating a system-wide outage related to disruptions with GCP and Cloudflare.

2. monitoring 2025-06-12 20:19 UTC

   GCP and Cloudflare have been gradually resolving their outages and Doppler services have been partially restored.

3. resolved 2025-06-12 21:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-11 02:15 UTC

   We're currently experiencing downtime due to extended database maintenance.

2. resolved 2025-04-11 02:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-30 22:10 UTC

   Certain users may be unable to fetch from personal configs.

2. investigating 2024-10-30 23:19 UTC

   We are continuing to investigate this issue.

3. investigating 2024-10-30 23:41 UTC

   A fix has been identified and should be deployed soon.

4. investigating 2024-10-30 23:53 UTC

   Only users with access to personal configs via groups are affected. Users with direct access to personal configs are not affected.

5. resolved 2024-10-31 00:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Splunk

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-05-31 18:04 UTC

   Activity Logs stopped publishing to Splunk as of May 30th at 19:55 UTC. The issue has been identified and a fix is in progress. After the issue has been resolved and the connections reconnected, missed activity logs will be republished.

2. identified 2024-05-31 18:05 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2024-05-31 19:51 UTC

   A fix has been deployed and we are monitoring reconnections. We will backfill missed Activity Logs as needed after workplaces reconnect Splunk.

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-04-15 15:59 UTC

   For a period of 18 minutes, secrets related API and dashboard actions saw increased error rates (503) and timeouts.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Railway

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-02-29 21:29 UTC

   We are working on a fix.

2. identified 2024-02-29 21:38 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2024-02-29 22:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-02-29 22:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-08-04 22:28 UTC

   We are currently investigating this issue.

2. investigating 2023-08-04 22:46 UTC

   We are continuing to investigate this issue.

3. resolved 2023-08-04 22:50 UTC

   This incident has been resolved.

4. postmortem 2023-08-04 23:18 UTC

   This incident was caused by a faulty Kubernetes NetworkPolicy change. We’ll be evaluating how we can adjust our deployment procedures to catch these changes in the future.

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-03-22 22:30 UTC

   We're currently investigating this issue. If you need immediate availability, you can install Doppler directly from our published release artifacts instead of via your OS's package registry by running: ``` (curl -Ls --tlsv1.2 --proto "=https" --retry 3...

2. resolved 2023-03-22 23:13 UTC

   An incident was identified at our provider for OS package registry downloads. They've fixed the issue and installs from OS package registries are available again. Impact: The incident affected all Doppler users attempting to install the Doppler CLI via their OS package...

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. resolved 2023-02-27 20:45 UTC

   For several hours on February 27, 2023, users intermittently encountered errors when attempting to install the Doppler CLI. This issue was due to a related incident on GitHub, where Doppler hosts all CLI binaries and signatures. According to GitHub's incident report, GitHub...

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2023-01-16 19:11 UTC

   During this incident, changes to secrets could not be synced to integrations or trigger webhook updates. Additionally, activity log notifications could not be posted to Slack, Microsoft Teams, Sumo Logic, Splunk, or Datadog.

2. postmortem 2023-01-17 01:31 UTC

   # Summary From 2023-01-16 19:11 UTC to 2023-01-16 20:04 UTC, Doppler experienced a partial outage which prevented sync integrations, webhooks, and activity log notifications from executing. The outage also prevented an internal job from firing which recomputes the version hashes...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Heroku

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-01-05 00:48 UTC

   New and existing Heroku sync integrations are currently not functioning. We have identified the issue and are working on resolving it. Secrets previously synced to Heroku apps will remain available but new secret changes in Doppler will not be synced until this is resolved.

2. identified 2023-01-05 01:06 UTC

   This incident may persist for up to 24 hours. In the meantime, if you have an urgent secret change that needs to be made, please update the secret in your Doppler dashboard and then manually update the secret in Heroku directly via `heroku config:set`. Updating the secret in...

3. resolved 2023-01-05 18:23 UTC

   This issue is now resolved. Additional action is required to re-enable existing Heroku syncs. All workplaces will need to reconnect their Heroku sync integrations from the [workplace Settings page](https://dashboard.doppler.com/workplace/settings). Once integrations are...

4. postmortem 2023-01-05 21:30 UTC

   **Root Cause** Doppler syncs secrets to Heroku via a Heroku OAuth application. This application is created in the Heroku dashboard and must be owned by a single Heroku user account. Doppler’s previous Heroku OAuth application was owned by a specific Doppler employee’s Heroku...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-08-29 00:38 UTC

   We are currently investigating this issue.

2. monitoring 2022-08-29 01:32 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2022-08-29 01:38 UTC

   This issue was caused by a redis server running out of memory. We've increased the amount of memory allotted to this server. We'll also be setting up additional alerting on redis resource usage so that we can catch and prevent these issues in the future.

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2022-07-28 20:00 UTC

   An error was discovered while running a data backfill job that resulted in users being unable to update secrets for affected environments. The data that was generated triggered an unexpected assertion in the secrets validation code. Users that attempted to save secrets in these...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2022-06-21 06:33 UTC

   We are currently investigating this issue.

2. identified 2022-06-21 06:52 UTC

   This issue is due to a widespread Cloudflare outage. https://www.cloudflarestatus.com/incidents/xvs51y9qs9dj

3. monitoring 2022-06-21 07:09 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2022-06-21 07:10 UTC

   We are continuing to monitor for any further issues.

5. resolved 2022-06-21 07:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-12-22 16:50 UTC

   We are currently investigating this issue.

2. monitoring 2021-12-22 16:54 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2021-12-22 17:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2021-12-07 22:05 UTC

   We're intermittently experiencing outages with our tokenization provider, who is impacted by the AWS us-east-1 outage.

2. resolved 2021-12-08 10:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2021-12-07 18:32 UTC

   The tokenization provider is impacted by the AWS us-east-1 outage.

2. monitoring 2021-12-07 18:45 UTC

   Our tokenization provider has recovered and all Doppler services are operational.

3. resolved 2021-12-07 19:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Dashboard (dashboard.doppler.com)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2021-11-19 23:48 UTC

   We're currently seeing intermittent errors on dashboard.doppler.com. We believe this is a connectivity issue between Cloudflare and our hosting provider and are investigating. API and CLI usage are not affected.

2. monitoring 2021-11-20 00:38 UTC

   We believe we've identified and resolved the issue. We're currently monitoring the fix to confirm.

3. resolved 2021-11-20 00:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-11-16 17:39 UTC

   This appears to be due to a larger Google outage. We are in contact with Google support and are monitoring their status page.

2. monitoring 2021-11-16 18:09 UTC

   The services are now coming back online. We are continuing to monitor.

3. resolved 2021-11-16 18:19 UTC

   This incident has been resolved. https://status.cloud.google.com/incidents/6PM5mNd43NbMqjCZ5REh

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-11-15 22:14 UTC

   We are currently investigating an issue with Service Tokens getting rate limited.

2. monitoring 2021-11-15 22:37 UTC

   We've rolled back the code change that's causing this issue. Service Tokens should resume normal operation.

3. resolved 2021-11-15 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2021-10-01 09:00 UTC

   Our API experienced an 11 minute outage due to database contention over locking our Workplace table. The issue resolved itself once the locks expired. We've refactored the affected component to achieve the desired result without locking. We'll be exploring a more holistic fix to...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2021-09-23 17:08 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2021-09-23 17:26 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2021-09-23 19:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2021-09-23 19:12 UTC

   This issue has been resolved. We've fixed an erroneous permission check that disallowed lower privilege users from authorizing the CLI.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-04-28 03:15 UTC

   We are currently investigating this issue.

2. monitoring 2021-04-28 03:24 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2021-04-28 03:26 UTC

   This incident with our third party vendor has been resolved. All secrets access has been restored.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2021-04-14 04:38 UTC

   We are currently experiencing an issue with authenticating CLI tokens. When connecting with a CLI token, users are receiving the message "Invalid CLI Token". We are investigating this and will have a new update within 1 hour. If you are experiencing this issue, you can...

2. resolved 2021-04-14 05:44 UTC

   The issue causing CLI authentication to fail has been resolved. CLI tokens should now be functioning as expected. If your CLI token continues not to work, please reach out to support.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: Dashboard (dashboard.doppler.com)

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-01-06 05:21 UTC

   SAML SSO has been disabled on all workplaces due to a faulty migration script. We are currently in the process of recovering SAML and will update this incident accordingly.

2. resolved 2021-01-06 05:53 UTC

   SAML SSO has been restored for all workplaces.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com), Marketing site (doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2020-07-17 21:20 UTC

   DNS resolution is currently failing for doppler.com and all subdomains. We believe this is a Cloudflare outage but are investigating.

2. investigating 2020-07-17 21:29 UTC

   We are continuing to investigate this issue.

3. monitoring 2020-07-17 21:37 UTC

   DNS resolution appears to be operating normally again. We are still monitoring.

4. monitoring 2020-07-17 21:41 UTC

   We are continuing to monitor for any further issues.

5. resolved 2020-07-17 22:05 UTC

   DNS resolution has resumed normal operation. A proper postmortem will follow.

6. postmortem 2020-07-17 22:17 UTC

   Today at 2:15pm Pacific we experienced our second outage in the last two weeks. Sadly the timing is not great but it did give us the opportunity to re-evaluate our failure points as we continue to harden our infrastructure. This outage affected all of our endpoints, from our...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-07-10 03:38 UTC

   We are currently investigating this issue.

2. monitoring 2020-07-10 04:05 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2020-07-10 04:07 UTC

   This incident has been resolved.

4. postmortem 2020-07-10 04:14 UTC

   Today at 8:38pm Pacific we experienced a critical outage that brought down all of our servers on both our primary and failover production environments. This outage did not result in any data loss but did disable all dashboard and API access. ## Why Did it Happen? At Doppler, we...

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2020-02-06 23:43 UTC

   We had a migration script that failed to run before the rest of our services deployed. This caused the newly deployed services to crash because the database was missing a column in a critical table. Our deployment orchestrator quickly detected the issue and reverted to the...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2019-12-09 05:00 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2019-12-09 06:48 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2019-12-09 07:38 UTC

   This issue has been resolved. During a revamp of our authentication methods, we introduced a logic bug. This bug prevented restricted API Keys from gaining access to their projects, causing any restricted API Key to receive the error "User must be provided." A fix has been...

4. postmortem 2019-12-09 09:23 UTC

   A critical outage around Restricted API Key authentication occurred Sunday evening at exactly 9:00 PM PST leading to over 1 hour of downtime. This outage did not result in any data loss but did render Restricted API Keys inoperable with our API endpoints for that period of time....

Excerpts are shortened. Read the full incident on Doppler's status page.

Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2019-04-15 01:08 UTC

   We are modifying our StatusPage to add new metrics which may briefly result in metrics showing false outages.

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com), Dashboard (dashboard.doppler.com)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2019-03-06 23:45 UTC

   We have investigated reports of elevated error rates. We've identified the issue causing an outage in updates and are rolling out a fix.

2. identified 2019-03-06 23:46 UTC

   We are continuing to work on a fix for this issue.

3. identified 2019-03-06 23:58 UTC

   We are continuing to work on a fix for this issue.

4. identified 2019-03-07 00:29 UTC

   We are still working on a fix for this issue on our API front. A fix has been implemented for the affected website and we are monitoring the results.

5. monitoring 2019-03-07 00:42 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2019-03-07 00:50 UTC

   This incident has been resolved.

7. postmortem 2019-03-07 05:28 UTC

   Our first critical outage occurred today, and it led to almost 2 hours of downtime but thankfully no data loss. This was an unacceptable amount of downtime and could have been completely prevented. We take your trust very seriously as Doppler is a critical path in your devops...

Excerpts are shortened. Read the full incident on Doppler's status page.

Affected: API (api.doppler.com)

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2018-12-19 13:13 UTC

   Upgraded servers and postgres databases for elastic scaling. During transition, a few API requests timed out. All systems are now fully operational.

2. resolved 2018-12-19 13:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Doppler's status page.