Rewindex

ChangesngrokGetting a high rate of ERR_NGROK_503 in the EU region - No available reserved addresses

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

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what ngrok removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Getting a high rate of ERR_NGROK_503 in the EU region - No available reserved addresses
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2024-12-09 16:20 UTC
AddedResolved time#5
Before: not present
After: 2024-12-09 18:27 UTC
AddedAffected components#6
Before: not present
After: Agent Connectivity - Region - EU, Region - EU
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateidentified#9
Before: not present
After: We have identified the issue and are deploying a fix.
AddedUpdatemonitoring#10
Before: not present
After: We have deployed the fix and are monitoring
AddedUpdatemonitoring#11
Before: not present
After: We are continuing to monitor for any further issues.
AddedUpdateresolved#12
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Monday, December 9, 2024

1 incident change

All ngrok changesngrok profileMarkdownJSON