outages.live
Live

ngrok

ngrok is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

1 h 34 min

Longest incident

5 h 27 min

Components

22
Dashboard (https://dashboard.ngrok.com) Operational
90 days ago2 days with an incidentToday
API (https://api.ngrok.com) Operational
90 days agoNo incidentsToday
ngrok Agent and Libraries Operational
90 days agoNo incidentsToday
Events Operational
90 days agoNo incidentsToday
Certificates Operational
90 days agoNo incidentsToday
ngrok.com Operational
90 days agoNo incidentsToday

Agent Connectivity

Region - AP Operational
90 days agoNo incidentsToday
Region - AU Operational
90 days agoNo incidentsToday
Region - EU Operational
90 days agoNo incidentsToday
Region - IN Operational
90 days agoNo incidentsToday
Region - JP Operational
90 days agoNo incidentsToday
Region - SA Operational
90 days agoNo incidentsToday
Region - US Operational
90 days agoNo incidentsToday
Region - us-cal-1 Operational
90 days agoNo incidentsToday

Endpoint Connectivity

Region - AP Operational
90 days agoNo incidentsToday
Region - AU Operational
90 days agoNo incidentsToday
Region - EU Operational
90 days agoNo incidentsToday
Region - IN Operational
90 days agoNo incidentsToday
Region - JP Operational
90 days agoNo incidentsToday
Region - SA Operational
90 days agoNo incidentsToday
Region - US Operational
90 days agoNo incidentsToday
Region - us-cal-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 17, 2026

Duration5 h 27 min15:10 to 20:37SSO session validation errors on dashboard.ngrok.comDegraded

This incident has been resolved.

Sep 8, 2026

Duration1 h 43 min20:05 to 21:48Error when signing in via SSOPartial outage

This incident has been resolved.

Duration1 h 25 min19:01 to 20:26Endpoints using traffic policies are erroneously hitting limitsPartial outage

This incident has been resolved.

Sep 3, 2026

Duration36 min23:34 to 00:11New accounts or newly created authtokens are not able to connectNotice

This incident has been resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane