Is ngrok down?
Vendor reports no incidentWhat ngrok reports
ngrok reports no incident on its status page.
As of the last successful poll, 2026-11-05 14:14 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 5 minutes ago
Our checks of ngrok pass from all 4 regions we check.
As of Nov 5, 2026, 2:20 PM UTC, RealUptime's checks of ngrok passed in all 4 regions that returned a reading.
ngrok reports: All systems operational (“All Systems Operational”)
ngrok's own component breakdown, as they publish it
- Dashboard (https://dashboard.ngrok.com)Operational
- Region - APOperational
- Region - APOperational
- API (https://api.ngrok.com)Operational
- Region - AUOperational
- Region - AUOperational
- Region - EUOperational
- Region - EUOperational
- Region - INOperational
- Region - INOperational
- Region - JPOperational
- Region - JPOperational
- ngrok Agent and LibrariesOperational
- EventsOperational
- Region - SAOperational
- Region - SAOperational
- CertificatesOperational
- Region - USOperational
- Region - USOperational
- Region - us-cal-1Operational
- Region - us-cal-1Operational
- ngrok.comOperational
These are ngrok's components, named and scored by ngrok. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is ngrok's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
ngrok response time, by region
Check your own site while you wait on ngrok
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not ngrok. It cannot diagnose ngrok's own systems.
What we measured, function by function
ngrok answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
Email me when ngrok reports an incident on its status page, and again when it reports it resolved.
Get an email when ngrok reports an incident
Email me when ngrok reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 880msstatus code: 400checked: Nov 5, 2026, 2:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach ngrok normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 585msstatus code: 400checked: Nov 5, 2026, 2:18 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach ngrok normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeChecks passinglatency: 730msstatus code: 400checked: Nov 5, 2026, 2:15 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach ngrok normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1179msstatus code: 400checked: Nov 5, 2026, 2:14 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach ngrok normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionngrok is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using ngrok, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for ngrok yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring ngrok since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for ngrok covering any window you pick, with our check readings and ngrok's own claim at the time, side by side.
Full check history for ngrok: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/ngrok)<a href="https://realuptime.io/outages/ngrok"><img src="https://realuptime.io/outages/ngrok/badge.svg?days=30" alt="ngrok uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is ngrok down?", https://realuptime.io/outages/ngrok. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.
Host checked: api.ngrok.com