User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 39 min ago. Last stored result reached it in 52 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 113 ms | 0 |
| Mon 17 | 0 | 0.0 | 586 ms | 0 |
| Mon 19 | 0 | 0.0 | 262 ms | 0 |
| Mon 21 | 0 | 0.0 | 248 ms | 0 |
| Mon 22 | 0 | 0.0 | 233 ms | 0 |
| Tue 00 | 0 | 0.0 | 1154 ms | 0 |
| Tue 02 | 0 | 0.0 | 762 ms | 0 |
| Tue 04 | 0 | 0.0 | 422 ms | 0 |
| Tue 06 | 0 | 0.0 | 437 ms | 0 |
| Tue 08 | 0 | 0.0 | 240 ms | 0 |
| Tue 10 | 0 | 0.0 | 160 ms | 0 |
| Tue 12 | 0 | 0.0 | 540 ms | 0 |
| Tue 14 | 0 | 0.0 | 343 ms | 0 |
| Tue 17 | 0 | 0.0 | 610 ms | 0 |
| Tue 19 | 0 | 0.0 | 441 ms | 0 |
| Tue 21 | 0 | 0.0 | 259 ms | 0 |
| Wed 00 | 0 | 0.0 | 103 ms | 0 |
| Wed 02 | 0 | 0.0 | 449 ms | 0 |
| Wed 04 | 0 | 0.0 | 160 ms | 0 |
| Wed 06 | 0 | 0.0 | 204 ms | 0 |
| Wed 08 | 0 | 0.0 | 110 ms | 0 |
| Wed 11 | 0 | 0.0 | 394 ms | 0 |
| Wed 13 | 0 | 0.0 | 80 ms | 0 |
| Wed 15 | 0 | 0.0 | 488 ms | 0 |
| Wed 17 | 0 | 0.0 | 382 ms | 0 |
| Wed 19 | 0 | 0.0 | 379 ms | 0 |
| Wed 21 | 0 | 0.0 | 414 ms | 0 |
| Wed 23 | 0 | 0.0 | 332 ms | 0 |
| Thu 02 | 0 | 0.0 | 396 ms | 0 |
| Thu 04 | 0 | 0.0 | 423 ms | 0 |
| Thu 06 | 0 | 0.0 | 781 ms | 0 |
| Thu 08 | 0 | 0.0 | 591 ms | 0 |
| Thu 10 | 0 | 0.0 | 134 ms | 0 |
| Thu 12 | 0 | 0.0 | 294 ms | 0 |
| Thu 14 | 0 | 0.0 | 465 ms | 0 |
| Thu 16 | 0 | 0.0 | 352 ms | 0 |
| Thu 18 | 0 | 0.0 | 50 ms | 0 |
| Thu 20 | 0 | 0.0 | 298 ms | 0 |
| Thu 22 | 0 | 0.0 | 58 ms | 0 |
| Thu 23 | 0 | 0.0 | 78 ms | 0 |
| Fri 01 | 0 | 0.0 | 416 ms | 0 |
| Fri 03 | 0 | 0.0 | 493 ms | 0 |
| Fri 05 | 0 | 0.0 | 458 ms | 0 |
| Fri 07 | 0 | 0.0 | 504 ms | 0 |
| Fri 09 | 0 | 0.0 | 161 ms | 0 |
| Fri 11 | 0 | 0.0 | 108 ms | 0 |
| Fri 12 | 0 | 0.0 | 93 ms | 0 |
| Fri 14 | 0 | 0.0 | 306 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Certain 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 Certain goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Certain alerts to Slack, Discord or a webhook — free.
We track Certain (certain.com) as part of the AI group. Turn every attendee interaction into a high-fidelity sales signal. Certain is the AI-powered event intelligence platform for enterprise marketers.
Certain publishes an official status page at status.certain.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 263 ms average, 50–559 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Certain incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
263 ms on average over the last 24 hours (50–559 ms).
Yes, at https://status.certain.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Certain here at once, the problem is on Certain'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 Certain. 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.