- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Application UI
- Down Index
- 29of 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 1h 32m it lasted.
Anything that failed between 2024-09-12 19:29 UTC and 2024-09-12 21:01 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
- monitoring
The issue has been identified, and our team are currently monitoring performance.
provider
- resolved
This incident has been resolved, and Close is fully operational.
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 Between 1900 and 2000 UTC on September 12, 2024 the Close app and API were severely degraded due to a partial outage of our back end MongoDB database. The database was restored to normal operation by 2000 UTC without data loss. The Close app and API returned to normal operation by 2000 UTC. ## Root Cause and Resolution At 1900 UTC on September 12, 2024 components of our back end MongoDB database in one of our data centers came under anomalous load and became unresponsive. This resulted in wide spread intermittent disruption to the Close app and API. Once the affected components were identified and restarted performance of the Close app and API returned to normal. We are in the process of deploying a new architecture for this part of our system that will be more resilient to this class of failure. In the meantime we are deploying additional monitoring that will reduce the amount of time required to identify and mitigate such issues going forward. ## Timeline * 1900 UTC: The Close app and API begin to experience elevated error rates * 1904 UTC: Close Engineering is alerted of the elevated error rate by automatic monitoring * 1909 UTC: Close Engineering identifies a network issue affecting one of our data-centers * 1945 UTC: Close Engineering identifies our back end MongoDB database as being critically impaired * 1954 UTC: Close Engineering begins operating on the affected database to restore normal operation * 2001 UTC: Close Engineering completes operations on the affected database * 2001 UTC: The Close app and API returns to normal operation
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-9d610e4655
Is Close still down?
No, this incident was resolved 2024-09-12 21:01 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
1h 32m, from 2024-09-12 19:29 UTC to 2024-09-12 21:01 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.