- Level
- confirmed
- Worst impact
- Degraded
- Components
- Region - JP, Region - JP
What to do
Check whether you use ngrok Region - JP, Region - JP. 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 7m it lasted.
Anything that failed between 2024-03-18 20:53 UTC and 2024-03-18 22:00 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
- identified
We have a identified an issue with the jp region and are working to resolve the issue.
provider
- monitoring
We have fixed the issues with JP region and are monitoring.
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-3982216cb8
Is ngrok still down?
No, this incident was resolved 2024-03-18 22:00 UTC. For ngrok's live state, see https://down.guide/ngrok.
How long did it last?
1h 7m, from 2024-03-18 20:53 UTC to 2024-03-18 22:00 UTC, by the times ngrok posted.
What was affected?
ngrok named Region - JP, Region - JP.
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.