Close had 16 outages in the last 2 years totaling 38h 11m of downtime — averaging 0.7 incidents per month.
There were 16 Close outages since September 5, 2025 totaling 38h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are again investigating an elevated number of database failures.
We are continuing to investigate the issue.
We have identified the problem, adjusted our scaling strategy, and are seeing healthy recovery of all systems.
This incident has been resolved.
We have become aware of degraded processing of background tasks in the Close system. We are currently investigating the issue.
We have identified the root cause and deployed a remediation. Background task processing performance is improving. Some customers may still see delayed processing of background tasks. Close Engineering is monitoring for improved performance.
This incident has been resolved. Background tasks are processing normally.
Changes done to CRM data are reflected in search with a delay.
We are continuing to investigate the issue.
We are continuing to investigate the issue. Updates to Close made via the web app and API may take longer than normal to appear in search results.
We are continuing to investigate the issue. Updates to Close made via the web app and API may take longer than normal to appear in search results.
We have implemented a remediation for the delayed search indexing and are monitoring for improvement. Updates to Close made via the web app and API may take longer than normal to appear in search results.
A fix has been implemented and we are monitoring the results. Updates to Close made via the web app and API may take longer than normal to appear in search results.
This incident has been resolved. The Close app and API are now functioning normally.
Some users are experiencing connection issues and application errors. Our engineers are currently investigating issues loading the Close application, making & receiving calls, and responding to Close API requests.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and the fix is being implemented.
A fix has been implemented and we are monitoring the results.
We've deployed a fix, we're continuing to see improvements in overall system performance, we expect recovery slowly over the next several minutes.
This incident has been resolved.
We are currently investigating this issue.
We are experiencing an issue with a 3rd party provider.
We are experiencing an issue with a 3rd party provider.
We're continuing to monitor the situation and expect gradual recovery over the next hour.
We're continuing to monitor the situation and expect gradual recovery over the next hour.
This incident has been resolved.
We are receiving an increased number of reports that users are unable to use calling when using the Desktop Application. Calling within the browser works fine. We're investigating.
We have identified the issue and are actively working on a fix.
The issue has been resolved. Please reach out to [email protected] if you continue to have calling issues after refreshing.
We're currently investigating a slowdown in application performance. You may experience delays in loading pages. The engineering team is currently looking into resolving this as quickly as possible.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating problems with Lead Pages being loaded too slowly while on a Dialer session.
A fix has been implemented, and we are currently monitoring this. New updates to follow.
This incident has been resolved.
There’s currently an outage on AWS’s end in a certain region. While our hosting is mainly in another region, many other services, including calling, are affected.
This incident has been resolved.
There’s currently an outage on AWS’s end in the us-east-1 region. While our hosting is mainly in another region, many other services, including calling, are affected. We are actively monitoring this, and we will keep you updated
AWS has reported partial recovery on this incident (https://health.aws.amazon.com/health/status), but services have yet to recover fully. Our service provider, Twilio, is also actively monitoring this (https://status.twilio.com/) We will continue to keep you posted.
This incident has been resolved.
Some customers in the EMEA region are experiencing connectivity issues to the Close app. We believe this is a widespread issue and are continuing to investigate.
The issue appears to have resolved itself. We are still monitoring and waiting for our Cloud provider to confirm resolution.
AWS confirmed they were investigating an issue but haven't yet notified us that it has been resolved. We are still monitoring for new issues.
Connectivity issues appear to have been resolved. Still waiting for AWS to confirm what actions were taken to resolve the issue.
Our cloud provider was able to confirm they were having issues with an external network provider during this time period that caused connectivity issues between Europe and the us-west-2 region. This aligns with the issues that were reported to our support team. We will review our monitoring and alerting processes to determine if we can be alerted sooner to these types of regional cloud connectivity issues so that we can more quickly notify our customers.
We are currently investigating a delay in processing triggers that kick off Workflow actions.
We have identified the problem as coming from our compute provider, AWS. An unplanned patch to our Event Stream is currently underway.
Unplanned patches have been applies and our system has processed through the delayed events.