- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on ngrok. 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 36m it lasted.
Anything that failed between 2026-09-03 23:34 UTC and 2026-09-04 00:11 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 3
- investigating
New accounts or newly created authtokens are not able to connect. Users get Team is looking into the issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- 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-cae37b6047
Is ngrok still down?
No, this incident was resolved 2026-09-04 00:11 UTC. For ngrok's live state, see https://down.guide/ngrok.
How long did it last?
36m, from 2026-09-03 23:34 UTC to 2026-09-04 00:11 UTC, by the times ngrok posted.
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.