Skip to main content
Close

Calling outage

Major outage Lasted 3h 40m · started · Close's page

Level
confirmed
Worst impact
Major outage
Components
Phone Service
Down Index
43of 100

What to do

  • Check whether you use Close Phone Service. 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 3h 40m it lasted.

    Anything that failed between 2024-04-22 14:53 UTC and 2024-04-22 18:33 UTC may need a replay.
  • Subscribe to Close's feed to hear about the next one first. RSS feed

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

Updates from Close 3

  1. investigating

    Our telephony provider, Twilio, is currently experiencing issues on their side that are impacting Close users. We will update this page as soon as we have more information from Twilio.

    provider

  2. monitoring

    A fix has been implemented by Twilio and baseline call functionality has been restored.

    provider

  3. resolved

    This incident has been resolved.

    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-ca78561ee1

Is Close still down?

No, this incident was resolved 2024-04-22 18:33 UTC. For Close's live state, see https://down.guide/close.

How long did it last?

3h 40m, from 2024-04-22 14:53 UTC to 2024-04-22 18:33 UTC, by the times Close posted.

What was affected?

Close named Phone Service.

What caused it?

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

Where does this come from?

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