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 21 min ago. Last stored result reached it in 1179 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 506 ms | 0 |
| Tue 04 | 0 | 0.0 | 134 ms | 0 |
| Tue 06 | 0 | 0.0 | 317 ms | 0 |
| Tue 08 | 0 | 0.0 | 882 ms | 0 |
| Tue 10 | 0 | 0.0 | 250 ms | 0 |
| Tue 13 | 0 | 0.0 | 141 ms | 0 |
| Tue 15 | 0 | 0.0 | 401 ms | 0 |
| Tue 17 | 0 | 0.0 | 260 ms | 0 |
| Tue 19 | 0 | 0.0 | 352 ms | 0 |
| Tue 22 | 0 | 0.0 | 317 ms | 0 |
| Wed 00 | 0 | 0.0 | 339 ms | 0 |
| Wed 02 | 0 | 0.0 | 221 ms | 0 |
| Wed 04 | 0 | 0.0 | 313 ms | 0 |
| Wed 07 | 0 | 0.0 | 245 ms | 0 |
| Wed 09 | 0 | 0.0 | 280 ms | 0 |
| Wed 11 | 0 | 0.0 | 141 ms | 0 |
| Wed 13 | 0 | 0.0 | 355 ms | 0 |
| Wed 15 | 0 | 0.0 | 223 ms | 0 |
| Wed 17 | 0 | 0.0 | 473 ms | 0 |
| Wed 20 | 0 | 0.0 | 86 ms | 0 |
| Wed 22 | 0 | 0.0 | 297 ms | 0 |
| Thu 00 | 0 | 0.0 | 330 ms | 0 |
| Thu 02 | 0 | 0.0 | 313 ms | 0 |
| Thu 04 | 0 | 0.0 | 118 ms | 0 |
| Thu 06 | 0 | 0.0 | 298 ms | 0 |
| Thu 08 | 0 | 0.0 | 362 ms | 0 |
| Thu 10 | 0 | 0.0 | 304 ms | 0 |
| Thu 12 | 0 | 0.0 | 135 ms | 0 |
| Thu 15 | 0 | 0.0 | 147 ms | 0 |
| Thu 17 | 0 | 0.0 | 276 ms | 0 |
| Thu 19 | 0 | 0.0 | 107 ms | 0 |
| Thu 21 | 0 | 0.0 | 404 ms | 0 |
| Thu 23 | 0 | 0.0 | 118 ms | 0 |
| Fri 01 | 0 | 0.0 | 321 ms | 0 |
| Fri 03 | 0 | 0.0 | 327 ms | 0 |
| Fri 05 | 0 | 0.0 | 108 ms | 0 |
| Fri 07 | 0 | 0.0 | 403 ms | 0 |
| Fri 09 | 0 | 0.0 | 260 ms | 0 |
| Fri 10 | 0 | 0.0 | 213 ms | 0 |
| Fri 11 | 0 | 0.0 | 366 ms | 0 |
| Fri 12 | 0 | 0.0 | 374 ms | 0 |
| Fri 14 | 0 | 0.0 | 450 ms | 0 |
| Fri 15 | 0 | 0.0 | 285 ms | 0 |
| Fri 17 | 0 | 0.0 | 349 ms | 0 |
| Fri 19 | 0 | 0.0 | 290 ms | 0 |
| Fri 20 | 0 | 0.0 | 137 ms | 0 |
| Fri 22 | 0 | 0.0 | 1179 ms | 0 |
| Fri 23 | 0 | 0.0 | 298 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Kylon 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 Kylon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kylon alerts to Slack, Discord or a webhook — free.
Kylon is listed in our AI category and checked at kylon.io. Kylon by Pure Reason is a company harness: AI agents join your team as members, with their own memory and permissions, and execute real work.
Kylon publishes an official status page at status.kylon.io; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 357 ms average, 108–1179 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Kylon incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
357 ms on average over the last 24 hours (108–1179 ms).
Yes, at https://status.kylon.io.
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 Kylon here at once, the problem is on Kylon'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 Kylon. 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.