User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Kilo down?
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
What to try while Kilo is having problems
Estimated fix: Not enough Kilo history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → kilo.ai—
Your browser → us—
Our checksReaching it
Official · ReportsMaintenance · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 30 min ago. Last stored result reached it in 324 ms.
Official status
Maintenance
Service Under Maintenance Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 333 ms | 0 |
| Mon 15 | 0 | 0.0 | 336 ms | 0 |
| Mon 18 | 0 | 0.0 | 549 ms | 0 |
| Mon 20 | 0 | 0.0 | 280 ms | 0 |
| Mon 22 | 0 | 0.0 | 370 ms | 0 |
| Tue 00 | 0 | 0.0 | 273 ms | 0 |
| Tue 02 | 0 | 0.0 | 256 ms | 0 |
| Tue 04 | 0 | 0.0 | 263 ms | 0 |
| Tue 06 | 0 | 0.0 | 268 ms | 0 |
| Tue 08 | 0 | 0.0 | 306 ms | 0 |
| Tue 10 | 0 | 0.0 | 258 ms | 0 |
| Tue 13 | 0 | 0.0 | 411 ms | 0 |
| Tue 15 | 0 | 0.0 | 312 ms | 0 |
| Tue 17 | 0 | 0.0 | 489 ms | 0 |
| Tue 19 | 0 | 0.0 | 292 ms | 0 |
| Tue 22 | 0 | 0.0 | 340 ms | 0 |
| Wed 00 | 0 | 0.0 | 322 ms | 0 |
| Wed 02 | 0 | 0.0 | 406 ms | 0 |
| Wed 04 | 0 | 0.0 | 407 ms | 0 |
| Wed 07 | 0 | 0.0 | 239 ms | 0 |
| Wed 09 | 0 | 0.0 | 385 ms | 0 |
| Wed 11 | 0 | 0.0 | 340 ms | 0 |
| Wed 13 | 0 | 0.0 | 317 ms | 0 |
| Wed 15 | 0 | 0.0 | 342 ms | 0 |
| Wed 17 | 0 | 0.0 | 319 ms | 0 |
| Wed 20 | 0 | 0.0 | 362 ms | 0 |
| Wed 22 | 0 | 0.0 | 301 ms | 0 |
| Thu 00 | 0 | 0.0 | 289 ms | 0 |
| Thu 02 | 0 | 0.0 | 304 ms | 0 |
| Thu 04 | 0 | 0.0 | 311 ms | 0 |
| Thu 06 | 0 | 0.0 | 289 ms | 0 |
| Thu 08 | 0 | 0.0 | 260 ms | 0 |
| Thu 10 | 0 | 0.0 | 386 ms | 0 |
| Thu 12 | 0 | 0.0 | 328 ms | 0 |
| Thu 14 | 0 | 0.0 | 687 ms | 0 |
| Thu 16 | 0 | 0.0 | 408 ms | 0 |
| Thu 19 | 0 | 0.0 | 308 ms | 0 |
| Thu 21 | 0 | 0.0 | 450 ms | 0 |
| Thu 23 | 0 | 0.0 | 311 ms | 0 |
| Fri 01 | 0 | 0.0 | 519 ms | 0 |
| Fri 03 | 0 | 0.0 | 394 ms | 0 |
| Fri 05 | 0 | 0.0 | 368 ms | 0 |
| Fri 07 | 0 | 0.0 | 444 ms | 0 |
| Fri 09 | 0 | 0.0 | 321 ms | 0 |
| Fri 11 | 0 | 0.0 | 581 ms | 0 |
| Fri 13 | 0 | 0.0 | 342 ms | 0 |
| Fri 15 | 0 | 0.0 | 380 ms | 0 |
| Fri 17 | 0 | 0.0 | 324 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live Kilo badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Kilo yet. Outages of 10 minutes or more get their own page here.
Having trouble with Kilo?
One report per service every 10 minutes from this network. No account.
Follow Kilo
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.
About Kilo
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: 385 ms average, 259–581 ms range across 16 successful checks.
Questions
Is Kilo down right now?
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
When was Kilo last down?
We have not recorded a public Kilo incident since monitoring began 8 days ago.
What is Kilo's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Kilo respond?
385 ms on average over the last 24 hours (259–581 ms).
Does Kilo have an official status page?
Yes, at https://status.kilo.ai.
Kilo not working for me but the status is fine. What now?
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.