Skip to main content
Vendor reliability

Vendor record

ngrok

Vendor reports Operational

Checked

Front door check counts and ngrok’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented ngrok endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.ngrok.com
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every ngrok product, region or your app worked.

How we count front door checks

ngrok says

Incident posts from ngrok’s status page, with its titles, impact levels and times. They say what ngrok chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

0

incidents ngrok posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • SSO session validation errors on dashboard.ngrok.com

    Minor

    Started, per ngrok

    Closed in our record(5h 29m)

    ngrok’s post
  • Error when signing in via SSO

    Major

    Started, per ngrok

    Closed in our record(1h 44m)

    ngrok’s post
  • Endpoints using traffic policies are erroneously hitting limits

    Major

    Started, per ngrok

    Closed in our record(1h 28m)

    ngrok’s post
  • New accounts or newly created authtokens are not able to connect

    Not specified

    Started, per ngrok

    Closed in our record(45m)

    ngrok’s post
  • Delays issuing certificates

    Minor

    Started, per ngrok

    Closed in our record(8h 49m)

    ngrok’s post
4 older records
  • SSO Login to the ngrok Dashboard is currently redirecting back to the login page

    Minor

    Started, per ngrok

    Closed in our record(30m)

    ngrok’s post
  • Delay in generating and renewing certificates for custom domains

    Minor

    Started, per ngrok

    Closed in our record(2h 17m)

    ngrok’s post
  • Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.

    Major

    Started, per ngrok

    Closed in our record(2h)

    ngrok’s post
  • Download of the ngrok binary are returning 500 errors

    Major

    Started, per ngrok

    Closed in our record(1d 14h)

    ngrok’s post

Your code, your dependencies

See which of your code paths call ngrok

Connect GitHub or GitLab to find where your public or private repository uses ngrok. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add ngrok status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · ngrokStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/ngrok?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="ngrok status badge"></iframe>

Frequently Asked Questions

Is ngrok currently down?

ngrok's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did ngrok last have an outage?

The most recent closed incident record began 29 days ago and spans 5h 29m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for ngrok?

No. CheckUpstream checks ngrok’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor ngrok in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track ngrok?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.