Close

Affected: Application UI

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-29 17:48 UTC

   We are currently investigating issues with parts of the Close application not loading.

2. monitoring 2026-09-29 18:11 UTC

   The issue was identified and reverted. We continue to monitor the application to ensure everything is back to normal.

3. resolved 2026-09-29 18:15 UTC

   This incident has been resolved.

4. postmortem 2026-10-05 17:25 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 Close systems were unavailable for 30...

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-11 13:12 UTC

   We are again investigating an elevated number of database failures.

2. investigating 2026-08-11 14:15 UTC

   We are continuing to investigate the issue.

3. monitoring 2026-08-11 14:53 UTC

   We have identified the problem, adjusted our scaling strategy, and are seeing healthy recovery of all systems.

4. resolved 2026-08-11 15:15 UTC

   This incident has been resolved.

5. postmortem 2026-08-13 22:56 UTC

   ## Summary & Impact Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously, and this incident is not acceptable to us. Below is an explanation of what happened and how we will prevent another such interruption from...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 08:26 UTC

   We are currently investigating an elevated number of database failures.

2. identified 2026-08-11 08:54 UTC

   We have identified an issue impacting our production database. Close Engineering is taking action to restore functionality. Users should notice improved performance over the next several minutes.

3. monitoring 2026-08-11 09:04 UTC

   We have remediated the issue with our production database. Users should be able to use the Close app normally. Close Engineering is monitoring system performance to confirm resolution.

4. resolved 2026-08-11 09:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 17:46 UTC

   We have become aware of degraded processing of background tasks in the Close system. We are currently investigating the issue.

2. monitoring 2026-06-29 19:25 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.

3. resolved 2026-06-29 19:39 UTC

   This incident has been resolved. Background tasks are processing normally.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-03 14:50 UTC

   Changes done to CRM data are reflected in search with a delay.

2. investigating 2026-06-03 15:21 UTC

   We are continuing to investigate the issue.

3. investigating 2026-06-03 16:05 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.

4. investigating 2026-06-03 16:41 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.

5. identified 2026-06-03 17:45 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.

6. monitoring 2026-06-03 18:17 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.

7. resolved 2026-06-03 18:53 UTC

   This incident has been resolved. The Close app and API are now functioning normally.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: API, Incoming Calls, Outgoing Calls, Dialer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-12 09:34 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 2026-05-12 11:07 UTC

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

3. resolved 2026-05-12 11:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-23 16:56 UTC

   We are currently investigating this issue.

2. identified 2026-04-23 17:14 UTC

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

3. monitoring 2026-04-23 17:56 UTC

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

4. monitoring 2026-04-23 18:50 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 2026-04-23 19:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Call Recording

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-23 16:16 UTC

   We are currently investigating this issue.

2. investigating 2026-04-23 16:56 UTC

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

3. monitoring 2026-04-23 17:32 UTC

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

4. monitoring 2026-04-23 18:52 UTC

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

5. monitoring 2026-04-23 19:45 UTC

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

6. resolved 2026-04-23 21:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-16 16:08 UTC

   We are currently investigating this issue.

2. investigating 2026-03-16 16:16 UTC

   We are investigating the issue and seeing some recovery.

3. monitoring 2026-03-16 16:27 UTC

   Database infrastructure is operational.

4. monitoring 2026-03-16 16:45 UTC

   Close services continue to recover. Most customers should see normal performance. Close Engineering continues to monitor the recovery.

5. resolved 2026-03-16 16:55 UTC

   This incident is resolved. Close has returned to normal performance.

6. postmortem 2026-03-17 15:13 UTC

   # Summary 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. The Close App and API were severely...

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-05 18:42 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 2025-11-05 19:21 UTC

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

3. resolved 2025-11-05 19:56 UTC

   The issue has been resolved. Please reach out to support@close.com if you continue to have calling issues after refreshing.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-01 08:55 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 2025-11-01 10:32 UTC

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

3. resolved 2025-11-01 10:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Dialer

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-10-23 11:40 UTC

   We identified an issue causing Lead Pages to load slowly during Dialer sessions. A fix has been implemented and will be deployed shortly. After deployment, we’ll monitor the system to ensure the issue is fully resolved. New updates to follow.

2. resolved 2025-10-23 15:52 UTC

   This incident has been resolved.

3. postmortem 2025-10-27 16:51 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 Between Tuesday 10/21 14:46–17:24 UTC,...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Dialer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-22 10:35 UTC

   We are currently investigating problems with Lead Pages being loaded too slowly while on a Dialer session.

