- Level
- confirmed
- Worst impact
- Partial outage
- Components
- SMS
- Down Index
- 31of 100
What to do
Check whether you use Close SMS. 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 2h 37m it lasted.
Anything that failed between 2023-05-04 15:05 UTC and 2023-05-04 17:42 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 2
- investigating
Our telephony provider, Twilio, is currently experiencing issues on their side that are impacting Close users. We're in contact with them about these issues and they are currently working on a fix. You can follow along with Twilio's status updates at: https://status.twilio.com/ We will update this page as soon as we have more information from Twilio.
provider
- 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-4806c4f063
Is Close still down?
No, this incident was resolved 2023-05-04 17:42 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
2h 37m, from 2023-05-04 15:05 UTC to 2023-05-04 17:42 UTC, by the times Close posted.
What was affected?
Close named SMS.
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.