Database issues

What to do

• Check whether you use Close Application UI, API. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 47m it lasted.

  Anything that failed between 2026-03-16 16:08 UTC and 2026-03-16 16:55 UTC may need a replay.

• Subscribe to Close's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=close works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Close 6

1. investigatingMar 16, 2026, 4:08 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingMar 16, 2026, 4:16 PM UTC

   We are investigating the issue and seeing some recovery.

   provider

3. monitoringMar 16, 2026, 4:27 PM UTC

   Database infrastructure is operational.

   provider

4. monitoringMar 16, 2026, 4:45 PM UTC

   Close services continue to recover. Most customers should see normal performance. Close Engineering continues to monitor the recovery.

   provider

5. resolvedMar 16, 2026, 4:55 PM UTC

   This incident is resolved. Close has returned to normal performance.

   provider

6. postmortemMar 17, 2026, 3: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.