Close: Call Recordings Processing Delayed

What to do

Check whether you use Close Call Recording. 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 5h 2m it lasted.
Anything that failed between 2026-04-23 16:16 UTC and 2026-04-23 21:18 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.

investigatingApr 23, 2026, 4:16 PM UTC
We are currently investigating this issue.
provider
investigatingApr 23, 2026, 4:56 PM UTC
We are experiencing an issue with a 3rd party provider.
provider
monitoringApr 23, 2026, 5:32 PM UTC
We are experiencing an issue with a 3rd party provider.
provider
monitoringApr 23, 2026, 6:52 PM UTC
We're continuing to monitor the situation and expect gradual recovery over the next hour.
provider
monitoringApr 23, 2026, 7:45 PM UTC
We're continuing to monitor the situation and expect gradual recovery over the next hour.
provider
resolvedApr 23, 2026, 9:18 PM 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-04-23 21:18 UTC. For Close's live state, see https://down.guide/close.

How long did it last?

5h 2m, from 2026-04-23 16:16 UTC to 2026-04-23 21:18 UTC, by the times Close posted.

What was affected?

Close named Call Recording.

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.