Live  /  ngrok  /  Incident

ngrok: Endpoints using traffic policies are erroneously hitting limits

ngrok · ngrok.comMajor incidentResolved2026-09-08 19:37 UTC
Public — what happened

Summary

ngrok reported a major incident in which endpoints that rely on traffic policies were wrongly being held back by usage limits, starting at 19:01 UTC on 2026-09-08. The company said it rolled out a fix across all regions, after which those endpoints stopped being incorrectly restricted, and it lists the issue as resolved at 20:27. ngrok noted that some customers might continue to see limit warnings in their dashboards, and the incident remains in a monitoring state.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach ngrok against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for ngrok: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the ngrok report →

More from ngrok

Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.

The full archive is on the ngrok status & history page.

Related: ngrok status & history. SquidGrid is not affiliated with ngrok.