- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 100
What to do
Check whether your product depends on Close. 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 1h 13m it lasted.
Anything that failed between 2025-11-05 18:42 UTC and 2025-11-05 19:56 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
- investigating
We are receiving an increased number of reports that users are unable to use calling when using the Desktop Application. Calling within the browser works fine. We're investigating.
provider
- identified
We have identified the issue and are actively working on a fix.
provider
- resolved
The issue has been resolved. Please reach out to support@close.com if you continue to have calling issues after refreshing.
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-dea6194797
Is Close still down?
No, this incident was resolved 2025-11-05 19:56 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 13m, from 2025-11-05 18:42 UTC to 2025-11-05 19:56 UTC, by the times Close posted.
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.