- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Application UI, API
- Down Index
- 29of 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 56m it lasted.
Anything that failed between 2023-09-05 16:08 UTC and 2023-09-05 17:04 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
- identified
Customers may be experiencing elevated error rates. The root cause has been identified. A fix is being deployed.
provider
- monitoring
The fix has been deployed. The Close application is now functioning normally. Close Engineering is continuing to monitor application performance.
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 Close users experienced elevated error rates from 16:00 until 16:16 UTC on September 5, 2023. During this time requests may have presented an error or timed out. ## Root Cause and Resolution At 16:00 UTC on September 5, 2023 a version of the Close app with a major performance issue was deployed to production. This resulted in degraded performance for all customers from 16:00 until 16:16 UTC. Close Engineering deployed a new version of the the Close app that did not have the performance issue at 16:16 UTC. Application performance then returned to normal. Close Engineering is working on a new set of pre-deployment tests that will prevent similar performance issues from being introduced in the future. ## Timeline * 2023-09-05 16:00 - A new version of the Close app is published. * 2023-09-05 16:03 - Close Engineering becomes aware of degraded performance of the Close application. * 2023-09-05 16:05 - Close Engineering reverts to the last working version of the Close application. * 2023-09-05 16:16 - The working version of the Close application is deployed. Performance recovers.
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-d4f7c47a3b
Is Close still down?
No, this incident was resolved 2023-09-05 17:04 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
56m, from 2023-09-05 16:08 UTC to 2023-09-05 17:04 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.