2. monitoring 2025-10-22 11:10 UTC

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

3. resolved 2025-10-22 11:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Phone Service, Outgoing Calls

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 14:20 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 2025-10-20 20:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Phone Service, Outgoing Calls, Telephony Provider Connectivity

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 10:38 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 2025-10-20 11:16 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 2025-10-20 13:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API, Querying

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-14 15:26 UTC

   Some users are experience downtime. Our engineers are currently investigating issues loading the Close application and pulling data from the Close API.

2. investigating 2025-10-14 15:48 UTC

   We are currently applying fixes to restore operations and monitoring their impact.

3. monitoring 2025-10-14 15:53 UTC

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

4. resolved 2025-10-14 16:00 UTC

   This incident has been resolved.

5. postmortem 2025-10-16 18:41 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 A small number of Close API requests began...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-09-24 12:01 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 2025-09-24 12:22 UTC

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

3. monitoring 2025-09-24 13:23 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 2025-09-24 13:31 UTC

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

5. postmortem 2025-09-25 10:19 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...

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-09-05 10:45 UTC

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

2. identified 2025-09-05 11:01 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 2025-09-05 11:13 UTC

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

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Phone Service, Incoming Calls, Outgoing Calls, Dialer, Call Recording, Telephony Provider Connectivity

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-08-06 08:16 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 2025-08-06 10:55 UTC

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

3. resolved 2025-08-06 13:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-07-22 19:34 UTC

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

2. resolved 2025-07-22 20:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-19 04:23 UTC

   Users are currently unable to load the application UI due to an issue with the serving infrastructure.

2. investigating 2025-06-19 05:02 UTC

   We're continuing to investigate the issue.

3. monitoring 2025-06-19 05:08 UTC

   Application is loading again, we're monitoring the situation.

4. monitoring 2025-06-19 05:09 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-06-19 05:10 UTC

   This incident has been resolved.

6. postmortem 2025-06-19 18:01 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 and Desktop applications were...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-14 15:47 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 2025-05-14 15:56 UTC

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

3. monitoring 2025-05-14 16:19 UTC

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

4. resolved 2025-05-14 16:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-04-22 14:30 UTC

   This incident has been resolved.

2. postmortem 2025-04-28 17:56 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 Between April 22nd 14:25 UTC and April 23rd...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing, Querying

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. identified 2025-03-25 18:21 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 2025-03-25 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Dialer

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-10 16:02 UTC

   We've become aware of degraded performance of our Dialer service. We are investigating the issue. Updates will be posted as they become available.

2. monitoring 2025-03-10 16:21 UTC

   We are continuing to investigate the cause of the degraded performance of our Dialer system. Our Dialer system is now functioning normally. We are monitoring performance.

3. resolved 2025-03-10 16:28 UTC

   This incident has been resolved.

4. postmortem 2025-03-12 17:39 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 Dialer functionality was impaired for 58...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, Indexing, API, Querying

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-14 21:11 UTC

   We have become aware of degraded performance of the Close system. We are actively triaging the issue. Updates will be posted as they become available.

2. identified 2025-02-14 21:45 UTC

   The issue has been identified and a fix is being implemented. Search indexing may be delayed for some customers.

3. monitoring 2025-02-14 21:54 UTC

   A fix has been implemented and we are monitoring the results. Search indexing may be delayed for some users.

4. resolved 2025-02-14 22:05 UTC

   This incident has been resolved.

5. postmortem 2025-02-21 19:42 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 On February 14th, 2025 for two and a half...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, Syncing, API, Calendar - Syncing

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-11 22:31 UTC

   We have become aware of degraded performance of the Close system. We are actively triaging the issue. Updates will be posted as they become available.

2. identified 2025-02-11 22:40 UTC

   The issue has been identified. A fix is being rolled out to our production system.

3. monitoring 2025-02-11 22:47 UTC

   A fix has been implemented. We are monitoring the results.

4. monitoring 2025-02-11 22:58 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2025-02-11 23:20 UTC

   Our App UI and API have returned to normal performance. Our email and calendar syncing systems are operational but delayed. We are continuing to monitor for further issues.

6. resolved 2025-02-11 23:34 UTC

   This incident has been resolved.

7. postmortem 2025-02-14 19:23 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 Beginning 22:00 UTC until 23:03 UTC on...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-23 16:41 UTC

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

2. identified 2025-01-23 17:11 UTC

   We are taking mitigation steps to reduce high database load.

