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 49 min ago. Last stored result reached it in 611 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 621 ms | 0 |
| Tue 02 | 0 | 0.0 | 589 ms | 0 |
| Tue 04 | 0 | 0.0 | 597 ms | 0 |
| Tue 06 | 0 | 0.0 | 558 ms | 0 |
| Tue 08 | 0 | 0.0 | 674 ms | 0 |
| Tue 10 | 0 | 0.0 | 655 ms | 0 |
| Tue 12 | 0 | 0.0 | 591 ms | 0 |
| Tue 15 | 0 | 0.0 | 627 ms | 0 |
| Tue 17 | 0 | 0.0 | 673 ms | 0 |
| Tue 19 | 0 | 0.0 | 714 ms | 0 |
| Tue 21 | 0 | 0.0 | 671 ms | 0 |
| Tue 22 | 0 | 0.0 | 606 ms | 0 |
| Wed 00 | 0 | 0.0 | 623 ms | 0 |
| Wed 02 | 0 | 0.0 | 624 ms | 0 |
| Wed 04 | 0 | 0.0 | 611 ms | 0 |
| Wed 06 | 0 | 0.0 | 513 ms | 0 |
| Wed 09 | 0 | 0.0 | 460 ms | 0 |
| Wed 11 | 0 | 0.0 | 654 ms | 0 |
| Wed 13 | 0 | 0.0 | 661 ms | 0 |
| Wed 15 | 0 | 0.0 | 632 ms | 0 |
| Wed 17 | 0 | 0.0 | 583 ms | 0 |
| Wed 20 | 0 | 0.0 | 610 ms | 0 |
| Wed 22 | 0 | 0.0 | 599 ms | 0 |
| Thu 00 | 0 | 0.0 | 612 ms | 0 |
| Thu 02 | 0 | 0.0 | 581 ms | 0 |
| Thu 04 | 0 | 0.0 | 613 ms | 0 |
| Thu 06 | 0 | 0.0 | 591 ms | 0 |
| Thu 08 | 0 | 0.0 | 650 ms | 0 |
| Thu 10 | 0 | 0.0 | 590 ms | 0 |
| Thu 12 | 0 | 0.0 | 544 ms | 0 |
| Thu 14 | 0 | 0.0 | 590 ms | 0 |
| Thu 16 | 0 | 0.0 | 608 ms | 0 |
| Thu 19 | 0 | 0.0 | 636 ms | 0 |
| Thu 21 | 0 | 0.0 | 629 ms | 0 |
| Thu 23 | 0 | 0.0 | 572 ms | 0 |
| Fri 01 | 0 | 0.0 | 561 ms | 0 |
| Fri 03 | 0 | 0.0 | 521 ms | 0 |
| Fri 05 | 0 | 0.0 | 630 ms | 0 |
| Fri 07 | 0 | 0.0 | 584 ms | 0 |
| Fri 09 | 0 | 0.0 | 564 ms | 0 |
| Fri 10 | 0 | 0.0 | 551 ms | 0 |
| Fri 12 | 0 | 0.0 | 626 ms | 0 |
| Fri 14 | 0 | 0.0 | 622 ms | 0 |
| Fri 16 | 0 | 0.0 | 611 ms | 0 |
| Fri 18 | 0 | 0.0 | 622 ms | 0 |
| Fri 20 | 0 | 0.0 | 642 ms | 0 |
| Fri 21 | 0 | 0.0 | 522 ms | 0 |
| Fri 22 | 0 | 0.0 | 611 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 Keito 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 Keito goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Keito alerts to Slack, Discord or a webhook — free.
Keito is listed in our AI category and checked at keito.ai. Track time from people and AI agents, approve expenses and invoice clients with Keito. Built for consultancies, agencies and professional-services teams.
Keito publishes an official status page at status.keito.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 585 ms average, 506–678 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Keito incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
585 ms on average over the last 24 hours (506–678 ms).
Yes, at https://status.keito.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 Keito here at once, the problem is on Keito'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 Keito. 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.