Live / ngrok / Incident
ngrok: Kubernetes bindings certs expired
ngrok · ngrok.comMajor incidentResolved2026-11-15 19:33 UTC
Public — what happened
Summary
ngrok reported a major incident beginning at 17:28 UTC on November 15, 2026, involving its Kubernetes bindings service. The company said security certificates for the service had expired, which meant traffic going through it was blocked. By 18:30 UTC ngrok said it had put new certificates in place and traffic was recovering while it watched to confirm. The incident was marked resolved at 19:33 UTC.
Affected
ngrok Agent and Libraries
Timeline
- Started — 2026-11-15 17:28 UTC
- Investigating — 2026-11-15 17:28 UTC
- Monitoring — 2026-11-15 18:30 UTC
- Resolved — 2026-11-15 19:33 UTC · 2h 05m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach ngrok against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for ngrok: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the ngrok report →
More from ngrok
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.