- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Down Index
- 18of 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 51m it lasted.
Anything that failed between 2025-05-14 15:47 UTC and 2025-05-14 16: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 4
- investigating
We've identified an issue with our webhook processing system. Webhooks may be delayed up to twenty minutes. Updates will be posted as they are available.
provider
- identified
This issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-1861fda733
Is Close still down?
No, this incident was resolved 2025-05-14 16:39 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
51m, from 2025-05-14 15:47 UTC to 2025-05-14 16: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.