Close Outage History

Close is up right now

Pingoru has recorded 50 incidents for Close: 11 in the last 12 months and 3 in the last 90 days.

Source: status.close.com

50incidents recorded
11last 12 months
3last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Close in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202625 of 720 (1%)
May 202612 of 744 (0%)
June 202626 of 720 (1%)
July 202600 of 744 (0%)
August 202623 of 744 (0%)
September 202610 of 720 (0%)
October 202600 of 571 (0%)

Incidents, newest first

Major February 11, 2025 Degraded Performance 1h 2m Application UI, Syncing, API, Calendar - Syncing

Started Feb 11, 2025, 10:31 PM UTC· resolved Feb 11, 2025, 11:34 PM UTC

  1. investigating Feb 11, 2025, 10:31 PM 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 Feb 11, 2025, 10:40 PM UTC

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

  3. monitoring Feb 11, 2025, 10:47 PM UTC

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

  4. monitoring Feb 11, 2025, 10:58 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Feb 11, 2025, 11:20 PM 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 Feb 11, 2025, 11:34 PM UTC

    This incident has been resolved.

  7. postmortem Feb 14, 2025, 07:23 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 Beginning 22:00 UTC until 23:03 UTC on Tuesday February 11, 2025 users of the Close App experienced significantly degraded performance and an elevated error rate. This included slow page loads, long API response times, delayed email syncing, and delayed calendar syncing for all customers. ## Root Cause and Resolution At 22:00 UTC on Tuesday February 11, 2025 a change was deployed to the production environment of the Close system. This change introduced a poorly optimized database query. This caused our primary back end database to become overloaded and unstable. Close Engineering identified and removed the offending database query by 22:47 UTC. Performance began to gradually return to baseline, fully recovering by 23:03 UTC. ## Timeline * 22:00 UTC - A change is deployed to production introducing a poorly optimized database query * 22:01 UTC - Load on our primary back end database begins to climb * 22:06 UTC - Load on our primary back end database breaches critical thresholds alerting Close Engineering * 22:17 UTC - Close Engineering isolates the poorly optimized database query and begins to remove it from production * 22:47 UTC - Removal of the poorly optimized database query completes * 23:03 UTC - Close system performance returns to baseline

Read the full incident report →

Minor January 23, 2025 Elevated Response Times 37m Application UI, API

Started Jan 23, 2025, 04:41 PM UTC· resolved Jan 23, 2025, 05:18 PM UTC

  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 1h 58m Application UI

Started Jan 06, 2025, 05:49 PM UTC· resolved Jan 06, 2025, 07:47 PM UTC

  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 51m Indexing

Started Nov 18, 2024, 02:57 PM UTC· resolved Nov 18, 2024, 03:48 PM UTC

  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 →

Major October 24, 2024 Issues syncing with Calendly 42m Calendar - Syncing

Started Oct 24, 2024, 08:17 PM UTC· resolved Oct 24, 2024, 09:00 PM UTC

  1. investigating Oct 24, 2024, 08:17 PM UTC

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

  2. resolved Oct 24, 2024, 09:00 PM UTC

    This incident has been resolved.

Read the full incident report →