Change indexing delayed
Resolved
This incident has been resolved. The Close app and API are now functioning normally.
Jun 3, 2:50 PMResolved Jun 3, 6:53 PMMinorIndexing
Status Provider
Home
/
Status
/
Service
Operational
Close Status
All-in-one CRM for growing teams.
Source
auto
Category
Communication
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 5m ago
23
Components
0
Active incidents
0
Maintenance
25%
90d uptime
Change indexing delayed
Jun 3, 2:50 PM
Service health overview
Operational snapshot
Normalized official status-page data for incidents, maintenance, components, and history.
25%
Known uptime
4 known history days
23
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Top affected components
Components with the most recent status-page events.
API
Operational
1
Application UI
Operational
1
Calendar - Syncing
Operational
1
Call Recording
Operational
1
Dialer
Operational
1
90-day status history
Daily rollup
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
3
outage days
0
maintenance days
86
unknown days
Recent incidents
Official incidents
Latest outages and degradations detected from the official status page.
Partial outage - connection issues and application errors
Resolved
This incident has been resolved.
May 12, 9:34 AMResolved May 12, 11:17 AMMajorDialerIncoming Calls
Search Functionality Delayed
Resolved
This incident has been resolved.
Apr 23, 4:56 PMResolved Apr 23, 7:44 PMMinorIndexing
Call Recordings Processing Delayed
Resolved
This incident has been resolved.
Apr 23, 4:16 PMResolved Apr 23, 9:18 PMMinorCall Recording
Database issues
Postmortem
# 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.
Mar 16, 4:08 PMResolved Mar 16, 4:55 PMCriticalApplication UIAPI
Calling problems in the Desktop Application
Resolved
The issue has been resolved. Please reach out to support@close.com if you continue to have calling issues after refreshing.
Nov 5, 6:42 PMResolved Nov 5, 7:56 PMNone
Application Slowness
Resolved
This incident has been resolved.
Nov 1, 8:55 AMResolved Nov 1, 10:53 AMMinorApplication UIAPI
Experiencing delays on Dialer Sessions
Postmortem
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, Wednesday 10/22 7:50–17:00 UTC, and Thursday 10/23 8:00–15:00 UTC, customers relying on real-time updates in Close \(which is critical for proper & timely functioning of our calling features and the Dialer\) experienced delays, outdated data being displayed on their screens, Dialer disconnections, and other unexpected behavior. ### Root Cause and Resolution On Monday 10/20 at 20:09 UTC, a subtle bug was introduced, which resulted in UI clients slowly opening more and more WebSocket subscriptions for our Data Monitoring Service – a component which powers real-time updates for our Activity Reporting pages. Over the next few days, the number of subscriptions kept rising. The rise was slow enough where it didn’t trigger our alerting, but fast enough to eventually start putting a real strain on our infrastructure and saturating our processing capacity. Our first course of action was to scale the supply to meet the demand, but the demand continued to rise more quickly. Because of unrelated rate-limiting changes that looked more directly responsible for the limitation of the supply, our engineering efforts went in a few wrong directions until finally the root cause – the UI bug – was identified and fixed on Thu 10/23 at 5:19 UTC. However, because the fix required clients to reload their UI, intermittent problems continued until enough clients have reloaded, finally resolving the problem on Thu 10/23 at 15:00 UTC. To prevent this problem from ever happening again, we are improving our monitoring, alerting, testing, and in the longer-term the architecture of our WebSocket subscription service. ### Timeline * Mon 10/20 20:09 UTC: A subtle bug is introduced and over the next few days keeps slowly increasing the number of WebSocket-based Data Monitoring Service subscriptions. * Tue 10/21 14:46 UTC: Close receives first signals of Dialer problems where Users hear the callee many seconds before the corresponding Lead Page loads and immediately start looking into the problem. * Tue 10/21 5:24 UTC: First fixes aimed at increasing the allowed rate of processing of the system land in production. The situation appears resolved. * Wed 10/22 7:50 UTC: The problem comes back despite the fixes. Engineers increase the scale of the system to meet the increasing demand, but the demand keeps saturating the scale. Status page is opened at 10:35 UTC \([https://status.close.com/incidents/ydzwc4l6xmhc](https://status.close.com/incidents/ydzwc4l6xmhc)\). Problems continue on and off until they fully subside around 17:00 UTC * Thu 10/23 5:19 UTC: Engineers identify the root cause and fix it. * Thu 10/23 8:00 UTC: Concerning metrics continue to emerge despite the fix. Customer reports follow and Status page is opened at 11:40 UTC \([https://status.close.com/incidents/j49qgd3m049n](https://status.close.com/incidents/j49qgd3m049n)\). Engineers continue working on the impact mitigation and root cause diagnosis until it is found and fixed at 11:47 UTC \(excessive WebSocket Subscriptions for our real-time Data Monitoring Service, coming from UI clients who visited the Activity Reporting page\). However, the fix being picked up requires some idle UI clients to reload, hence the saturated demand continues until 15 UTC despite scaling attempts. * Thu 10/23 15:00 UTC: The problem is officially resolved.
Oct 23, 11:40 AMResolved Oct 23, 3:52 PMMinorDialer
Experiencing Delays on Dialer Sessions
Resolved
This incident has been resolved.
Oct 22, 10:35 AMResolved Oct 22, 11:50 AMMinorDialer
Service interruption
Resolved
This incident has been resolved.
Oct 20, 2:20 PMResolved Oct 20, 8:27 PMMajorPhone ServiceOutgoing Calls
Recent maintenance
Maintenance windows
Scheduled and completed maintenance windows are separated from incidents.
Database Maintenance
Completed
The scheduled maintenance has been completed.
Apr 9, 4:00 AMResolved Apr 9, 4:35 AMMaintenanceApplication UIAPI
Database Maintenance
Completed
This maintenance has been canceled.
Apr 2, 4:00 AMResolved Apr 1, 2:17 PMMaintenanceApplication UIAPI
Infrastructure Maintenance
Completed
The scheduled maintenance has been completed.
Nov 26, 6:00 AMResolved Nov 26, 6:30 AMMaintenanceApplication UIAPI
Database Maintenance
Completed
The scheduled maintenance has been completed.
Oct 16, 4:00 AMResolved Oct 16, 4:30 AMMaintenanceQueryingApplication UI
Database Maintenance
Completed
The scheduled maintenance has been completed.
Jul 31, 5:00 AMResolved Jul 31, 5:15 AMMaintenance
OAuth Database maintenance
Completed
The scheduled maintenance has been completed.
Jun 19, 5:00 AMResolved Jun 19, 5:14 AMMaintenance
Infrastructure Maintenance
Completed
The scheduled maintenance has been completed.
Jun 8, 3:00 AMResolved Jun 8, 3:50 AMMaintenanceApplication UIAPI
Database Maintenance
Completed
The scheduled maintenance has been completed.
Apr 11, 5:00 AMResolved Apr 11, 5:29 AMMaintenanceApplication UIAPI
Infrastructure Maintenance
Completed
The scheduled maintenance has been completed.
Feb 21, 4:00 AMResolved Feb 21, 4:17 AMMaintenanceApplication UIAPI
Database maintenance
Completed
The scheduled maintenance has been completed.
Feb 20, 8:00 AMResolved Feb 20, 8:51 AMMaintenanceAPI
About the Close status page integration
Uptimus tracks the official Close status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.close.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Outage map preview
Regional reports can be layered on top of official provider status when user signals are available.
Close components
Tracked components
Showing 1 to 23 of 23 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Search Smart Views, Leads search, Inbox, Reporting, Opportunities list page | Operational | Group | Not recorded |
Operational | Group | Not recorded | |
Phone Incoming and outgoing calls | Operational | Group | Not recorded |
Application UI UI of the Close.io application (web + native apps) | Operational | Component | Not recorded |
Indexing Lead indexing (updates to existing leads and the creation of new leads) | Operational | Component | Not recorded |
Phone Service Close.io-specific portions of our calling integration | Operational | Component | Not recorded |
Syncing Indicates if we're pulling emails from IMAP accounts into Close.io quickly | Operational | Component | Not recorded |
API Backend JSON service that powers the Developer API directly, as well as the data behind the App. | Operational | Component | Not recorded |
Incoming Calls | Operational | Component | Not recorded |
Querying | Operational | Component | Not recorded |
Sending Emails sent from within Close.io | Operational | Component | Not recorded |
Outgoing Calls | Operational | Component | Not recorded |
Public Website Marketing homepage / website | Operational | Component | Not recorded |
Dialer Overall health and availability of the Power Dialer and the Predictive Dialer. | Operational | Component | Not recorded |
Call Recording Twilio Call Recording API | Operational | Component | Not recorded |
SMS Twilio SMS API | Operational | Component | Not recorded |
Support Center Our FAQ site on help.close.io | Operational | Component | Not recorded |
Telephony Provider Connectivity Twilio Web Client | Operational | Component | Not recorded |
Calendar - Syncing | Operational | Component | Not recorded |
Downstream Telephony Carriers Twilio PSTN connectivity | Operational | Component | Not recorded |
Outgoing Calls - Infrastructure (Twilio Conference Calling API) Twilio's Conference Calling API | Operational | Component | Not recorded |
Outgoing Calls - Infrastructure (Twilio REST API) Twilio REST API | Operational | Component | Not recorded |
Outgoing Calls - Infrastructure (Twilio TwiML) Twilio TwiML | Operational | Component | Not recorded |
Get notified when Close changes status
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Show Close on your own status page
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Users also follow these services
Related status pages based on category, adapter type, and operational history.
Frequently asked questions
Is Close down right now?
Close is currently marked as Operational in Uptimus based on the latest official status page check.
How often does Uptimus check Close?
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
Are maintenance windows counted as incidents?
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Can I get alerts for Close?
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.