Is Close down?
Last checked 9m agoNo incidents right now.
Close is operational right now. Last checked 9m ago; the most recent incident resolved 10d ago.
Real-time Close status, recent outages, and incident history — pulled directly from Close's official status page at https://status.close.com every 5 minutes. Pingoru tracks 20 Close services and has captured 5 incidents in the last 90 days (99.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Close reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Indexing
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.
Latest: This incident has been resolved. The Close app and API are now functioning normally.
-
- APIIncoming CallsOutgoing CallsDialer
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.
Latest: This incident has been resolved.
-
- Indexing
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.
Latest: This incident has been resolved.
-
- Call Recording
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.
Latest: This incident has been resolved.
-
- Application UIAPI
Timeline · 6 updates
- investigating · Mar 16, 2026, 04:08 PM UTC
We are currently investigating this issue.
- investigating · Mar 16, 2026, 04:16 PM UTC
We are investigating the issue and seeing some recovery.
- monitoring · Mar 16, 2026, 04:27 PM UTC
Database infrastructure is operational.
- monitoring · Mar 16, 2026, 04:45 PM UTC
Close services continue to recover. Most customers should see normal performance. Close Engineering continues to monitor the recovery.
- resolved · Mar 16, 2026, 04:55 PM UTC
This incident is resolved. Close has returned to normal performance.
- postmortem · Mar 17, 2026, 03:13 PM 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 disrupted for all users for 18 minutes between 15:57 and 16:15 UTC on Monday March 16, 2026. Automated systems restored functionality by 16:15 UTC. # Incident Timeline | Time \(UTC\) | Event | | --- | --- | | 2026-03-16 | | | 15:57:00 | **Automated Database Maintenance begins** | | 15:58:42 | **Incident detected by monitoring** | | 15:58:49 | **Escalation acknowledged by Close Engineering On-Call** | | 16:02:41 | **Incident accepted by Close Engineering** | | 16:15:00 | **Affected database restored to normal operation** | | 17:09:22 | **Incident resolved** | # Root Cause and Resolution At ~15:57 UTC an automated database maintenance process began that starved our production database cluster of resources. This caused our primary instance and both replica instances of the production cluster to become unavailable for ~18 minutes. The system recovered and began performing normally at 16:15 UTC. To prevent this from happening in the future Close Engineering has provisioned additional resources to the affected database cluster to make it more resilient to sudden demand spikes. Close Engineering will also perform an audit of the maintenance process' configuration to identify opportunities to reduce its impact on system performance.
Latest: # 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 …
-
- Change indexing delayed ResolvedStarted Jun 03, 2026, 02:50 PM UTC · Resolved Jun 03, 2026, 06:53 PM UTC · 4h 2m
- Started May 12, 2026, 09:34 AM UTC · Resolved May 12, 2026, 11:17 AM UTC · 1h 42m
- Search Functionality Delayed ResolvedStarted Apr 23, 2026, 04:56 PM UTC · Resolved Apr 23, 2026, 07:44 PM UTC · 2h 47m
- Call Recordings Processing Delayed ResolvedStarted Apr 23, 2026, 04:16 PM UTC · Resolved Apr 23, 2026, 09:18 PM UTC · 5h 2m
- Database issues ResolvedStarted Mar 16, 2026, 04:08 PM UTC · Resolved Mar 16, 2026, 04:55 PM UTC · 47m