Clearbit Outage History
9 incidents recorded over the last 365 days, 4 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 Clearbit Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 18, 2026 | Salesforce synchronization issuesThis incident has been resolved. | 117h 13m | Resolved |
| Sep 1, 2026 | Authentication errorsBetween 4:55 AM and 5:15 AM PST, some users experienced authentication errors that prevented them from logging in or using the Clearbit platform and APIs. Our engineering team identified and fully resolved the root… | -93 min | Resolved |
| Jun 7, 2026 | Database maintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| May 25, 2026 | Database maintenanceThe scheduled maintenance has been completed. | 7h 0m | Scheduled |
| Feb 11, 2026 | Audience results delayThis incident has been resolved. Company and Person Audiences are functioning as normal. | 39h 23m | Resolved |
| Jan 19, 2026 | Segment database maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 17, 2025 | Batch enrichment processing delaysThis incident has been resolved. | 114h 33m | Resolved |
| Nov 28, 2025 | Marketo maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 12, 2025 | Elevated API ErrorsThe scheduled maintenance has been completed. | 24h 0m | Scheduled |
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 Clearbit 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 Clearbit 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 Clearbit 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 Clearbit outage in this window ran 4d 21h, against a mean recovery of 1d 14h. If you depend on Clearbit 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.