- Level
- confirmed
- Worst impact
- Degraded
- Components
- Region - AP
- Down Index
- 20of 100
What to do
Check whether you use ngrok Region - AP. 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 32m it lasted.
Anything that failed between 2024-02-07 21:34 UTC and 2024-02-08 00:06 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 identified an issue with a service rollout in the ap region and are resolving this issue. Customers may see a percentage of requests fail at ngrok's edge. We are resolving the issue and monitoring for recovery.
provider
- monitoring
We are seeing a partial recovery and continuing to monitor.
provider
- resolved
After monitoring, we believe this issue to be resolved. Please reach out to our support team if you continue to see issues.
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-1404b9b512
Is ngrok still down?
No, this incident was resolved 2024-02-08 00:06 UTC. For ngrok's live state, see https://down.guide/providers/ngrok.
How long did it last?
2h 32m, from 2024-02-07 21:34 UTC to 2024-02-08 00:06 UTC, by the times ngrok posted.
What was affected?
ngrok named Region - AP.
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.