- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Clearbit. 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 0m it lasted.
Anything that failed between 2025-05-05 17:36 UTC and 2025-05-03 01:00 UTC may need a replay.Subscribe to Clearbit's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=clearbit works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Clearbit 1
- resolved
On Saturday May 3 (UTC), between 1:00 AM and 7:00 AM UTC (6:00 PM to 12:00 AM Friday May 2 Pacific Time), customers using our legacy Segment, Marketo, and HubSpot integrations, as well as those using webhooks in our Enrichment API, were affected by a processing failure. Enrichments requested via API for webhook delivery, or through the aforementioned legacy integrations were not delivered. To ensure processing, enrichment requests from that time period will need to be resubmitted. The issue has been resolved, and all systems are now operating normally. We're continuing to monitor performance and assess preventive measures.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-58fba15f97
Is Clearbit still down?
No, this incident was resolved 2025-05-03 01:00 UTC. For Clearbit's live state, see https://down.guide/clearbit.
How long did it last?
0m, from 2025-05-05 17:36 UTC to 2025-05-03 01:00 UTC, by the times Clearbit posted.
What caused it?
Clearbit hasn't published a root cause. If it does, it shows here.
Where does this come from?
Clearbit's official status page, https://status.clearbit.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.