Is ngrok Down?

No — ngrok is up

ngrok's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 417 ms

Right now

The verdict is the worse of these two. How we decide

ngrok's status page

status.ngrok.com · read 3 minutes ago · checked every 3 minutes

Operational

ngrok's components, as its status page reports them
Component	Status
Dashboard (https://dashboard.ngrok.com)	Operational
API (https://api.ngrok.com)	Operational
ngrok Agent and Libraries	Operational
Events	Operational
Certificates	Operational
ngrok.com the service itself	Operational
Region - AP	Operational
Region - SA	Operational
Region - us-cal-1	Operational
Region - AP	Operational
Region - SA	Operational
Region - us-cal-1	Operational

10 locations All operational

Open their status page

FlareWarden checks

ngrok.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 417 ms
Checked: 5 hours ago

By region

Chicago reachable, 387 ms
London reachable, 303 ms
Los Angeles reachable, 391 ms
San Jose reachable, 235 ms
Singapore reachable, 626 ms
Sydney reachable, 632 ms
Tokyo reachable, 347 ms
Toronto reachable, 418 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	43 ms	10 ms	15 ms	346 ms
London	58 ms	14 ms	20 ms	243 ms
Los Angeles	152 ms	11 ms	17 ms	345 ms
San Jose	66 ms	2 ms	8 ms	222 ms
Singapore	139 ms	4 ms	8 ms	613 ms
Sydney	200 ms	2 ms	8 ms	624 ms
Tokyo	135 ms	2 ms	8 ms	335 ms
Toronto	55 ms	22 ms	28 ms	327 ms

We check that ngrok.com loads, not every feature behind it. Test it yourself

History

Incidents ngrok reported

Since Oct 22, 15 days · from status.ngrok.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

ngrok website availability

Measured by FlareWarden · ngrok.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 579ms

Last 30 days

77-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of ngrok.com from multiple regions every 6 hours. ngrok's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What ngrok does

ngrok exposes services running on a laptop or inside a private network at a public URL, without opening firewall ports. Developers use it to receive webhooks against local code and to demonstrate work in progress, and teams run it as production ingress for services that have no public address of their own.

What an outage looks like

The agent fails to start or exits reporting it cannot reach the ngrok service. Existing tunnels stay listed but return errors to visitors instead of reaching the local process. Webhook senders begin timing out and start their own retry cycles. The dashboard and API become unreachable so new tunnels cannot be created, even while established ones continue serving.

What to do about it

status.ngrok.com divides its regions into two groups, Agent Connectivity and Endpoint Connectivity, which is the distinction that matters: whether new agents can connect is tracked apart from whether existing endpoints still carry traffic. Dashboard, API, the agent libraries, Events and Certificates each report separately. If only Agent Connectivity is affected, leave running tunnels alone rather than restarting them, because a restart cannot reconnect.

Is it down for everyone, or just you?

If this page says ngrok is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

ngrok outage FAQ

My tunnel died and will not restart. Is ngrok down?

Look at Agent Connectivity for your region rather than the overall status. That component covers an agent's ability to establish a session, and when it is degraded a tunnel that is already running keeps working while any restart fails. This is the one situation where restarting is actively harmful, since it destroys a working session you cannot recreate.

Are webhooks lost while ngrok is down?

That depends on the sender, not on ngrok. Most webhook providers retry on failure over a period of hours, so deliveries during a short incident usually arrive afterwards. Providers that do not retry drop them permanently. Check the sending service's retry policy, and where one exists, look for a manual redelivery option once your tunnel is back.

Is it ngrok or the service on my machine?

Request your local service directly on its own port, bypassing the tunnel. If it answers there but the public URL returns an error, the fault is in the tunnel path. The ngrok agent also reports connection state in its own output, which distinguishes a failed local target from a failed connection to ngrok.

Does an outage affect every region at once?

Not usually. ngrok reports connectivity per region, covering the United States, Europe, Asia-Pacific, Australia, India, Japan and South America separately, within both the agent and endpoint groups. An incident in one region leaves tunnels elsewhere working, so a colleague in another country may see no problem with the same setup.

Can I keep working during an ngrok outage?

For local development, point the webhook sender at a different ingress or capture requests locally and replay them later. For anything depending on a fixed public URL, there is no quick substitute, because the URL itself is the thing that is unavailable. That dependency is worth knowing about before an incident rather than during one.

How we measure this

We request ngrok's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where ngrok publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of ngrok itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when ngrok goes down

We check ngrok every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required