Loading status…
ngrok status · Developer Tools · checked (2s ago)
No — ngrok is not down. All ngrok systems are reported operational.
According to ngrok's official status page, ngrok was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, ngrok's feed reported no outage in 100.00% of our checks.
Everything above is read from ngrok's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported ngrok in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
ngrok puts a public URL in front of something running on your machine or in a private network — a tunnel for webhook development, demos and, increasingly, production ingress. The value is entirely in the hosted edge, so when ngrok is unavailable the local process is fine and simply unreachable.
The status page reports the tunnel edges by region alongside the dashboard and API. Regional reporting is what matters here: your agent connects to a specific region, so an incident in one says nothing about another. Free-tier and paid edges share the same infrastructure and are not reported separately.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where ngrok's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days ngrok was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of ngrok's status endpoint.
ngrok has published 14 incidents in the last 12 months, newest first. Only what ngrok posted itself — not every problem users hit.
resolved · Sep 17, 03:10 PM (2d ago)
resolved · Sep 8, 08:05 PM (11d ago)
resolved · Sep 8, 07:01 PM (11d ago)
resolved · Sep 3, 11:34 PM (16d ago)
resolved · Aug 28, 04:00 PM (22d ago)
resolved · Jun 18, 08:16 PM (93d ago)
resolved · May 15, 12:49 AM (128d ago)
resolved · May 8, 08:12 PM (134d ago)
resolved · Apr 28, 02:29 PM (144d ago)
resolved · Mar 31, 03:12 AM (173d ago)
resolved · Mar 6, 05:11 PM (197d ago)
resolved · Jan 12, 05:01 PM (250d ago)
resolved · Nov 26, 06:28 PM (297d ago)
resolved · Oct 4, 12:35 AM (351d ago)
Free ngrok URLs change on every restart, and a webhook still pointed at the old one fails with nothing wrong anywhere. Agent version deprecation is enforced server-side and disconnects old clients with an error that looks like an outage. Connection limits and the interstitial warning page on free accounts also break automated callers that would otherwise work.
