ngrok: Getting a high rate of ERR_NGROK_503 in the EU region - No available reserved addresses

What to do

Check whether you use ngrok Region - EU in eu. 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 2h 6m it lasted.
Anything that failed between 2024-12-09 16:20 UTC and 2024-12-09 18:27 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.

investigatingDec 9, 2024, 4:20 PM UTC
We are currently investigating this issue.
provider
investigatingDec 9, 2024, 4:21 PM UTC
We are continuing to investigate this issue.
provider
identifiedDec 9, 2024, 4:52 PM UTC
We have identified the issue and are deploying a fix.
provider
monitoringDec 9, 2024, 5:57 PM UTC
We have deployed the fix and are monitoring
provider
monitoringDec 9, 2024, 5:57 PM UTC
We are continuing to monitor for any further issues.
provider
resolvedDec 9, 2024, 6:27 PM UTC
This incident has been resolved.
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-12-09 18:27 UTC. For ngrok's live state, see https://down.guide/ngrok.

How long did it last?

2h 6m, from 2024-12-09 16:20 UTC to 2024-12-09 18:27 UTC, by the times ngrok posted.

What was affected?

ngrok named Region - EU in eu.

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.