User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
trycomp.ai · 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 44 min ago. Last stored result reached it in 491 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 510 ms | 0 |
| Mon 20 | 0 | 0.0 | 511 ms | 0 |
| Mon 22 | 0 | 0.0 | 615 ms | 0 |
| Tue 00 | 0 | 0.0 | 569 ms | 0 |
| Tue 02 | 0 | 0.0 | 762 ms | 0 |
| Tue 05 | 0 | 0.0 | 389 ms | 0 |
| Tue 07 | 0 | 0.0 | 503 ms | 0 |
| Tue 09 | 0 | 0.0 | 543 ms | 0 |
| Tue 11 | 0 | 0.0 | 520 ms | 0 |
| Tue 13 | 0 | 0.0 | 480 ms | 0 |
| Tue 15 | 0 | 0.0 | 473 ms | 0 |
| Tue 18 | 0 | 0.0 | 513 ms | 0 |
| Tue 20 | 0 | 0.0 | 426 ms | 0 |
| Tue 22 | 0 | 0.0 | 578 ms | 0 |
| Wed 00 | 0 | 0.0 | 540 ms | 0 |
| Wed 03 | 0 | 0.0 | 592 ms | 0 |
| Wed 05 | 0 | 0.0 | 691 ms | 0 |
| Wed 07 | 0 | 0.0 | 421 ms | 0 |
| Wed 09 | 0 | 0.0 | 612 ms | 0 |
| Wed 12 | 0 | 0.0 | 523 ms | 0 |
| Wed 14 | 0 | 0.0 | 426 ms | 0 |
| Wed 16 | 0 | 0.0 | 433 ms | 0 |
| Wed 18 | 0 | 0.0 | 449 ms | 0 |
| Wed 20 | 0 | 0.0 | 577 ms | 0 |
| Wed 22 | 0 | 0.0 | 435 ms | 0 |
| Thu 00 | 0 | 0.0 | 504 ms | 0 |
| Thu 03 | 0 | 0.0 | 480 ms | 0 |
| Thu 05 | 0 | 0.0 | 423 ms | 0 |
| Thu 07 | 0 | 0.0 | 680 ms | 0 |
| Thu 09 | 0 | 0.0 | 536 ms | 0 |
| Thu 11 | 0 | 0.0 | 490 ms | 0 |
| Thu 13 | 0 | 0.0 | 509 ms | 0 |
| Thu 15 | 0 | 0.0 | 392 ms | 0 |
| Thu 16 | 0 | 0.0 | 395 ms | 0 |
| Thu 19 | 0 | 0.0 | 529 ms | 0 |
| Thu 21 | 0 | 0.0 | 493 ms | 0 |
| Thu 22 | 0 | 0.0 | 565 ms | 0 |
| Fri 01 | 0 | 0.0 | 508 ms | 0 |
| Fri 03 | 0 | 0.0 | 585 ms | 0 |
| Fri 05 | 0 | 0.0 | 475 ms | 0 |
| Fri 07 | 0 | 0.0 | 458 ms | 0 |
| Fri 09 | 0 | 0.0 | 667 ms | 0 |
| Fri 11 | 0 | 0.0 | 636 ms | 0 |
| Fri 13 | 0 | 0.0 | 447 ms | 0 |
| Fri 15 | 0 | 0.0 | 486 ms | 0 |
| Fri 17 | 0 | 0.0 | 495 ms | 0 |
| Fri 18 | 0 | 0.0 | 522 ms | 0 |
| Fri 19 | 0 | 0.0 | 491 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 Comp AI 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 Comp AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Comp AI alerts to Slack, Discord or a webhook — free.
We track Comp AI (trycomp.ai) as part of the AI group. Automate SOC 2, ISO 27001, HIPAA, and GDPR. 580+ integrations, 1,000+ companies, audit-ready in days, with audit and pentest included.
Comp AI publishes an official status page at status.trycomp.ai; 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: 531 ms average, 447–759 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Comp AI incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
531 ms on average over the last 24 hours (447–759 ms).
Yes, at https://status.trycomp.ai.
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 Comp AI here at once, the problem is on Comp AI'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 Comp AI. 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.