Close Outage History
Close is up right nowClose had 14 outages in the last 2 years totaling 36h 13m of downtime — averaging 0.6 incidents per month.
There were 14 Close outages since October 14, 2025 totaling 36h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
Background Task Processing Delays
Timeline · 3 updates
- investigating Jun 29, 2026, 05:46 PM UTC
We have become aware of degraded processing of background tasks in the Close system. We are currently investigating the issue.
- monitoring Jun 29, 2026, 07:25 PM UTC
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.
- resolved Jun 29, 2026, 07:39 PM UTC
This incident has been resolved. Background tasks are processing normally.
Change indexing delayed
Timeline · 7 updates
- investigating Jun 03, 2026, 02:50 PM UTC
Changes done to CRM data are reflected in search with a delay.
- investigating Jun 03, 2026, 03:21 PM UTC
We are continuing to investigate the issue.
- investigating Jun 03, 2026, 04:05 PM UTC
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.
- investigating Jun 03, 2026, 04:41 PM UTC
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.
- identified Jun 03, 2026, 05:45 PM UTC
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.
- monitoring Jun 03, 2026, 06:17 PM UTC
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.
- resolved Jun 03, 2026, 06:53 PM UTC
This incident has been resolved. The Close app and API are now functioning normally.
Partial outage - connection issues and application errors
Timeline · 3 updates
- investigating May 12, 2026, 09:34 AM UTC
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.
- monitoring May 12, 2026, 11:07 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 12, 2026, 11:17 AM UTC
This incident has been resolved.
Search Functionality Delayed
Timeline · 5 updates
- investigating Apr 23, 2026, 04:56 PM UTC
We are currently investigating this issue.
- identified Apr 23, 2026, 05:14 PM UTC
The issue has been identified and the fix is being implemented.
- monitoring Apr 23, 2026, 05:56 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 23, 2026, 06:50 PM UTC
We've deployed a fix, we're continuing to see improvements in overall system performance, we expect recovery slowly over the next several minutes.
- resolved Apr 23, 2026, 07:44 PM UTC
This incident has been resolved.
Call Recordings Processing Delayed
Timeline · 6 updates
- investigating Apr 23, 2026, 04:16 PM UTC
We are currently investigating this issue.
- investigating Apr 23, 2026, 04:56 PM UTC
We are experiencing an issue with a 3rd party provider.
- monitoring Apr 23, 2026, 05:32 PM UTC
We are experiencing an issue with a 3rd party provider.
- monitoring Apr 23, 2026, 06:52 PM UTC
We're continuing to monitor the situation and expect gradual recovery over the next hour.
- monitoring Apr 23, 2026, 07:45 PM UTC
We're continuing to monitor the situation and expect gradual recovery over the next hour.
- resolved Apr 23, 2026, 09:18 PM UTC
This incident has been resolved.
Database issues
Timeline · 6 updates
Calling problems in the Desktop Application
Timeline · 3 updates
- investigating Nov 05, 2025, 06:42 PM UTC
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.
- identified Nov 05, 2025, 07:21 PM UTC
We have identified the issue and are actively working on a fix.
- resolved Nov 05, 2025, 07:56 PM UTC
The issue has been resolved. Please reach out to [email protected] if you continue to have calling issues after refreshing.
Application Slowness
Timeline · 3 updates
- investigating Nov 01, 2025, 08:55 AM UTC
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.
- identified Nov 01, 2025, 10:32 AM UTC
The issue has been identified and a fix is being implemented.
- resolved Nov 01, 2025, 10:53 AM UTC
This incident has been resolved.
Experiencing delays on Dialer Sessions
Timeline · 3 updates
Experiencing Delays on Dialer Sessions
Timeline · 3 updates
- investigating Oct 22, 2025, 10:35 AM UTC
We are currently investigating problems with Lead Pages being loaded too slowly while on a Dialer session.
- monitoring Oct 22, 2025, 11:10 AM UTC
A fix has been implemented, and we are currently monitoring this. New updates to follow.
- resolved Oct 22, 2025, 11:50 AM UTC
This incident has been resolved.
Service interruption
Timeline · 2 updates
- investigating Oct 20, 2025, 02:20 PM UTC
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.
- resolved Oct 20, 2025, 08:27 PM UTC
This incident has been resolved.
Service Interruption
Timeline · 3 updates
- monitoring Oct 20, 2025, 10:38 AM UTC
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
- monitoring Oct 20, 2025, 11:16 AM UTC
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.
- resolved Oct 20, 2025, 01:12 PM UTC
This incident has been resolved.