ngrok reported "SSO session validation errors on dashboard.ngrok.com" on its status page at 2026-09-17 15:10 UTC.

ngrok lists these components: Dashboard (https://dashboard.ngrok.com).

When did the incident start and end?

It started at 2026-09-17 15:10 UTC and ended at 2026-09-17 20:37 UTC. It lasted 5 h 27 min.

How do I get alerts for ngrok?

Subscribe to the ngrok live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of ngrok. outages.live reads it every few minutes and keeps every update.

ngrokIncident · 2026-09-17 15:10 UTC

SSO session validation errors on dashboard.ngrok.com

ResolvedOfficial update

This incident has been resolved.

The latest update from ngrok.

State

Resolved

Started

45 d ago

2026-09-17 15:10 UTC

Lasted

5 h 27 min

until 2026-09-17 20:37 UTC

Worst impact

Degraded

Timeline

3 updates

15:1016:3217:5419:1520:37

DegradedUpdate postedTimes in UTC

Investigating

26 min 8%

Monitoring

5 h 1 min 92%

Updates

Times in UTC

As posted by ngrok

Resolved2026-09-17 20:37 UTC

This incident has been resolved.

Monitoring2026-09-17 15:36 UTC

We've identified an individual host that was experiencing networking issues and removed it from our infrastructure.

Investigating2026-09-17 15:10 UTC

Users logging into dashboard.ngrok.com via SSO are encountering errors related to session validation.

Affected components

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

ngrok in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 34 min

This incident

3.5× 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·Error when signing in via SSO

This incident has been resolved.

Resolvedresolved 54 d ago

ngrok·Endpoints using traffic policies are erroneously hitting limits

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