Close Outage History

Close is up right now

Close had 30 outages in the last 2 years totaling 46h 39m of downtime — averaging 1.2 incidents per month.

There were 30 Close outages since July 26, 2024 totaling 46h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.close.com

Major May 12, 2026

Partial outage - connection issues and application errors

Detected by Pingoru
May 12, 2026, 09:34 AM UTC
Resolved
May 12, 2026, 11:17 AM UTC
Duration
1h 42m
Affected: APIIncoming CallsOutgoing CallsDialer
Timeline · 3 updates
  1. 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.

  2. monitoring May 12, 2026, 11:07 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 12, 2026, 11:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

Search Functionality Delayed

Detected by Pingoru
Apr 23, 2026, 04:56 PM UTC
Resolved
Apr 23, 2026, 07:44 PM UTC
Duration
2h 47m
Affected: Indexing
Timeline · 5 updates
  1. investigating Apr 23, 2026, 04:56 PM UTC

    We are currently investigating this issue.

  2. identified Apr 23, 2026, 05:14 PM UTC

    The issue has been identified and the fix is being implemented.

  3. monitoring Apr 23, 2026, 05:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. 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.

  5. resolved Apr 23, 2026, 07:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026

Call Recordings Processing Delayed

Detected by Pingoru
Apr 23, 2026, 04:16 PM UTC
Resolved
Apr 23, 2026, 09:18 PM UTC
Duration
5h 2m
Affected: Call Recording
Timeline · 6 updates
  1. investigating Apr 23, 2026, 04:16 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 23, 2026, 04:56 PM UTC

    We are experiencing an issue with a 3rd party provider.

  3. monitoring Apr 23, 2026, 05:32 PM UTC

    We are experiencing an issue with a 3rd party provider.

  4. monitoring Apr 23, 2026, 06:52 PM UTC

    We're continuing to monitor the situation and expect gradual recovery over the next hour.

  5. monitoring Apr 23, 2026, 07:45 PM UTC

    We're continuing to monitor the situation and expect gradual recovery over the next hour.

  6. resolved Apr 23, 2026, 09:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 5, 2025

Calling problems in the Desktop Application

Detected by Pingoru
Nov 05, 2025, 06:42 PM UTC
Resolved
Nov 05, 2025, 07:56 PM UTC
Duration
1h 13m
Timeline · 3 updates
  1. 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.

  2. identified Nov 05, 2025, 07:21 PM UTC

    We have identified the issue and are actively working on a fix.

  3. 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.

Read the full incident report →

Minor November 1, 2025

Application Slowness

Detected by Pingoru
Nov 01, 2025, 08:55 AM UTC
Resolved
Nov 01, 2025, 10:53 AM UTC
Duration
1h 58m
Affected: Application UIAPI
Timeline · 3 updates
  1. 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.

  2. identified Nov 01, 2025, 10:32 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Nov 01, 2025, 10:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 22, 2025

Experiencing Delays on Dialer Sessions

Detected by Pingoru
Oct 22, 2025, 10:35 AM UTC
Resolved
Oct 22, 2025, 11:50 AM UTC
Duration
1h 15m
Affected: Dialer
Timeline · 3 updates
  1. 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.

  2. monitoring Oct 22, 2025, 11:10 AM UTC

    A fix has been implemented, and we are currently monitoring this. New updates to follow.

  3. resolved Oct 22, 2025, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

Service interruption

Detected by Pingoru
Oct 20, 2025, 02:20 PM UTC
Resolved
Oct 20, 2025, 08:27 PM UTC
Duration
6h 7m
Affected: Phone ServiceOutgoing Calls
Timeline · 2 updates
  1. 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.

  2. resolved Oct 20, 2025, 08:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

Service Interruption

Detected by Pingoru
Oct 20, 2025, 10:38 AM UTC
Resolved
Oct 20, 2025, 01:12 PM UTC
Duration
2h 34m
Affected: Phone ServiceOutgoing CallsTelephony Provider Connectivity
Timeline · 3 updates
  1. 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

  2. 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.

  3. resolved Oct 20, 2025, 01:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 24, 2025

Connectivity issues from EMEA Region

Detected by Pingoru
Sep 24, 2025, 12:01 PM UTC
Resolved
Sep 24, 2025, 01:31 PM UTC
Duration
1h 29m
Affected: Application UIAPI
Timeline · 5 updates
  1. investigating Sep 24, 2025, 12:01 PM UTC

    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.

  2. monitoring Sep 24, 2025, 12:22 PM UTC

    The issue appears to have resolved itself. We are still monitoring and waiting for our Cloud provider to confirm resolution.

  3. monitoring Sep 24, 2025, 01:23 PM UTC

    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.

  4. resolved Sep 24, 2025, 01:31 PM UTC

    Connectivity issues appear to have been resolved. Still waiting for AWS to confirm what actions were taken to resolve the issue.

  5. postmortem Sep 25, 2025, 10:19 AM UTC

    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.

Read the full incident report →

Notice September 5, 2025

Delayed processing of Workflow Triggers

