- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI
- Down Index
- 18of 100
What to do
Check whether you use Close Application UI. 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 42m it lasted.
Anything that failed between 2024-10-14 20:32 UTC and 2024-10-14 21:14 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 are currently seeing intermittent issues with Close loading. We will let you know as soon as this is fixed.
provider
- investigating
We are continuing to investigate the issue. We will post updates as they are available.
provider
- monitoring
We have remediated the performance issue affecting some Close customers. The Close App & API should be functioning normally for all users. We will continue to monitor our system's performance.
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-d42444b868
Is Close still down?
No, this incident was resolved 2024-10-14 21:14 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
42m, from 2024-10-14 20:32 UTC to 2024-10-14 21:14 UTC, by the times Close posted.
What was affected?
Close named Application UI.
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.