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 40 min ago. Last stored result reached it in 98 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 95 ms | 0 |
| Tue 19 | 0 | 0.0 | 100 ms | 0 |
| Tue 22 | 0 | 0.0 | 134 ms | 0 |
| Wed 00 | 0 | 0.0 | 76 ms | 0 |
| Wed 02 | 0 | 0.0 | 170 ms | 0 |
| Wed 04 | 0 | 0.0 | 196 ms | 0 |
| Wed 06 | 0 | 0.0 | 271 ms | 0 |
| Wed 09 | 0 | 0.0 | 216 ms | 0 |
| Wed 11 | 0 | 0.0 | 77 ms | 0 |
| Wed 13 | 0 | 0.0 | 287 ms | 0 |
| Wed 15 | 0 | 0.0 | 210 ms | 0 |
| Wed 17 | 0 | 0.0 | 297 ms | 0 |
| Wed 19 | 0 | 0.0 | 218 ms | 0 |
| Wed 22 | 0 | 0.0 | 142 ms | 0 |
| Thu 00 | 0 | 0.0 | 192 ms | 0 |
| Thu 02 | 0 | 0.0 | 230 ms | 0 |
| Thu 04 | 0 | 0.0 | 190 ms | 0 |
| Thu 06 | 0 | 0.0 | 196 ms | 0 |
| Thu 08 | 0 | 0.0 | 168 ms | 0 |
| Thu 10 | 0 | 0.0 | 181 ms | 0 |
| Thu 12 | 0 | 0.0 | 390 ms | 0 |
| Thu 14 | 0 | 0.0 | 96 ms | 0 |
| Thu 16 | 0 | 0.0 | 336 ms | 0 |
| Thu 18 | 0 | 0.0 | 194 ms | 0 |
| Thu 21 | 0 | 0.0 | 226 ms | 0 |
| Thu 23 | 0 | 0.0 | 173 ms | 0 |
| Fri 01 | 0 | 0.0 | 87 ms | 0 |
| Fri 03 | 0 | 0.0 | 88 ms | 0 |
| Fri 05 | 0 | 0.0 | 231 ms | 0 |
| Fri 07 | 0 | 0.0 | 235 ms | 0 |
| Fri 09 | 0 | 0.0 | 60 ms | 0 |
| Fri 10 | 0 | 0.0 | 90 ms | 0 |
| Fri 11 | 0 | 0.0 | 86 ms | 0 |
| Fri 12 | 0 | 0.0 | 109 ms | 0 |
| Fri 13 | 0 | 0.0 | 94 ms | 0 |
| Fri 15 | 0 | 0.0 | 165 ms | 0 |
| Fri 17 | 0 | 0.0 | 162 ms | 0 |
| Fri 18 | 0 | 0.0 | 182 ms | 0 |
| Fri 19 | 0 | 0.0 | 68 ms | 0 |
| Fri 21 | 0 | 0.0 | 95 ms | 0 |
| Fri 23 | 0 | 0.0 | 259 ms | 0 |
| Sat 01 | 0 | 0.0 | 168 ms | 0 |
| Sat 03 | 0 | 0.0 | 97 ms | 0 |
| Sat 05 | 0 | 0.0 | 160 ms | 0 |
| Sat 07 | 0 | 0.0 | 214 ms | 0 |
| Sat 09 | 0 | 0.0 | 255 ms | 0 |
| Sat 11 | 0 | 0.0 | 94 ms | 0 |
| Sat 14 | 0 | 0.0 | 98 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 AI or Not 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 AI or Not goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AI or Not alerts to Slack, Discord or a webhook — free.
We track AI or Not (aiornot.com) as part of the AI group. AI or Not is the leading AI detector for all content types: text (ChatGPT, Claude), image (Midjourney, 4o), music (Suno, Udio) & video (Veo, Kling)
AI or Not publishes an official status page at status.aiornot.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 152 ms average, 60–334 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AI or Not incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
152 ms on average over the last 24 hours (60–334 ms).
Yes, at https://status.aiornot.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 AI or Not here at once, the problem is on AI or Not'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 AI or Not. 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.