Detected by Pingoru
Sep 05, 2025, 10:45 AM UTC
Resolved
Sep 05, 2025, 11:13 AM UTC
Duration
28m
Timeline · 3 updates
  1. investigating Sep 05, 2025, 10:45 AM UTC

    We are currently investigating a delay in processing triggers that kick off Workflow actions.

  2. identified Sep 05, 2025, 11:01 AM UTC

    We have identified the problem as coming from our compute provider, AWS. An unplanned patch to our Event Stream is currently underway.

  3. resolved Sep 05, 2025, 11:13 AM UTC

    Unplanned patches have been applies and our system has processed through the delayed events.

Read the full incident report →

Notice August 6, 2025

Calling Service Disconnections

Detected by Pingoru
Aug 06, 2025, 08:16 AM UTC
Resolved
Aug 06, 2025, 01:08 PM UTC
Duration
4h 52m
Affected: Phone ServiceIncoming CallsOutgoing CallsDialerCall RecordingTelephony Provider Connectivity
Timeline · 3 updates
  1. identified Aug 06, 2025, 08:16 AM UTC

    We've identified a problem with our telephony provider, Twilio, which incorrectly flags some (not all) accounts as compromised and thus disables their ability to make calls. We have escalated the problem and are working urgently with Twilio to resolve the issue.

  2. monitoring Aug 06, 2025, 10:55 AM UTC

    Our telephony provider, Twilio, has fixed the accounts affected so far and is actively working on preventing the problem from reoccurring.

  3. resolved Aug 06, 2025, 01:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 22, 2025

Experiencing delays with computing derived fields

Detected by Pingoru
Jul 22, 2025, 07:34 PM UTC
Resolved
Jul 22, 2025, 08:18 PM UTC
Duration
43m
Affected: Indexing
Timeline · 2 updates
  1. monitoring Jul 22, 2025, 07:34 PM UTC

    Some customers may experience delayed updates to derived fields such as "Last Communication Date". The delay should be resolved soon.

  2. resolved Jul 22, 2025, 08:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 14, 2025

Delayed Webhook Processing

Detected by Pingoru
May 14, 2025, 03:47 PM UTC
Resolved
May 14, 2025, 04:39 PM UTC
Duration
51m
Affected: API
Timeline · 4 updates
  1. investigating May 14, 2025, 03:47 PM UTC

    We've identified an issue with our webhook processing system. Webhooks may be delayed up to twenty minutes. Updates will be posted as they are available.

  2. identified May 14, 2025, 03:56 PM UTC

    This issue has been identified and a fix is being implemented.

  3. monitoring May 14, 2025, 04:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 14, 2025, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 25, 2025

OpenAI - Increased Error Rates

Detected by Pingoru
Mar 25, 2025, 06:21 PM UTC
Resolved
Mar 25, 2025, 09:44 PM UTC
Duration
3h 22m
Affected: IndexingQuerying
Timeline · 2 updates
  1. identified Mar 25, 2025, 06:21 PM UTC

    OpenAI are currently experiencing increased error rates on their side, which is impacting Lead Summaries and AI Search in Close. You can follow for updates on their status page here - https://status.openai.com/

  2. resolved Mar 25, 2025, 09:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 23, 2025

Elevated Response Times

Detected by Pingoru
Jan 23, 2025, 04:41 PM UTC
Resolved
Jan 23, 2025, 05:18 PM UTC
Duration
37m
Affected: Application UIAPI
Timeline · 4 updates
  1. investigating Jan 23, 2025, 04:41 PM UTC

    Users may currently experience elevated response times. We are investigating the situation.

  2. identified Jan 23, 2025, 05:11 PM UTC

    We are taking mitigation steps to reduce high database load.

  3. monitoring Jan 23, 2025, 05:14 PM UTC

    The response times should be normalized, we are monitoring the situation.

  4. resolved Jan 23, 2025, 05:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 6, 2025

App UI unavailable

Detected by Pingoru
Jan 06, 2025, 05:49 PM UTC
Resolved
Jan 06, 2025, 07:47 PM UTC
Duration
1h 58m
Affected: Application UI
Timeline · 4 updates
  1. investigating Jan 06, 2025, 05:49 PM UTC

    We are currently investigating the issue.

  2. monitoring Jan 06, 2025, 05:50 PM UTC

    Issue was identified and reverted. Monitoring to confirm no further issues.

  3. resolved Jan 06, 2025, 07:47 PM UTC

    This incident has been resolved.

  4. postmortem Jan 09, 2025, 07:48 AM UTC

    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 The Close Web UI was unavailable for 15 minutes from 2025-01-06 17:33 to 2025-01-06 17:48. ## Root Cause and Resolution A change to our deployment process introduced a build where JavaScript file contents were updated without corresponding filename changes, leading to caching issues that caused outdated files to be served. We quickly rolled back to a previous build to restore services and then resolved the underlying issue by updating the affected assets. ## Timeline * 17:33 UTC - Deployment of the broken Close Web UI * 17:48 UTC - Restored prior version

Read the full incident report →

Minor November 18, 2024

Search Indexer Delays

Detected by Pingoru
Nov 18, 2024, 02:57 PM UTC
Resolved
Nov 18, 2024, 03:48 PM UTC
Duration
51m
Affected: Indexing
Timeline · 4 updates
  1. identified Nov 18, 2024, 02:57 PM UTC

    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.

  2. monitoring Nov 18, 2024, 03:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 18, 2024, 03:48 PM UTC

    This incident has been resolved.

  4. postmortem Nov 18, 2024, 05:26 PM UTC

    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

Read the full incident report →