- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard
- Down Index
- 33of 100
What to do
Check whether you use Clearbit Dashboard. 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-06-06 21:27 UTC and 2025-06-09 14:37 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 3
- identified
We're currently experiencing an issue that's preventing Audiences from being processed for Google Ads. Processing will resume once a fix is in place. We're actively working to resolve the issue and will share updates as they become available.
provider
- monitoring
We've implemented a fix, and Google Ads Audience processing has resumed. Delayed jobs are now running, and we're monitoring the system to ensure everything runs as expected.
provider
- resolved
This incident has been resolved, Google Ads Audiences are processing normally.
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-f43f86070b
Is Clearbit still down?
No, this incident was resolved 2025-06-09 14:37 UTC. For Clearbit's live state, see https://down.guide/clearbit.
How long did it last?
2d 17h, from 2025-06-06 21:27 UTC to 2025-06-09 14:37 UTC, by the times Clearbit posted.
What was affected?
Clearbit named Dashboard.
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.