Is ngrok Down?

No — ngrok is up

Reachable from all 8 checked regions

Average response time: 667ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.ngrok.com

ngrok uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

533ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 31 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

31-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra

233ms

DNS 115ms TCP 2ms TLS 9ms TTFB 221ms

gru

608ms

DNS 210ms TCP 3ms TLS 11ms TTFB 594ms

iad

443ms

DNS 125ms TCP 23ms TLS 29ms TTFB 369ms

jnb

2701ms

DNS 11ms TCP 271ms TLS 278ms TTFB 1887ms

lax

309ms

DNS 49ms TCP 9ms TLS 16ms TTFB 279ms

lhr

221ms

DNS 21ms TCP 14ms TLS 21ms TTFB 179ms

nrt

467ms

DNS 187ms TCP 2ms TLS 12ms TTFB 453ms

ord

358ms

DNS 48ms TCP 9ms TLS 16ms TTFB 327ms

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 18 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.
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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when ngrok goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required