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 24 min ago. Last stored result reached it in 63 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 114 ms | 0 |
| Nov 7 | 0 | 0.0 | 81 ms | 0 |
| Nov 7 | 0 | 0.0 | 61 ms | 0 |
| Nov 7 | 0 | 0.0 | 87 ms | 0 |
| Nov 7 | 0 | 0.0 | 78 ms | 0 |
| Nov 8 | 0 | 0.0 | 138 ms | 0 |
| Nov 8 | 0 | 0.0 | 83 ms | 0 |
| Nov 8 | 0 | 0.0 | 77 ms | 0 |
| Nov 8 | 0 | 0.0 | 180 ms | 0 |
| Nov 9 | 0 | 0.0 | 128 ms | 0 |
| Nov 9 | 0 | 0.0 | 86 ms | 0 |
| Nov 9 | 0 | 0.0 | 95 ms | 0 |
| Nov 9 | 0 | 0.0 | 225 ms | 0 |
| Nov 10 | 0 | 0.0 | 137 ms | 0 |
| Nov 10 | 0 | 0.0 | 139 ms | 0 |
| Nov 10 | 0 | 0.0 | 133 ms | 0 |
| Nov 10 | 0 | 0.0 | 95 ms | 0 |
| Nov 11 | 0 | 0.0 | 183 ms | 0 |
| Nov 11 | 0 | 0.0 | 125 ms | 0 |
| Nov 11 | 0 | 0.0 | 110 ms | 0 |
| Nov 11 | 0 | 0.0 | 113 ms | 0 |
| Nov 12 | 0 | 0.0 | 181 ms | 0 |
| Nov 12 | 0 | 0.0 | 226 ms | 0 |
| Nov 12 | 0 | 0.0 | 206 ms | 0 |
| Nov 12 | 0 | 0.0 | 103 ms | 0 |
| Nov 13 | 0 | 0.0 | 104 ms | 0 |
| Nov 13 | 0 | 0.0 | 99 ms | 0 |
| Nov 13 | 0 | 0.0 | 162 ms | 0 |
| Nov 13 | 0 | 0.0 | 113 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 Air 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 Air goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Air alerts to Slack, Discord or a webhook — free.
Air, at air.inc, is one of the AI services we monitor. AI that understands your brand, organizes your library, and scales creative while keeping humans involved where they matter most.
Air publishes an official status page at status.air.inc; 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: 124 ms average, 63–241 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Air incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
124 ms on average over the last 24 hours (63–241 ms).
Yes, at https://status.air.inc.
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 Air here at once, the problem is on Air'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 Air. 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.