ngrok: Delayed certificate provisioning for wildcard domains created in the last two days

What to do

Check whether you use ngrok Certificates. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 4h 2m it lasted.
Anything that failed between 2024-07-26 19:34 UTC and 2024-07-26 23:36 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.

investigatingJul 26, 2024, 7:34 PM UTC
We are currently investigating this issue.
provider
identifiedJul 26, 2024, 7:36 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringJul 26, 2024, 8:52 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedJul 26, 2024, 11:36 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is ngrok still down?

No, this incident was resolved 2024-07-26 23:36 UTC. For ngrok's live state, see https://down.guide/ngrok.

How long did it last?

4h 2m, from 2024-07-26 19:34 UTC to 2024-07-26 23:36 UTC, by the times ngrok posted.

What was affected?

ngrok named Certificates.

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.