- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI, API
- Down Index
- 19of 100
What to do
Check whether you use Close Application UI, 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 54m it lasted.
Anything that failed between 2023-09-15 14:37 UTC and 2023-09-15 15:31 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 7
- investigating
We are currently investigating this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
A fix has been implemented. The Close application and API are fully functional. We expect full recovery of background task processing performance in the next 15 minutes.
provider
- resolved
This incident has been resolved.
provider
- postmortem
Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Our processing of background tasks was delayed between 13:30 and 15:30 UTC on September 15, 2023. Some customers may have noticed the Close Application taking longer than normal to sync data from third parties like Zoom or Calendly. Inbox notifications may have been delayed. Some Power Dialer sessions may also have been impacted. No data was lost during this incident. ## Root Cause and Resolution At 13:25 UTC on September 15, 2023 a new version of the Close Application was deployed to production. This change introduced a bug into our background task processing system that prevented it from processing new work. By 14:35 Close Engineering deployed a a fix and performance began to recover. The Close Application completely recovered by 15:30 UTC. To prevent similar issues from happening in the future, Close Engineering will upgrade our background task processing system to better isolate workloads that could potentially break. ## Timeline * 13:25 UTC - A new version of the Close app is published. * 13:39 UTC - Close Engineering becomes aware of a problem with background task processing and takes steps to remediate. * 14:35 UTC - Close Engineering deploys a fixed version of the Close application. Performance begins to recover. * 15:30 UTC - The Close Application is fully recovered and performing normally.
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-ac6077f1fb
Is Close still down?
No, this incident was resolved 2023-09-15 15:31 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
54m, from 2023-09-15 14:37 UTC to 2023-09-15 15:31 UTC, by the times Close posted.
What was affected?
Close named Application UI, 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.