- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI, Indexing, API, Querying
- Regions
- us
- Down Index
- 21of 100
What to do
Check whether you use Close Application UI, Indexing, API, Querying in us. 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 55m it lasted.
Anything that failed between 2025-02-14 21:11 UTC and 2025-02-14 22:05 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 5
- 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 and a fix is being implemented. Search indexing may be delayed for some customers.
provider
- monitoring
A fix has been implemented and we are monitoring the results. Search indexing may be delayed for some users.
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 On February 14th, 2025 for two and a half hours \(between 19:50 UTC and 22:00 UTC\) some users saw outdated data in search results and smart views. No data was lost during the outage. ## Root Cause and Resolution A software update introduced malformed data to our Search platform that disrupted updates to our Search database. Close Engineering reverted the change and deleted the malformed data, which allowed the platform to resume processing updates to our Search database. The processing backlog was cleared by 22:00 UTC when full functionality was restored. We are implementing a new set of metrics and alerts that will help us identify this kind of failure more quickly. We are also enhancing the Search platform to better identify and discard malformed data to prevent similar incidents from occurring. ## Timeline All times are in UTC and events take place on 2025-02-14. * 19:50: A software update is deployed that sends malformed data to our search platform. * 20:33: Close Engineering is notified of an elevated error rate on the search platform and start investigating. * 21:04: Root cause is identified and work starts on a fix. * 21:40: The issue is resolved and all data is up-to-date.
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-237bc45d37
Is Close still down?
No, this incident was resolved 2025-02-14 22:05 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
55m, from 2025-02-14 21:11 UTC to 2025-02-14 22:05 UTC, by the times Close posted.
What was affected?
Close named Application UI, Indexing, API, Querying in us.
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.