Skip to content
PulseWatchOUTAGE.INTEL
ngrok logo

Other

Is ngrok down right now?

NormalOfficial status last polled Oct 12, 2026 20:14 UTCngrok.comOfficial status page

Are you on the ngrok team and see something inaccurate? Report it to us. We respond within one business day.

Is ngrok down right now?

No. ngrok has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 20:24 UTC

Normal

ngrok is operating normally

As of Oct 12, 2026 20:24 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 17, 2026 22:20 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for ngrok.

1

Incident days

29

No recorded incident

6h 45m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for ngrok. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

1

Days with incidents

1 incident

Busiest day

6h 45m

Recorded duration

Report volume

0 reports in last 24H

08:15 PM11:45 PM03:15 AM06:45 AM10:15 AM01:45 PM05:15 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

ngrok outage on September 17 6h 44m disruption

Sep 17, 03:35 PM → Sep 17, 10:20 PM · 6h 44m · medium

An incident affecting the ngrok service was detected by automated monitoring systems. The issue began on September 17, 2026, at 15:35 UTC and was resolved on September 17, 2026, at 22:20 UTC.

Duration
6h 44m
tracked by PulseWatch

Impact

During the 6-hour and 44-minute incident, the ngrok service experienced a medium-severity disruption. This incident was identified through automated monitoring and vendor status page updates. No user-reported data was collected for this incident, indicating that any potential impact was not widely reported by users. The disruption was limited to the ngrok service itself.

Incident timeline

  1. Sep 17, 03:35 PM

    PulseWatch detected the incident from automated vendor and probe signals (medium severity)

  2. Sep 17, 03:36 PM

    Status updated: possible issue

  3. Sep 17, 10:20 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 17, 03:35 PM

    ngrok status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.

Reliability

Detected by PulseWatch

30-day uptime

99.06%

90-day uptime

99.69%

Calculated from ngrok's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

ngrok: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/17/2026, 3:35:59 PM · 6h 44m

03:35 PM10:20 PM
Detection9/17/2026, 3:35:59 PM · 25d ago

Detected — medium severity

ngrok: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment ngrok enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

ngrok.com