ngrok Outage History
Uptime record, past incidents, and downtime history for ngrok.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 92% | 25 | 2 |
| April 2026 | 93.3% | 30 | 2 |
| March 2026 | 93.5% | 31 | 2 |
| February 2026 | 100% | 5 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
SSO Login to the ngrok Dashboard is currently redirecting back to the login page
Started: May 15, 12:49 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 15, 1:00 AM
identified
The issue has been identified and a fix is being implemented.
May 15, 12:49 AM
Delay in generating and renewing certificates for custom domains
Started: May 8, 8:12 PM
monitoring
Our provider has fixed their system.
May 8, 9:28 PM
investigating
Our certificate provider has run into an issue and is currently pausing generation and renewal of certificates.
May 8, 8:12 PM
April 2026
Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.
Started: Apr 28, 2:29 PM
monitoring
Agent version 3.39.1 has been released to all channels. Once approved by Microsoft, the new build will be available via the Microsoft Store.
Apr 28, 3:24 PM
identified
We expect a new version of the agent that resolves this issue to be available within the next hour.
Apr 28, 2:44 PM
identified
The issue has been identified and the engineering team is working on the fix.
Apr 28, 2:30 PM
investigating
Users who have installed the ngrok agent via the Microsoft Store on Windows are seeing fatal panics on endpoint startup on the most recent agent version. Non Windows users and Windows users installing via other channels should not be impacted.
Apr 28, 2:29 PM
March 2026
Download of the ngrok binary are returning 500 errors
Started: Mar 31, 3:12 AM
identified
The issue has been identified and a fix is being implemented.
Mar 31, 3:12 AM