User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
Estimated fix: Not enough Kilo history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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 59 min ago. Last stored result reached it in 476 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:30 | 0 | 0.0 | 260 ms | 0 |
| 10:30 | 0 | 0.0 | 386 ms | 0 |
| 12:45 | 0 | 0.0 | 328 ms | 0 |
| 14:45 | 0 | 0.0 | 687 ms | 0 |
| 16:45 | 0 | 0.0 | 408 ms | 0 |
| 19:00 | 0 | 0.0 | 308 ms | 0 |
| 21:00 | 0 | 0.0 | 450 ms | 0 |
| 23:00 | 0 | 0.0 | 311 ms | 0 |
| 01:00 | 0 | 0.0 | 519 ms | 0 |
| 03:15 | 0 | 0.0 | 394 ms | 0 |
| 05:15 | 0 | 0.0 | 259 ms | 0 |
| 05:30 | 0 | 0.0 | 476 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 Kilo 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 Kilo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kilo alerts to Slack, Discord or a webhook — free.
Kilo, at kilo.ai, is one of the AI services we monitor. Open source AI coding agent for VS Code, JetBrains, CLI, and Cloud. 500+ models at zero markup, your own keys, or local models for privacy.
Kilo publishes an official status page at status.kilo.ai; 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: 398 ms average, 259–687 ms range across 13 successful checks.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
We have not recorded a public Kilo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
398 ms on average over the last 24 hours (259–687 ms).
Yes, at https://status.kilo.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 Kilo here at once, the problem is on Kilo'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 Kilo. 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.