3. monitoring 2025-01-23 17:14 UTC

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

4. resolved 2025-01-23 17:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-01-06 17:49 UTC

   We are currently investigating the issue.

2. monitoring 2025-01-06 17:50 UTC

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

3. resolved 2025-01-06 19:47 UTC

   This incident has been resolved.

4. postmortem 2025-01-09 07:48 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...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-11-18 14:57 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 2024-11-18 15:07 UTC

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

3. resolved 2024-11-18 15:48 UTC

   This incident has been resolved.

4. postmortem 2024-11-18 17:26 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...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, Indexing, API, Querying

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-04 08:45 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. identified 2024-11-04 09:20 UTC

   We have identified a problem with one of our search databases and have initiated a failover.

3. monitoring 2024-11-04 09:29 UTC

   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.

4. resolved 2024-11-04 09:31 UTC

   The issue is resolved now.

5. postmortem 2024-11-07 15:06 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 For some clients changes performed in Close...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Calendar - Syncing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-24 20:17 UTC

   We are currently investigating issues with calendar events syncing via our Calendly integration.

2. resolved 2024-10-24 21:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-14 20:33 UTC

   We are currently seeing intermittent issues with Close loading. We will let you know as soon as this is fixed.

2. investigating 2024-10-14 20:55 UTC

   We are continuing to investigate the issue. We will post updates as they are available.

3. monitoring 2024-10-14 21:01 UTC

   We have remediated the performance issue affecting some Close customers. The Close App & API should be functioning normally for all users. We will continue to monitor our system's performance.

4. resolved 2024-10-14 21:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, Indexing, API, Sending

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-25 14:40 UTC

   We are currently investigating this issue

2. investigating 2024-09-25 18:28 UTC

   The app is recovering and we are continuing to monitor the situation. Some background tasks could still be delayed.

3. monitoring 2024-09-25 18:31 UTC

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

4. monitoring 2024-09-25 18:53 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2024-09-25 19:05 UTC

   The Close app is functioning normally. Some background task processing may be delayed. We are continuing to monitor for further issues.

6. monitoring 2024-09-25 19:11 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2024-09-25 19:12 UTC

   The Close app is functioning normally. Some background task processing may be delayed. We are continuing to monitor for further issues.

8. resolved 2024-09-25 19:52 UTC

   This incident has been resolved.

9. postmortem 2024-09-26 20:57 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 Between 13:40 and 16:55 UTC on Wednesday...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-12 19:29 UTC

   We are currently seeing intermittent issues with Close loading. We will let you know as soon as this is fixed.

2. monitoring 2024-09-12 20:06 UTC

   The issue has been identified, and our team are currently monitoring performance.

3. resolved 2024-09-12 21:01 UTC

   This incident has been resolved, and Close is fully operational.

4. postmortem 2024-09-13 15:45 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 Between 1900 and 2000 UTC on September 12,...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Indexing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-07-26 21:52 UTC

   Indexing is currently delayed. Data in search results, smart views, reporting, and inbox may be delayed. We expect this issue to resolve within the hour.

2. monitoring 2024-07-26 22:06 UTC

   This incident has been resolved.

3. resolved 2024-07-26 22:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-05-24 11:13 UTC

   API endpoints and application areas backed by Search infrastructure - leads, contacts, opportunities list pages, and certain reporting pages were inaccessible for 20 minutes. This has been resolved.

2. postmortem 2024-05-24 12:06 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 API endpoints and application areas backed...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Phone Service

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-04-22 14:53 UTC

   Our telephony provider, Twilio, is currently experiencing issues on their side that are impacting Close users. We will update this page as soon as we have more information from Twilio.

2. monitoring 2024-04-22 17:36 UTC

   A fix has been implemented by Twilio and baseline call functionality has been restored.

3. resolved 2024-04-22 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-03-14 15:07 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. monitoring 2024-03-14 15:25 UTC

   Webhook processing is no longer delayed. Monitoring will continue and updates will be provided.

3. resolved 2024-03-14 16:06 UTC

   Webhook processing is stable.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-09-15 14:37 UTC

   We are currently investigating this issue.

2. identified 2023-09-15 14:37 UTC

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

3. identified 2023-09-15 14:41 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2023-09-15 14:41 UTC

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

5. monitoring 2023-09-15 15:05 UTC

   A fix has been implemented. The Close application and API are fully functional. We expect full recovery of background task processing performance in the next 15 minutes.

6. resolved 2023-09-15 15:31 UTC

   This incident has been resolved.

