- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI, API
- Down Index
- 21of 100
What to do
Check whether you use Close Application UI, API. 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 59m it lasted.
Anything that failed between 2025-11-01 08:55 UTC and 2025-11-01 10:53 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're currently investigating a slowdown in application performance. You may experience delays in loading pages. The engineering team is currently looking into resolving this as quickly as possible.
provider
- identified
The issue has been identified and a fix is being implemented.
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-f989643e2f
Is Close still down?
No, this incident was resolved 2025-11-01 10:53 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 59m, from 2025-11-01 08:55 UTC to 2025-11-01 10:53 UTC, by the times Close posted.
What was affected?
Close named Application UI, API.
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.