outages.live
Live
ngrokIncident · 2026-09-08 19:01 UTC

Endpoints using traffic policies are erroneously hitting limits

ResolvedOfficial update

This incident has been resolved.

The latest update from ngrok.

State

Resolved

Started

54 d ago

2026-09-08 19:01 UTC

Lasted

1 h 25 min

until 2026-09-08 20:26 UTC

Worst impact

Partial outage

Timeline

5 updates
19:0119:2219:4320:0420:26
Partial outageUpdate postedTimes in UTC

Investigating

36 min 42%

Monitoring

49 min 58%

Updates

Times in UTC

As posted by ngrok

Resolved2026-09-08 20:26 UTC

This incident has been resolved.

Monitoring2026-09-08 19:37 UTC

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.

Investigating2026-09-08 19:30 UTC

We are continuing to investigate this issue.

Investigating2026-09-08 19:29 UTC

Customer endpoints using traffic policy are erroneously being flagged as hitting limits. The ngrok engineering team is currently working to resolve this issue.

Investigating2026-09-08 19:01 UTC

We are currently investigating an issue preventing some customers from logging in to dashboard.ngrok.com

Affected components

1
Dashboard (https://dashboard.ngrok.com)

ngrok in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 34 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 h 27 min
median 1 h 34 min
90 days agoToday

Other ngrok incidents

All incidents

ngrok·SSO session validation errors on dashboard.ngrok.com

This incident has been resolved.

Resolvedresolved 45 d ago

ngrok·Error when signing in via SSO

This incident has been resolved.

Resolvedresolved 54 d ago

ngrok·New accounts or newly created authtokens are not able to connect

This incident has been resolved.

Resolvedresolved 59 d ago

Follow ngrok

Your coding agent knows when ngrok is down, and tells you when a failure is theirs, not yours. You can also get ngrok incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ngrok" and tell me if ngrok has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=ngrok
Slack
/feed subscribe https://outages.live/feed.xml?providers=ngrok

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane