Critical incident

Close: Database issues

Affected: Application UI, API

Current status of Close: Operational — live Close status

Timeline

1. Mar 16, 2026, 16:08 UTC
   investigating
   We are currently investigating this issue.
2. Mar 16, 2026, 16:16 UTC
   investigating
   We are investigating the issue and seeing some recovery.
3. Mar 16, 2026, 16:27 UTC
   monitoring
   Database infrastructure is operational.
4. Mar 16, 2026, 16:45 UTC
   monitoring
   Close services continue to recover. Most customers should see normal performance. Close Engineering continues to monitor the recovery.
5. Mar 16, 2026, 16:55 UTC
   resolved
   This incident is resolved. Close has returned to normal performance.
6. Mar 17, 2026, 15:13 UTC
   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.

Updates as published by Close (original).