Skip to main content
Menu
Doppler

Incident

Unable to fetch secrets from the Doppler dashboard and API

Partial outage Lasted 22m · started · Doppler's page

DWN-8e9f010256

Level
confirmed
Worst impact
Partial outage
Components
API (api.doppler.com), Dashboard (dashboard.doppler.com)
Down Index
26of 100

What to do

  • Check whether you use Doppler API (api.doppler.com), Dashboard (dashboard.doppler.com). Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 22m it lasted.

    Anything that failed between 2023-08-04 22:28 UTC and 2023-08-04 22:50 UTC may need a replay.
  • Subscribe to Doppler's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=doppler works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

This incident was caused by a faulty Kubernetes NetworkPolicy change.
Read the postmortem

Updates from Doppler 4

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. resolved

    This incident has been resolved.

    provider

  4. postmortem

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-8e9f010256

Is Doppler still down?

No, this incident was resolved 2023-08-04 22:50 UTC. For Doppler's live state, see https://down.guide/providers/doppler.

How long did it last?

22m, from 2023-08-04 22:28 UTC to 2023-08-04 22:50 UTC, by the times Doppler posted.

What was affected?

Doppler named API (api.doppler.com), Dashboard (dashboard.doppler.com).

What caused it?

Doppler wrote: "This incident was caused by a faulty Kubernetes NetworkPolicy change." The postmortem: https://stspg.io/s4r601cq5k78

Where does this come from?

Doppler's official status page, https://www.dopplerstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.