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 3 min ago. Last stored result reached it in 138 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 123 ms | 0 |
| Tue 00 | 0 | 0.0 | 199 ms | 0 |
| Tue 02 | 0 | 0.0 | 756 ms | 0 |
| Tue 04 | 0 | 0.0 | 233 ms | 0 |
| Tue 06 | 0 | 0.0 | 321 ms | 0 |
| Tue 08 | 0 | 0.0 | 251 ms | 0 |
| Tue 10 | 0 | 0.0 | 118 ms | 0 |
| Tue 12 | 0 | 0.0 | 258 ms | 0 |
| Tue 14 | 0 | 0.0 | 185 ms | 0 |
| Tue 17 | 0 | 0.0 | 360 ms | 0 |
| Tue 19 | 0 | 0.0 | 407 ms | 0 |
| Tue 21 | 0 | 0.0 | 512 ms | 0 |
| Tue 23 | 0 | 0.0 | 53 ms | 0 |
| Wed 02 | 0 | 0.0 | 120 ms | 0 |
| Wed 04 | 0 | 0.0 | 539 ms | 0 |
| Wed 06 | 0 | 0.0 | 136 ms | 0 |
| Wed 08 | 0 | 0.0 | 115 ms | 0 |
| Wed 11 | 0 | 0.0 | 75 ms | 0 |
| Wed 13 | 0 | 0.0 | 146 ms | 0 |
| Wed 15 | 0 | 0.0 | 497 ms | 0 |
| Wed 17 | 0 | 0.0 | 420 ms | 0 |
| Wed 19 | 0 | 0.0 | 337 ms | 0 |
| Wed 21 | 0 | 0.0 | 285 ms | 0 |
| Thu 00 | 0 | 0.0 | 187 ms | 0 |
| Thu 02 | 0 | 0.0 | 578 ms | 0 |
| Thu 04 | 0 | 0.0 | 344 ms | 0 |
| Thu 06 | 0 | 0.0 | 199 ms | 0 |
| Thu 08 | 0 | 0.0 | 71 ms | 0 |
| Thu 10 | 0 | 0.0 | 165 ms | 0 |
| Thu 12 | 0 | 0.0 | 451 ms | 0 |
| Thu 14 | 0 | 0.0 | 123 ms | 0 |
| Thu 16 | 0 | 0.0 | 148 ms | 0 |
| Thu 18 | 0 | 0.0 | 121 ms | 0 |
| Thu 21 | 0 | 0.0 | 160 ms | 0 |
| Thu 22 | 0 | 0.0 | 173 ms | 0 |
| Fri 00 | 0 | 0.0 | 171 ms | 0 |
| Fri 03 | 0 | 0.0 | 153 ms | 0 |
| Fri 05 | 0 | 0.0 | 159 ms | 0 |
| Fri 07 | 0 | 0.0 | 118 ms | 0 |
| Fri 09 | 0 | 0.0 | 111 ms | 0 |
| Fri 10 | 0 | 0.0 | 91 ms | 0 |
| Fri 11 | 0 | 0.0 | 385 ms | 0 |
| Fri 13 | 0 | 0.0 | 223 ms | 0 |
| Fri 15 | 0 | 0.0 | 176 ms | 0 |
| Fri 17 | 0 | 0.0 | 349 ms | 0 |
| Fri 19 | 0 | 0.0 | 64 ms | 0 |
| Fri 21 | 0 | 0.0 | 193 ms | 0 |
| Fri 23 | 0 | 0.0 | 138 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Caido 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 Caido goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Caido alerts to Slack, Discord or a webhook — free.
We track Caido (caido.io) as part of the AI group. The web hacking toolkit designed to scale manual testing through AI and teamwork.
Caido publishes an official status page at status.caido.io; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 186 ms average, 64–568 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 Caido incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
186 ms on average over the last 24 hours (64–568 ms).
Yes, at https://status.caido.io.
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 Caido here at once, the problem is on Caido'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 Caido. 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.