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 1 hr ago. Last stored result reached it in 908 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 | 1004 ms | 0 |
| Tue 04 | 0 | 0.0 | 709 ms | 0 |
| Tue 06 | 0 | 0.0 | 573 ms | 0 |
| Tue 08 | 0 | 0.0 | 924 ms | 0 |
| Tue 10 | 0 | 0.0 | 862 ms | 0 |
| Tue 13 | 0 | 0.0 | 959 ms | 0 |
| Tue 15 | 0 | 0.0 | 674 ms | 0 |
| Tue 17 | 0 | 0.0 | 717 ms | 0 |
| Tue 19 | 0 | 0.0 | 924 ms | 0 |
| Tue 22 | 0 | 0.0 | 452 ms | 0 |
| Wed 00 | 0 | 0.0 | 859 ms | 0 |
| Wed 02 | 0 | 0.0 | 1003 ms | 0 |
| Wed 04 | 0 | 0.0 | 829 ms | 0 |
| Wed 07 | 0 | 0.0 | 785 ms | 0 |
| Wed 09 | 0 | 0.0 | 840 ms | 0 |
| Wed 11 | 0 | 0.0 | 989 ms | 0 |
| Wed 13 | 0 | 0.0 | 968 ms | 0 |
| Wed 15 | 0 | 0.0 | 799 ms | 0 |
| Wed 17 | 0 | 0.0 | 791 ms | 0 |
| Wed 20 | 0 | 0.0 | 262 ms | 0 |
| Wed 22 | 0 | 0.0 | 759 ms | 0 |
| Thu 00 | 0 | 0.0 | 608 ms | 0 |
| Thu 02 | 0 | 0.0 | 1190 ms | 0 |
| Thu 04 | 0 | 0.0 | 398 ms | 0 |
| Thu 06 | 0 | 0.0 | 759 ms | 0 |
| Thu 08 | 0 | 0.0 | 589 ms | 0 |
| Thu 10 | 0 | 0.0 | 861 ms | 0 |
| Thu 12 | 0 | 0.0 | 898 ms | 0 |
| Thu 15 | 0 | 0.0 | 408 ms | 0 |
| Thu 17 | 0 | 0.0 | 902 ms | 0 |
| Thu 19 | 0 | 0.0 | 832 ms | 0 |
| Thu 21 | 0 | 0.0 | 730 ms | 0 |
| Thu 23 | 0 | 0.0 | 746 ms | 0 |
| Fri 01 | 0 | 0.0 | 1002 ms | 0 |
| Fri 03 | 0 | 0.0 | 1045 ms | 0 |
| Fri 05 | 0 | 0.0 | 252 ms | 0 |
| Fri 07 | 0 | 0.0 | 860 ms | 0 |
| Fri 09 | 0 | 0.0 | 672 ms | 0 |
| Fri 10 | 0 | 0.0 | 823 ms | 0 |
| Fri 12 | 0 | 0.0 | 873 ms | 0 |
| Fri 14 | 0 | 0.0 | 666 ms | 0 |
| Fri 16 | 0 | 0.0 | 718 ms | 0 |
| Fri 18 | 0 | 0.0 | 891 ms | 0 |
| Fri 20 | 0 | 0.0 | 602 ms | 0 |
| Fri 22 | 0 | 0.0 | 913 ms | 0 |
| Sat 00 | 0 | 0.0 | 726 ms | 0 |
| Sat 02 | 0 | 0.0 | 666 ms | 0 |
| Sat 04 | 0 | 0.0 | 760 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 Kabeen 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 Kabeen goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kabeen alerts to Slack, Discord or a webhook — free.
We track Kabeen (kabeen.io) as part of the AI group. Kabeen unifies application mapping, automated discovery, usage analytics and IT dashboards in a living context for IT teams and AI agents.
Kabeen publishes an official status page at status.kabeen.io; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 750 ms average, 187–1017 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 Kabeen incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
750 ms on average over the last 24 hours (187–1017 ms).
Yes, at https://status.kabeen.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 Kabeen here at once, the problem is on Kabeen'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 Kabeen. 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.