Close Outage History
12 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Close Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | App is unavailable for some customersThis incident has been resolved. | 28 min | Resolved |
| Oct 8, 2026 | Email - SyncingThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Sep 29, 2026 | Application impairmentClose 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… | 26 min | Resolved |
| Aug 11, 2026 | Database Failures## Summary & Impact Close sincerely apologizes for the interruption of our service. We take the stability of our platform very seriously, and this incident is not acceptable to us. Below is an explanation of what… | 2h 3m | Resolved |
| Aug 11, 2026 | Database FailuresThis incident has been resolved. | 59 min | Resolved |
| Jun 29, 2026 | Background Task Processing DelaysThis incident has been resolved. Background tasks are processing normally. | 1h 53m | Resolved |
| Jun 3, 2026 | Change indexing delayedThis incident has been resolved. The Close app and API are now functioning normally. | 4h 2m | Resolved |
| May 12, 2026 | Partial outage - connection issues and application errorsThis incident has been resolved. | 1h 42m | Resolved |
| Apr 23, 2026 | Search Functionality DelayedThis incident has been resolved. | 2h 47m | Resolved |
| Apr 23, 2026 | Call Recordings Processing DelayedThis incident has been resolved. | 5h 2m | Resolved |
| Mar 16, 2026 | Database issues# 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… | 47 min | Resolved |
| Nov 5, 2025 | Calling problems in the Desktop ApplicationThe issue has been resolved. Please reach out to support@close.com if you continue to have calling issues after refreshing. | 1h 13m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Close incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Close Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Close acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Close outage in this window ran 5h 2m, against a mean recovery of 2h 7m. If you depend on Close in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.