Skip to main content
ngrok

Endpoints using traffic policies are erroneously hitting limits

Partial outage Lasted 1h 25m · started · ngrok's page

Level
confirmed
Worst impact
Partial outage
Components
Dashboard (https://dashboard.ngrok.com)
Down Index
29of 100

What to do

  • Check whether you use ngrok Dashboard (https://dashboard.ngrok.com). Check your stack

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

    Anything that failed between 2026-09-08 19:01 UTC and 2026-09-08 20:26 UTC may need a replay.
  • Subscribe to ngrok's feed to hear about the next one first. RSS feed

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

Updates from ngrok 5

  1. investigating

    We are currently investigating an issue preventing some customers from logging in to dashboard.ngrok.com

    provider

  2. investigating

    Customer endpoints using traffic policy are erroneously being flagged as hitting limits. The ngrok engineering team is currently working to resolve this issue.

    provider

  3. investigating

    We are continuing to investigate this issue.

    provider

  4. monitoring

    A fix has been deployed to all regions and endpoints using traffic policies are no longer being erroneously limited. Customers may still see notices in their dashboards warning about the limits.

    provider

  5. resolved

    This incident has been resolved.

    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-5226219f44

Is ngrok still down?

No, this incident was resolved 2026-09-08 20:26 UTC. For ngrok's live state, see https://down.guide/ngrok.

How long did it last?

1h 25m, from 2026-09-08 19:01 UTC to 2026-09-08 20:26 UTC, by the times ngrok posted.

What was affected?

ngrok named Dashboard (https://dashboard.ngrok.com).

What caused it?

ngrok hasn't published a root cause. If it does, it shows here.

Where does this come from?

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