ngrok Outage History
13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded ngrok Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 17, 2026 | SSO session validation errors on dashboard.ngrok.comThis incident has been resolved. | 5h 26m | Resolved |
| Sep 8, 2026 | Error when signing in via SSOThis incident has been resolved. | 1h 42m | Resolved |
| Sep 8, 2026 | Endpoints using traffic policies are erroneously hitting limitsThis incident has been resolved. | 1h 24m | Resolved |
| Sep 3, 2026 | New accounts or newly created authtokens are not able to connectThis incident has been resolved. | 36 min | Resolved |
| Sep 1, 2026 | User invites disruptionBetween August 28 and September 1, people invited to an ngrok account couldn't accept the invitation. The invitation link returned an error instead of signing the user in. An authentication change shipped on August 28… | -5900 min | Resolved |
| Jun 18, 2026 | Delays issuing certificatesThis incident has been resolved. | 8h 48m | Resolved |
| May 15, 2026 | SSO Login to the ngrok Dashboard is currently redirecting back to the login pageThis incident has been resolved. | 23 min | Resolved |
| May 8, 2026 | Delay in generating and renewing certificates for custom domainsThis has been resolved | 2h 8m | Resolved |
| Apr 28, 2026 | Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.Agent version 3.39.1 is now available in the Microsoft Store. | 1h 59m | Resolved |
| Mar 31, 2026 | Download of the ngrok binary are returning 500 errorsThis incident has been resolved. | 38h 31m | Resolved |
| Mar 6, 2026 | Mac OS Agent Download is currently brokenThis incident has been resolved. | 14 min | Resolved |
| Jan 12, 2026 | Slowness in Traffic Inspector Data ViewingThis incident has been resolved. | 2h 3m | Resolved |
| Nov 26, 2025 | Intermittent issue downloading the ngrok agentThis incident has been resolved. | 2h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next ngrok incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This ngrok Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before ngrok acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single ngrok outage in this window ran 1d 14h, against a mean recovery of 5h 29m. If you depend on ngrok in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.