User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
clearbit.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 130 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 281 ms | 0 |
| Mon 18 | 0 | 0.0 | 187 ms | 0 |
| Mon 20 | 0 | 0.0 | 171 ms | 0 |
| Mon 22 | 0 | 0.0 | 211 ms | 0 |
| Tue 01 | 0 | 0.0 | 234 ms | 0 |
| Tue 03 | 0 | 0.0 | 255 ms | 0 |
| Tue 05 | 0 | 0.0 | 218 ms | 0 |
| Tue 07 | 0 | 0.0 | 142 ms | 0 |
| Tue 09 | 0 | 0.0 | 183 ms | 0 |
| Tue 11 | 0 | 0.0 | 194 ms | 0 |
| Tue 13 | 0 | 0.0 | 175 ms | 0 |
| Tue 16 | 0 | 0.0 | 238 ms | 0 |
| Tue 18 | 0 | 0.0 | 216 ms | 0 |
| Tue 20 | 0 | 0.0 | 246 ms | 0 |
| Tue 22 | 0 | 0.0 | 236 ms | 0 |
| Wed 01 | 0 | 0.0 | 176 ms | 0 |
| Wed 03 | 0 | 0.0 | 115 ms | 0 |
| Wed 05 | 0 | 0.0 | 111 ms | 0 |
| Wed 07 | 0 | 0.0 | 246 ms | 0 |
| Wed 09 | 0 | 0.0 | 134 ms | 0 |
| Wed 10 | 0 | 0.0 | 98 ms | 0 |
| Wed 12 | 0 | 0.0 | 171 ms | 0 |
| Wed 13 | 0 | 0.0 | 318 ms | 0 |
| Wed 15 | 0 | 0.0 | 237 ms | 0 |
| Wed 17 | 0 | 0.0 | 260 ms | 0 |
| Wed 19 | 0 | 0.0 | 251 ms | 0 |
| Wed 21 | 0 | 0.0 | 201 ms | 0 |
| Wed 23 | 0 | 0.0 | 188 ms | 0 |
| Thu 02 | 0 | 0.0 | 213 ms | 0 |
| Thu 04 | 0 | 0.0 | 265 ms | 0 |
| Thu 06 | 0 | 0.0 | 255 ms | 0 |
| Thu 08 | 0 | 0.0 | 243 ms | 0 |
| Thu 10 | 0 | 0.0 | 183 ms | 0 |
| Thu 12 | 0 | 0.0 | 257 ms | 0 |
| Thu 14 | 0 | 0.0 | 206 ms | 0 |
| Thu 16 | 0 | 0.0 | 181 ms | 0 |
| Thu 18 | 0 | 0.0 | 79 ms | 0 |
| Thu 20 | 0 | 0.0 | 112 ms | 0 |
| Thu 22 | 0 | 0.0 | 131 ms | 0 |
| Fri 00 | 0 | 0.0 | 268 ms | 0 |
| Fri 02 | 0 | 0.0 | 242 ms | 0 |
| Fri 04 | 0 | 0.0 | 136 ms | 0 |
| Fri 06 | 0 | 0.0 | 160 ms | 0 |
| Fri 08 | 0 | 0.0 | 231 ms | 0 |
| Fri 10 | 0 | 0.0 | 81 ms | 0 |
| Fri 12 | 0 | 0.0 | 126 ms | 0 |
| Fri 14 | 0 | 0.0 | 115 ms | 0 |
| Fri 16 | 0 | 0.0 | 130 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Clearbit yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Clearbit goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clearbit alerts to Slack, Discord or a webhook — free.
We track Clearbit (clearbit.com) as part of the Cloud & developer group. Now reinvented with Artificial Intelligence—Clearbit is the first HubSpot Native Data Provider. Enrich your records, score, route, and reveal buying intent from your visitors.
Clearbit publishes an official status page at status.clearbit.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 151 ms average, 79–268 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Clearbit incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
151 ms on average over the last 24 hours (79–268 ms).
Yes, at https://status.clearbit.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Clearbit here at once, the problem is on Clearbit's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Clearbit. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.