- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 20of 100
What to do
Check whether you use Close 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 54m it lasted.
Anything that failed between 2026-06-29 17:46 UTC and 2026-06-29 19:39 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 have become aware of degraded processing of background tasks in the Close system. We are currently investigating the issue.
provider
- monitoring
We have identified the root cause and deployed a remediation. Background task processing performance is improving. Some customers may still see delayed processing of background tasks. Close Engineering is monitoring for improved performance.
provider
- resolved
This incident has been resolved. Background tasks are processing normally.
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-1fbf59badf
Is Close still down?
No, this incident was resolved 2026-06-29 19:39 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 54m, from 2026-06-29 17:46 UTC to 2026-06-29 19:39 UTC, by the times Close posted.
What was affected?
Close named 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.