Skip to main content
Menu
ngrok

Incident

OAuth, OIDC, and SAML modules for Edges degraded

Partial outage Lasted 26m · started · ngrok's page

DWN-958ea70ed3

Level
confirmed
Worst impact
Partial outage
Components
Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Regions
eu, us
Down Index
34of 100

What to do

  • Check whether you use ngrok Region - AP, Region - AU, Region - EU, Region - IN and 4 more in eu, us. Check your stack

    Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 26m it lasted.

    Anything that failed between 2024-02-07 19:43 UTC and 2024-02-07 20:09 UTC may need a replay.
  • Subscribe to ngrok's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=ngrok works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from ngrok 4

  1. identified

    We have identified an issue with the following Edge modules that may be impacting customers' ability to access content served by the Edge: OAuth, OIDC, and SAML. We are rolling out a fix and monitoring. This issue started approximately ten minutes ago.

    provider

  2. monitoring

    Fixes are rolled out. The team will continue monitoring to confirm a full recovery.

    provider

  3. monitoring

    Customers using SAML modules may in rare cases need to clear cookies if you are seeing BAD REQUEST errors on login.

    provider

  4. resolved

    The system should be recovered for all users.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-958ea70ed3

Is ngrok still down?

No, this incident was resolved 2024-02-07 20:09 UTC. For ngrok's live state, see https://down.guide/providers/ngrok.

How long did it last?

26m, from 2024-02-07 19:43 UTC to 2024-02-07 20:09 UTC, by the times ngrok posted.

What was affected?

ngrok named Region - AP, Region - AU, Region - EU, Region - IN and 4 more in eu, us.

What caused it?

ngrok hasn't published a root cause. If it does, it shows here.

Where does this come from?

ngrok's official status page, https://status.ngrok.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.