ngrok: `jp` region is down for new tunnel starts and endpoint configuration changes

What to do

Check whether you use ngrok 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 55m it lasted.
Anything that failed between 2024-03-07 16:25 UTC and 2024-03-07 17:20 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.

identifiedMar 7, 2024, 4:25 PM UTC
The `jp` region is unable to update state, as such new tunnel starts will fail and changes to configuration for endpoints and Edges will fail. Existing tunnels are still working. The team has identified the issue and is working on mitigation.
provider
identifiedMar 7, 2024, 4:46 PM UTC
We are continuing to work on a fix for this issue.
provider
monitoringMar 7, 2024, 5:00 PM UTC
We are seeing `jp` recover and are continuing to monitor.
provider
resolvedMar 7, 2024, 5:20 PM UTC
We are fully recovered in `jp`.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is ngrok still down?

No, this incident was resolved 2024-03-07 17:20 UTC. For ngrok's live state, see https://down.guide/ngrok.

How long did it last?

55m, from 2024-03-07 16:25 UTC to 2024-03-07 17:20 UTC, by the times ngrok posted.

What was affected?

ngrok named 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.