7. postmortem 2023-09-15 20:46 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 Our processing of background tasks was...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-09-05 16:08 UTC

   Customers may be experiencing elevated error rates. The root cause has been identified. A fix is being deployed.

2. monitoring 2023-09-05 16:17 UTC

   The fix has been deployed. The Close application is now functioning normally. Close Engineering is continuing to monitor application performance.

3. resolved 2023-09-05 17:04 UTC

   This incident has been resolved.

4. postmortem 2023-09-05 21:35 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 Close users experienced elevated error rates...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Querying

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-08-14 18:50 UTC

   We are currently investigating an issue whereby the limit function in our search filters is not being applied to bulk actions.

2. investigating 2023-08-14 18:50 UTC

   We are continuing to investigate this issue.

3. identified 2023-08-14 19:45 UTC

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

4. resolved 2023-08-14 20:46 UTC

   This incident has been resolved.

5. postmortem 2023-08-22 07:26 UTC

   Close sincerely apologizes for the interruption of our service. We take the stability of a platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Bulk actions performed in Close between...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI, API

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2023-08-01 16:22 UTC

   Close has become aware of degraded performance of our API. This resulted in a brief window between 15:55 and 16:05 UTC when users may have seen elevated error rates when using the Close App and API. Performance has recovered and users should no longer be impacted. Close...

2. resolved 2023-08-01 17:22 UTC

   This incident has been resolved.

3. postmortem 2023-08-01 22:38 UTC

   Close sincerely apologizes for the interruption of our service. We take the stability of a platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Between 15:55 UTC and 16:05 UTC on August 1,...

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-07-26 16:30 UTC

   Between 16:47 UTC and 17:18 UTC on July 26, 2023 Close users may have experienced degraded performance and an elevated error rate when using the Close application or API.

2. postmortem 2023-07-28 15:45 UTC

   Close sincerely apologizes for the interruption of our service. We take the stability of a platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact Between 16:47 UTC and 17:18 UTC on July 26,...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Phone Service, Application UI, Indexing, Syncing, API, Incoming Calls, Sending, Querying, Outgoing Calls, Dialer, SMS

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-07-07 17:37 UTC

   We're currently investigating a slowdown in application performance. You may experience delays in email syncing, report updates, smartviews / search results, calling, and bulk actions. The engineering team is currently looking into resolving this as quickly as possible.

2. monitoring 2023-07-07 18:36 UTC

   Application Loading Issues

3. monitoring 2023-07-07 18:38 UTC

   The performance in Close is now operational. Our engineers are still closely monitoring the situation.

4. resolved 2023-07-07 21:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: SMS

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2023-05-04 15:05 UTC

   Our telephony provider, Twilio, is currently experiencing issues on their side that are impacting Close users. We're in contact with them about these issues and they are currently working on a fix. You can follow along with Twilio's status updates at: https://status.twilio.com/...

2. resolved 2023-05-04 17:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-03-01 13:24 UTC

   Webhook events are being delayed. We are currently investigating this issue.

2. monitoring 2023-03-01 14:13 UTC

   The issue has been identified, and a fix has been implemented. The event backlog is being processed.

3. resolved 2023-03-01 15:39 UTC

   The event backlog has been processed.

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-11-08 13:09 UTC

   We are currently investigating this issue.

2. identified 2022-11-08 15:48 UTC

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

3. monitoring 2022-11-08 16:10 UTC

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

4. resolved 2022-11-08 16:51 UTC

   This incident has been resolved.

5. postmortem 2022-11-16 20:23 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 Close CRM was not loading for a subset of...

Excerpts are shortened. Read the full incident on Close's status page.

Affected: Application UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-11-02 12:33 UTC

   We are aware that Close is currently not loading. Our engineering team is investigating this issue, and we will update as soon as possible.

2. identified 2022-11-02 12:36 UTC

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

3. monitoring 2022-11-02 12:38 UTC

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

4. monitoring 2022-11-02 12:39 UTC

   We are continuing to monitor for any further issues.

5. resolved 2022-11-02 12:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Close's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2022-10-20 09:30 UTC

   Email sync into the Close application was delayed between 5:30 AM and 6:40 AM EDT.

2. postmortem 2022-10-20 19:04 UTC

   Close sincerely apologizes for the interruption of our service. We take the stability of a platform very seriously. Below is an explanation of what happened and how we will prevent another such interruption from occurring. ## Impact On October 20 from 5:30 AM until 6:40 AM EDT...

Excerpts are shortened. Read the full incident on Close's status page.