- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Application UI, Syncing, API, Calendar - Syncing
- Down Index
- 31of 100
What to do
Check whether you use Close Application UI, Syncing, API, Calendar - Syncing. 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 1h 3m it lasted.
Anything that failed between 2025-02-11 22:31 UTC and 2025-02-11 23:34 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 have become aware of degraded performance of the Close system. We are actively triaging the issue. Updates will be posted as they become available.
provider
- identified
The issue has been identified. A fix is being rolled out to our production system.
provider
- monitoring
A fix has been implemented. We are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
Our App UI and API have returned to normal performance. Our email and calendar syncing systems are operational but delayed. We are continuing to monitor for further issues.
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 Beginning 22:00 UTC until 23:03 UTC on Tuesday February 11, 2025 users of the Close App experienced significantly degraded performance and an elevated error rate. This included slow page loads, long API response times, delayed email syncing, and delayed calendar syncing for all customers. ## Root Cause and Resolution At 22:00 UTC on Tuesday February 11, 2025 a change was deployed to the production environment of the Close system. This change introduced a poorly optimized database query. This caused our primary back end database to become overloaded and unstable. Close Engineering identified and removed the offending database query by 22:47 UTC. Performance began to gradually return to baseline, fully recovering by 23:03 UTC. ## Timeline * 22:00 UTC - A change is deployed to production introducing a poorly optimized database query * 22:01 UTC - Load on our primary back end database begins to climb * 22:06 UTC - Load on our primary back end database breaches critical thresholds alerting Close Engineering * 22:17 UTC - Close Engineering isolates the poorly optimized database query and begins to remove it from production * 22:47 UTC - Removal of the poorly optimized database query completes * 23:03 UTC - Close system performance returns to baseline
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-6e1d1a4bef
Is Close still down?
No, this incident was resolved 2025-02-11 23:34 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 3m, from 2025-02-11 22:31 UTC to 2025-02-11 23:34 UTC, by the times Close posted.
What was affected?
Close named Application UI, Syncing, API, Calendar - Syncing.
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.