- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
- Regions
- eu, us
- Down Index
- 38of 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
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 2h 44m it lasted.
Anything that failed between 2025-08-13 22:04 UTC and 2025-08-14 00:48 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
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
This incident has been resolved.
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-5f4a0b646c
Is ngrok still down?
No, this incident was resolved 2025-08-14 00:48 UTC. For ngrok's live state, see https://down.guide/providers/ngrok.
How long did it last?
2h 44m, from 2025-08-13 22:04 UTC to 2025-08-14 00:48 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.