Rewindex

ChangesngrokEndpoints using traffic policies are erroneously hitting limits

ngrok: Major incident: Endpoints using traffic policies are erroneously hitting limits

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: Endpoints using traffic policies are erroneously hitting limits
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-09-08 19:01 UTC
AddedResolved time#5
Before: not present
After: 2026-09-08 20:26 UTC
AddedAffected components#6
Before: not present
After: Dashboard (https://dashboard.ngrok.com)
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating an issue preventing some customers from logging in to dashboard.ngrok.com
AddedUpdateinvestigating#8
Before: not present
After: Customer endpoints using traffic policy are erroneously being flagged as hitting limits. The ngrok engineering team is currently working to resolve this issue.
AddedUpdateinvestigating#9
Before: not present
After: We are continuing to investigate this issue.
AddedUpdatemonitoring#10
Before: not present
After: A fix has been deployed to all regions and endpoints using traffic policies are no longer being erroneously limited. Customers may still see notices in their dashboards warning about the limits.
AddedUpdateresolved#11
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

Tuesday, September 8

1 incident change

All ngrok changesngrok profileMarkdownJSON