- Level
- confirmed
- Worst impact
- Degraded
- Regions
- apac
- Down Index
- 12of 100
What to do
Check whether you use ngrok in apac. 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 0m it lasted.
Anything that failed between 2026-09-01 18:20 UTC and 2026-08-28 16: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 1
- resolved
Between August 28 and September 1, people invited to an ngrok account couldn't accept the invitation. The invitation link returned an error instead of signing the user in. An authentication change shipped on August 28 broke the URL that redeems an invitation. We moved redemption to login.ngrok.com, and invitations worked again from September 1 at 00:21 UTC. Users routed through Tokyo kept seeing the error until 14:15 UTC, when we cleared a stale routing config in that region. If an invitation still fails, ask the account owner to send a new one, or email support@ngrok.com.
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-ac01b825dd
Is ngrok still down?
No, this incident was resolved 2026-08-28 16:00 UTC. For ngrok's live state, see https://down.guide/ngrok.
How long did it last?
0m, from 2026-09-01 18:20 UTC to 2026-08-28 16:00 UTC, by the times ngrok posted.
What was affected?
ngrok named in apac.
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.