- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Webhooks
- Down Index
- 43of 100
What to do
Check whether you use Clearbit Webhooks. 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 2d 17h it lasted.
Anything that failed between 2025-05-03 00:35 UTC and 2025-05-05 17:36 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 4
- investigating
We're currently investigating a potential issue with webhook processing. Webhooks may not be delivering as expected. This issue appears to have started around 8:00 PM UTC (1:00 PM Pacific Time). We'll provide updates as we learn more.
provider
- monitoring
We've identified and resolved the issue affecting webhook processing. Queued webhooks are now being delivered, and the system is catching up. We'll continue to monitor performance closely until processing is fully up to date.
provider
- monitoring
While monitoring the issue, we discovered that the earlier fix did not fully resolve the problem. As a result, webhooks submitted between 1:00 AM and 7:00 AM UTC (6:00 PM to 12:00 AM Pacific Time) were not processed and cannot be recovered. To ensure delivery, these webhooks will need to be re-submitted. We implemented a fix, and are again monitoring.
provider
- resolved
This incident has been resolved.
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-3761f735d9
Is Clearbit still down?
No, this incident was resolved 2025-05-05 17:36 UTC. For Clearbit's live state, see https://down.guide/clearbit.
How long did it last?
2d 17h, from 2025-05-03 00:35 UTC to 2025-05-05 17:36 UTC, by the times Clearbit posted.
What was affected?
Clearbit named Webhooks.
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.