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 38 min ago. Last stored result reached it in 416 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 408 ms | 0 |
| Tue 00 | 0 | 0.0 | 236 ms | 0 |
| Tue 02 | 0 | 0.0 | 309 ms | 0 |
| Tue 04 | 0 | 0.0 | 136 ms | 0 |
| Tue 06 | 0 | 0.0 | 409 ms | 0 |
| Tue 08 | 0 | 0.0 | 386 ms | 0 |
| Tue 10 | 0 | 0.0 | 409 ms | 0 |
| Tue 13 | 0 | 0.0 | 150 ms | 0 |
| Tue 15 | 0 | 0.0 | 328 ms | 0 |
| Tue 17 | 0 | 0.0 | 238 ms | 0 |
| Tue 19 | 0 | 0.0 | 240 ms | 0 |
| Tue 22 | 0 | 0.0 | 248 ms | 0 |
| Wed 00 | 0 | 0.0 | 657 ms | 0 |
| Wed 02 | 0 | 0.0 | 438 ms | 0 |
| Wed 04 | 0 | 0.0 | 233 ms | 0 |
| Wed 07 | 0 | 0.0 | 279 ms | 0 |
| Wed 09 | 0 | 0.0 | 229 ms | 0 |
| Wed 11 | 0 | 0.0 | 244 ms | 0 |
| Wed 13 | 0 | 0.0 | 199 ms | 0 |
| Wed 15 | 0 | 0.0 | 257 ms | 0 |
| Wed 17 | 0 | 0.0 | 148 ms | 0 |
| Wed 19 | 0 | 0.0 | 211 ms | 0 |
| Wed 21 | 0 | 0.0 | 429 ms | 0 |
| Thu 00 | 0 | 0.0 | 458 ms | 0 |
| Thu 02 | 0 | 0.0 | 215 ms | 0 |
| Thu 04 | 0 | 0.0 | 415 ms | 0 |
| Thu 06 | 0 | 0.0 | 451 ms | 0 |
| Thu 08 | 0 | 0.0 | 403 ms | 0 |
| Thu 10 | 0 | 0.0 | 509 ms | 0 |
| Thu 12 | 0 | 0.0 | 143 ms | 0 |
| Thu 14 | 0 | 0.0 | 224 ms | 0 |
| Thu 16 | 0 | 0.0 | 420 ms | 0 |
| Thu 18 | 0 | 0.0 | 111 ms | 0 |
| Thu 20 | 0 | 0.0 | 232 ms | 0 |
| Thu 22 | 0 | 0.0 | 296 ms | 0 |
| Thu 23 | 0 | 0.0 | 254 ms | 0 |
| Fri 01 | 0 | 0.0 | 239 ms | 0 |
| Fri 03 | 0 | 0.0 | 134 ms | 0 |
| Fri 05 | 0 | 0.0 | 200 ms | 0 |
| Fri 06 | 0 | 0.0 | 194 ms | 0 |
| Fri 08 | 0 | 0.0 | 575 ms | 0 |
| Fri 10 | 0 | 0.0 | 394 ms | 0 |
| Fri 11 | 0 | 0.0 | 206 ms | 0 |
| Fri 13 | 0 | 0.0 | 393 ms | 0 |
| Fri 15 | 0 | 0.0 | 195 ms | 0 |
| Fri 17 | 0 | 0.0 | 107 ms | 0 |
| Fri 19 | 0 | 0.0 | 470 ms | 0 |
| Fri 21 | 0 | 0.0 | 416 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 Kleep 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 Kleep goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Kleep alerts to Slack, Discord or a webhook — free.
Kleep is listed in our AI category and checked at kleep.ai. Search, sizing, virtual try-on, recommendations and merchandising from one AI model that understands fashion. 300+ brands boost conversion and cut returns with Kleep.
Kleep publishes an official status page at status.kleep.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 303 ms average, 107–575 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 Kleep incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
303 ms on average over the last 24 hours (107–575 ms).
Yes, at https://status.kleep.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 Kleep here at once, the problem is on Kleep'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 Kleep. 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.