Major incident
ngrok: Endpoints using traffic policies are erroneously hitting limits
Sep 8, 2026, 19:01 UTC
started
20:26 UTC
resolved
1 h 25 min
duration
Affected: Dashboard (https://dashboard.ngrok.com)
Current status of ngrok: Operational — live ngrok status
Timeline
- Sep 8, 2026, 19:01 UTCinvestigatingWe are currently investigating an issue preventing some customers from logging in to dashboard.ngrok.com
- Sep 8, 2026, 19:29 UTCinvestigatingCustomer endpoints using traffic policy are erroneously being flagged as hitting limits. The ngrok engineering team is currently working to resolve this issue.
- Sep 8, 2026, 19:30 UTCinvestigatingWe are continuing to investigate this issue.
- Sep 8, 2026, 19:37 UTCmonitoringA 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.
- Sep 8, 2026, 20:26 UTCresolvedThis incident has been resolved.
Updates as published by ngrok (original).
Other services with incidents at the same time
- Confluent Cloud 20:01 UTC · Connectivity degradation - AWS us-east-1
- Kaseya 19:43 UTC · Datto BCDR - Server5465 (US-East) - Degraded Node Functionality
- Miro 19:21 UTC · Sign-in with username and password is unavailable
- Kaseya 19:10 UTC · Datto BCDR - Server2214 (US-East) - Degraded Node Functionality
- Flexera System Status Dashboard 18:46 UTC · Flexera One - IT Asset Management - APAC - Service Unavailable
- dbt Cloud 18:44 UTC · User Login Sessions Terminated
More ngrok incidents
- September 8, 2026 Error when signing in via SSO
- April 28, 2026 Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.
- March 31, 2026 Download of the ngrok binary are returning 500 errors