outages.live
Live
ngrokIncident ·

Kubernetes bindings certs expired

Partial outageOfficial update
0

The ngrok Agent and Libraries have a partial outage. Certificates for the Kubernetes bindings service expired on 11/15/2026, and traffic through the bindings service is blocked until new certificates are added. ngrok is investigating.

State

Investigating

Started

Ongoing for

26 min

Worst impact

Partial outage

Timeline

1 update
17:2817:3517:4117:4717:54
Partial outageUpdate postedTimes in UTC

Investigating

26 min 100%

Updates

Times in UTC

As posted by ngrok

Investigating

The certs for the kubernetes bindings service are expired on 11/15/2026. Traffic through the bindings service will be blocked until new certs are added.

Affected components

1
ngrok Agent and Libraries

ngrok in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

5

Median duration

1 h 34 min

This incident

72% shorter than 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.

Resolved

ngrok·Error when signing in via SSO

This incident has been resolved.

Resolved

ngrok·Endpoints using traffic policies are erroneously hitting limits

This incident has been resolved.

Resolved

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

This incident has been resolved.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane