Close outage, 16 March 2026

Database issues

Started
Resolved
16 Mar 2026, 16:55 UTC (after 47 min)
Impact
Critical
Affected
Application UI, API

Last update from Close

# 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 | **In...

17 Mar 2026, 15:13 UTC

Read the full incident on the official Close status page

Is Close down now?

This page is the record of one past incident. For the live status, see Is Close down right now? - it reads the official status page every 2 minutes.

Other Close incidents

  1. Application impairment

  2. Database Failures

  3. Database Failures

  4. Background Task Processing Delays

  5. Change indexing delayed

  6. Partial outage - connection issues and application errors

  7. Search Functionality Delayed

  8. Call Recordings Processing Delayed

All recorded Close incidents