CheckUpstream measured ngrok at 100.000% availability across 2038 independent checks (global · api). 5 incidents were recorded in the past 12 months; the most recent resolved 74 days ago after 9 hours. Status signals are polled from ngrok's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2038 · p95 425ms (30d)
Share of our own checks against ngrok endpoints that returned ngrok's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
ngrok posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
Fewer incidents in the last 30 days than 55% of 232 tracked services.
Share of each window with no impact declared by ngrok
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.328%
1y
99.669%
Does ngrok actually matter to you?
A ngrok outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Jun 18, 20:16 UTC · resolved in 8h 49m · Resolved
May 15, 00:49 UTC · resolved in 30m · Resolved
May 8, 20:12 UTC · resolved in 2h 17m · Resolved
Live ngrok status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/ngrok)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
ngrok is currently Operational. CheckUpstream tracks ngrok in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
ngrok's last resolved incident started 74 days ago and lasted 8h 49m (degraded performance).
Looking for the live "is ngrok down" view? See the ngrok Live status page.
Apr 28, 14:29 UTC · resolved in 2h · Resolved
ngrok's 30-day measured availability is 100.000%, from CheckUpstream's own probes against ngrok endpoints. It is the share of checks that returned the expected response, not a figure taken from ngrok's status page.
Sign up to CheckUpstream and add ngrok to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll ngrok's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.