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 34 min ago. Last stored result reached it in 250 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 415 ms | 0 |
| Mon 17 | 0 | 0.0 | 328 ms | 0 |
| Mon 19 | 0 | 0.0 | 371 ms | 0 |
| Mon 22 | 0 | 0.0 | 348 ms | 0 |
| Tue 00 | 0 | 0.0 | 275 ms | 0 |
| Tue 02 | 0 | 0.0 | 446 ms | 0 |
| Tue 04 | 0 | 0.0 | 353 ms | 0 |
| Tue 06 | 0 | 0.0 | 400 ms | 0 |
| Tue 08 | 0 | 0.0 | 397 ms | 0 |
| Tue 10 | 0 | 0.0 | 336 ms | 0 |
| Tue 12 | 0 | 0.0 | 328 ms | 0 |
| Tue 15 | 0 | 0.0 | 318 ms | 0 |
| Tue 17 | 0 | 0.0 | 236 ms | 0 |
| Tue 19 | 0 | 0.0 | 240 ms | 0 |
| Tue 21 | 0 | 0.0 | 327 ms | 0 |
| Wed 00 | 0 | 0.0 | 335 ms | 0 |
| Wed 02 | 0 | 0.0 | 165 ms | 0 |
| Wed 04 | 0 | 0.0 | 365 ms | 0 |
| Wed 06 | 0 | 0.0 | 335 ms | 0 |
| Wed 08 | 0 | 0.0 | 369 ms | 0 |
| Wed 11 | 0 | 0.0 | 207 ms | 0 |
| Wed 13 | 0 | 0.0 | 358 ms | 0 |
| Wed 15 | 0 | 0.0 | 381 ms | 0 |
| Wed 17 | 0 | 0.0 | 391 ms | 0 |
| Wed 19 | 0 | 0.0 | 374 ms | 0 |
| Wed 21 | 0 | 0.0 | 411 ms | 0 |
| Thu 00 | 0 | 0.0 | 562 ms | 0 |
| Thu 02 | 0 | 0.0 | 522 ms | 0 |
| Thu 04 | 0 | 0.0 | 414 ms | 0 |
| Thu 06 | 0 | 0.0 | 281 ms | 0 |
| Thu 08 | 0 | 0.0 | 431 ms | 0 |
| Thu 10 | 0 | 0.0 | 320 ms | 0 |
| Thu 12 | 0 | 0.0 | 410 ms | 0 |
| Thu 14 | 0 | 0.0 | 394 ms | 0 |
| Thu 16 | 0 | 0.0 | 252 ms | 0 |
| Thu 18 | 0 | 0.0 | 223 ms | 0 |
| Thu 20 | 0 | 0.0 | 293 ms | 0 |
| Thu 22 | 0 | 0.0 | 295 ms | 0 |
| Fri 00 | 0 | 0.0 | 312 ms | 0 |
| Fri 02 | 0 | 0.0 | 290 ms | 0 |
| Fri 05 | 0 | 0.0 | 492 ms | 0 |
| Fri 07 | 0 | 0.0 | 376 ms | 0 |
| Fri 09 | 0 | 0.0 | 312 ms | 0 |
| Fri 10 | 0 | 0.0 | 235 ms | 0 |
| Fri 11 | 0 | 0.0 | 311 ms | 0 |
| Fri 12 | 0 | 0.0 | 320 ms | 0 |
| Fri 14 | 0 | 0.0 | 348 ms | 0 |
| Fri 16 | 0 | 0.0 | 250 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 comet 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 comet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send comet alerts to Slack, Discord or a webhook — free.
comet is listed in our AI category and checked at comet.com. Comet is the creator of Opik, an end-to-end AI observability platform for developers with best-in-class agent testing, optimization, and monitoring.
comet publishes an official status page at status.comet.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 312 ms average, 223–492 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public comet incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
312 ms on average over the last 24 hours (223–492 ms).
Yes, at https://status.comet.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 comet here at once, the problem is on comet'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 comet. 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.