Is there an Close outage?
Close status: Systems Active
Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Close and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Close and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Close.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API | Active |
| Application UI | Active |
| Public Website | Active |
| Support Center | Active |
| Active | |
| Sending | Active |
| Syncing | Active |
| Phone | Active |
| Call recording (primary) | Active |
| Call Recording (secondary) | Active |
| Dialer | Active |
| Downstream telephony carriers (primary) | Active |
| Downstream telephony carriers (secondary) | Active |
| Incoming Calls | Active |
| Outgoing Calls | Active |
| Outgoing Calls - Infrastructure (Twilio conference calling API) | Active |
| Outgoing Calls - Infrastructure (Twilio REST API) | Active |
| Outgoing Calls - Infrastructure (Twilio TwiML) | Active |
| Phone Service | Active |
| SIP & SIP Registrar (secondary) | Active |
| SMS (primary) | Active |
| Telephony provider connectivity (primary) | Active |
| Search | Active |
| Indexing | Active |
| Querying | Active |
View the latest incidents for Close and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Sept. 25, 2024, 2:40 p.m.
Description: 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
Status: Postmortem
Impact: Major | Started At: Sept. 12, 2024, 7:29 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 26, 2024, 9:52 p.m.
Description: 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 API endpoints and application areas backed by Search infrastructure - leads, contacts, opportunities list pages, and certain reporting pages were inaccessible for 20 minutes. ## Root Cause and Resolution As part of an ongoing effort to increase security of Close application, we shipped a change to how authentication is handled between the application and internal search clusters. However, a certain kind of authentication exchange wasn’t handled correctly, which caused most of the requests to Search infrastructure to fail in production. We have reverted the change, and will be improving our testing setup to catch these issues during development, as well as deployment and monitoring systems to catch production issues earlier. ## Timeline * 10:20 UTC - An engineer rolls out an incorrect change in how authentication handled between application and internal search clusters. * 10:21 UTC - Monitoring systems alert on-call engineer * 10:33 UTC - The change was reverted * 10:40 UTC - The application functionality fully recovered
Status: Postmortem
Impact: None | Started At: May 24, 2024, 11:13 a.m.
Description: 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 API endpoints and application areas backed by Search infrastructure - leads, contacts, opportunities list pages, and certain reporting pages were inaccessible for 20 minutes. ## Root Cause and Resolution As part of an ongoing effort to increase security of Close application, we shipped a change to how authentication is handled between the application and internal search clusters. However, a certain kind of authentication exchange wasn’t handled correctly, which caused most of the requests to Search infrastructure to fail in production. We have reverted the change, and will be improving our testing setup to catch these issues during development, as well as deployment and monitoring systems to catch production issues earlier. ## Timeline * 10:20 UTC - An engineer rolls out an incorrect change in how authentication handled between application and internal search clusters. * 10:21 UTC - Monitoring systems alert on-call engineer * 10:33 UTC - The change was reverted * 10:40 UTC - The application functionality fully recovered
Status: Postmortem
Impact: None | Started At: May 24, 2024, 11:13 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
