- Level
- confirmed
- Worst impact
- Degraded
- Components
- Indexing
- Down Index
- 21of 100
What to do
Check whether you use Close Indexing. 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 48m it lasted.
Anything that failed between 2026-04-23 16:56 UTC and 2026-04-23 19:44 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 5
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and the fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We've deployed a fix, we're continuing to see improvements in overall system performance, we expect recovery slowly over the next several minutes.
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-4a6903198b
Is Close still down?
No, this incident was resolved 2026-04-23 19:44 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
2h 48m, from 2026-04-23 16:56 UTC to 2026-04-23 19:44 UTC, by the times Close posted.
What was affected?
Close named Indexing.
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.