- Level
- confirmed
- Worst impact
- Degraded
- Components
- Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
- Regions
- eu, us
- Down Index
- 25of 100
What to do
Check whether you use ngrok Region - AP, Region - AU, Region - EU, Region - IN and 4 more in eu, us. 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 41m it lasted.
Anything that failed between 2025-07-07 20:48 UTC and 2025-07-07 21:29 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
We are currently investigating this issue.
provider
- identified
The issue has been indentified and only affects a very small number of accounts. A fix is being work on.
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-087c408995
Is ngrok still down?
No, this incident was resolved 2025-07-07 21:29 UTC. For ngrok's live state, see https://down.guide/ngrok.
How long did it last?
41m, from 2025-07-07 20:48 UTC to 2025-07-07 21:29 UTC, by the times ngrok posted.
What was affected?
ngrok named Region - AP, Region - AU, Region - EU, Region - IN and 4 more in eu, us.
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.