- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI, Indexing, API, Querying
- Down Index
- 21of 100
What to do
Check whether you use Close Application UI, Indexing, API, Querying. 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 46m it lasted.
Anything that failed between 2024-11-04 08:45 UTC and 2024-11-04 09:31 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 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
- identified
We have identified a problem with one of our search databases and have initiated a failover.
provider
- monitoring
The failover succeeded. The Indexer is still catching up with the backlog of events. We are monitoring the situation and estimate that everything will be back to normal within 3-5 minutes.
provider
- resolved
The issue is resolved now.
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 For some clients changes performed in Close took longer than usual to be reflected in our search functionality on November 4th from 8:06 to 9:31 UTC. ## Root Cause and Resolution We are in the process of moving data to a new search infrastructure. Due to encountering a number of unexpectedly large objects during this process the indexing of new changes got delayed. We adjusted the indexing process to truncate the overly large objects to avoid encountering this in the future.
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-e4bd25e549
Is Close still down?
No, this incident was resolved 2024-11-04 09:31 UTC. For Close's live state, see https://down.guide/close.
How long did it last?
46m, from 2024-11-04 08:45 UTC to 2024-11-04 09:31 UTC, by the times Close posted.
What was affected?
Close named Application UI, Indexing, API, Querying.
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.