User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
airops.com · 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 46 min ago. Last stored result reached it in 197 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 159 ms | 0 |
| Mon 17 | 0 | 0.0 | 81 ms | 0 |
| Mon 19 | 0 | 0.0 | 205 ms | 0 |
| Mon 21 | 0 | 0.0 | 154 ms | 0 |
| Mon 23 | 0 | 0.0 | 79 ms | 0 |
| Tue 02 | 0 | 0.0 | 116 ms | 0 |
| Tue 04 | 0 | 0.0 | 227 ms | 0 |
| Tue 06 | 0 | 0.0 | 272 ms | 0 |
| Tue 08 | 0 | 0.0 | 157 ms | 0 |
| Tue 10 | 0 | 0.0 | 97 ms | 0 |
| Tue 12 | 0 | 0.0 | 193 ms | 0 |
| Tue 14 | 0 | 0.0 | 340 ms | 0 |
| Tue 17 | 0 | 0.0 | 160 ms | 0 |
| Tue 19 | 0 | 0.0 | 132 ms | 0 |
| Tue 21 | 0 | 0.0 | 130 ms | 0 |
| Tue 23 | 0 | 0.0 | 244 ms | 0 |
| Wed 02 | 0 | 0.0 | 183 ms | 0 |
| Wed 04 | 0 | 0.0 | 137 ms | 0 |
| Wed 06 | 0 | 0.0 | 84 ms | 0 |
| Wed 08 | 0 | 0.0 | 107 ms | 0 |
| Wed 11 | 0 | 0.0 | 171 ms | 0 |
| Wed 13 | 0 | 0.0 | 156 ms | 0 |
| Wed 15 | 0 | 0.0 | 146 ms | 0 |
| Wed 17 | 0 | 0.0 | 178 ms | 0 |
| Wed 19 | 0 | 0.0 | 176 ms | 0 |
| Wed 21 | 0 | 0.0 | 152 ms | 0 |
| Thu 00 | 0 | 0.0 | 138 ms | 0 |
| Thu 02 | 0 | 0.0 | 275 ms | 0 |
| Thu 04 | 0 | 0.0 | 319 ms | 0 |
| Thu 06 | 0 | 0.0 | 163 ms | 0 |
| Thu 08 | 0 | 0.0 | 145 ms | 0 |
| Thu 10 | 0 | 0.0 | 150 ms | 0 |
| Thu 12 | 0 | 0.0 | 188 ms | 0 |
| Thu 14 | 0 | 0.0 | 233 ms | 0 |
| Thu 16 | 0 | 0.0 | 301 ms | 0 |
| Thu 18 | 0 | 0.0 | 87 ms | 0 |
| Thu 20 | 0 | 0.0 | 168 ms | 0 |
| Thu 22 | 0 | 0.0 | 340 ms | 0 |
| Fri 00 | 0 | 0.0 | 158 ms | 0 |
| Fri 02 | 0 | 0.0 | 115 ms | 0 |
| Fri 04 | 0 | 0.0 | 454 ms | 0 |
| Fri 06 | 0 | 0.0 | 165 ms | 0 |
| Fri 09 | 0 | 0.0 | 113 ms | 0 |
| Fri 10 | 0 | 0.0 | 95 ms | 0 |
| Fri 11 | 0 | 0.0 | 192 ms | 0 |
| Fri 12 | 0 | 0.0 | 100 ms | 0 |
| Fri 14 | 0 | 0.0 | 277 ms | 0 |
| Fri 16 | 0 | 0.0 | 197 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 AirOps 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 AirOps goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AirOps alerts to Slack, Discord or a webhook — free.
AirOps is listed in our AI category and checked at airops.com. Build an AI discovery strategy that earns trust across the web, gets your brand chosen by AI, and drives growth with AirOps.
AirOps publishes an official status page at status.airops.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 184 ms average, 44–454 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 AirOps incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
184 ms on average over the last 24 hours (44–454 ms).
Yes, at https://status.airops.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 AirOps here at once, the problem is on AirOps'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 AirOps. 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.