Close: Database Failures

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 59m it lasted.
Anything that failed between 2026-08-11 08:26 UTC and 2026-08-11 09:26 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.

investigatingAug 11, 2026, 8:26 AM UTC
We are currently investigating an elevated number of database failures.
provider
identifiedAug 11, 2026, 8:54 AM UTC
We have identified an issue impacting our production database. Close Engineering is taking action to restore functionality. Users should notice improved performance over the next several minutes.
provider
monitoringAug 11, 2026, 9:04 AM UTC
We have remediated the issue with our production database. Users should be able to use the Close app normally. Close Engineering is monitoring system performance to confirm resolution.
provider
resolvedAug 11, 2026, 9:26 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Close still down?

No, this incident was resolved 2026-08-11 09:26 UTC. For Close's live state, see https://down.guide/close.

How long did it last?

59m, from 2026-08-11 08:26 UTC to 2026-08-11 09:26 UTC, by the times Close posted.

What was affected?

Close named Application UI, API.

What caused it?

Close hasn't published a root cause. If it does, it shows here.

Where does this come from?

Close's official status page, https://status.close.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.