- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API
- Down Index
- 30of 100
What to do
Check whether you use Close API. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 15m it lasted.
Anything that failed between 2023-03-01 13:24 UTC and 2023-03-01 15: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
Webhook events are being delayed. We are currently investigating this issue.
provider
- monitoring
The issue has been identified, and a fix has been implemented. The event backlog is being processed.
provider
- resolved
The event backlog has been processed.
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-d4a32c36b8
Is Close still down?
No, this incident was resolved 2023-03-01 15:39 UTC. For Close's live state, see https://down.guide/providers/close.
How long did it last?
2h 15m, from 2023-03-01 13:24 UTC to 2023-03-01 15: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.