- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 100
What to do
Check whether your product depends on Close. 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 28m it lasted.
Anything that failed between 2025-09-05 10:45 UTC and 2025-09-05 11:13 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 are currently investigating a delay in processing triggers that kick off Workflow actions.
provider
- identified
We have identified the problem as coming from our compute provider, AWS. An unplanned patch to our Event Stream is currently underway.
provider
- resolved
Unplanned patches have been applies and our system has processed through the delayed events.
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-95e4a8a433
Is Close still down?
No, this incident was resolved 2025-09-05 11:13 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
28m, from 2025-09-05 10:45 UTC to 2025-09-05 11:13 UTC, by the times Close posted.
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.