- Level
- confirmed
- Worst impact
- Degraded
- Components
- Indexing
- Down Index
- 18of 100
What to do
Check whether you use Close Indexing. 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 51m it lasted.
Anything that failed between 2024-11-18 14:57 UTC and 2024-11-18 15:48 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
We are investigating an issue where our Search Indexer's ingestion of new events is delayed. This may result in the latest changes not being reflected on many pages across the application – Leads Search, Contacts Search, Inbox, Opportunities, Reporting, etc.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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 Changes to Lead data in Close were not reflected on search-based pages, including Leads, Inbox, and Reporting pages from 13:40 UTC to 15:05 UTC on Nov 18th 2024. ## Root Cause and Resolution Due to a change in a recent release, we sent bad data to the system that powers our search tools. As a result, this system failed to process any new incoming information and search results became outdated. Once we determined the root cause, we updated the search system to ignore such bad data in the future. Search results are now up-to-date. ## Timeline * 13:40 UTC - bad data gets sent to the system that powers our search * 14:15 UTC - engineers identify the issue * 15:05 UTC - rollout of the fix is complete
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-a2bd1736b3
Is Close still down?
No, this incident was resolved 2024-11-18 15:48 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
51m, from 2024-11-18 14:57 UTC to 2024-11-18 15:48 UTC, by the times Close posted.
What was affected?
Close named Indexing.
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.