- Level
- confirmed
- Worst impact
- Operational
- Components
- Region - AP, Region - AP, Region - AU, Region - AU, Region - EU, Region - EU, Region - IN, Region - IN, Region - JP, Region - JP, Region - SA, Region - SA, Region - US, Region - US, Region - us-cal-1, Region - us-cal-1
- Regions
- eu, us
What to do
Check whether you use ngrok Region - AP, Region - AP, Region - AU, Region - AU and 12 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 7h 38m it lasted.
Anything that failed between 2024-11-22 18:11 UTC and 2024-11-23 01:49 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 2
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
The fix has been confirmed and the issue is now 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-c5ca58633e
Is ngrok still down?
No, this incident was resolved 2024-11-23 01:49 UTC. For ngrok's live state, see https://down.guide/providers/ngrok.
How long did it last?
7h 38m, from 2024-11-22 18:11 UTC to 2024-11-23 01:49 UTC, by the times ngrok posted.
What was affected?
ngrok named Region - AP, Region - AP, Region - AU, Region - AU and 12 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.