User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 39 min ago. Last stored result reached it in 185 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 67 ms | 0 |
| Tue 01 | 0 | 0.0 | 70 ms | 0 |
| Tue 03 | 0 | 0.0 | 34 ms | 0 |
| Tue 05 | 0 | 0.0 | 106 ms | 0 |
| Tue 07 | 0 | 0.0 | 47 ms | 0 |
| Tue 09 | 0 | 0.0 | 26 ms | 0 |
| Tue 12 | 0 | 0.0 | 45 ms | 0 |
| Tue 14 | 0 | 0.0 | 125 ms | 0 |
| Tue 16 | 0 | 0.0 | 48 ms | 0 |
| Tue 18 | 0 | 0.0 | 41 ms | 0 |
| Tue 21 | 0 | 0.0 | 64 ms | 0 |
| Tue 23 | 0 | 0.0 | 28 ms | 0 |
| Wed 01 | 0 | 0.0 | 37 ms | 0 |
| Wed 03 | 0 | 0.0 | 34 ms | 0 |
| Wed 06 | 0 | 0.0 | 107 ms | 0 |
| Wed 08 | 0 | 0.0 | 53 ms | 0 |
| Wed 10 | 0 | 0.0 | 74 ms | 0 |
| Wed 12 | 0 | 0.0 | 89 ms | 0 |
| Wed 14 | 0 | 0.0 | 218 ms | 0 |
| Wed 16 | 0 | 0.0 | 100 ms | 0 |
| Wed 19 | 0 | 0.0 | 74 ms | 0 |
| Wed 21 | 0 | 0.0 | 62 ms | 0 |
| Wed 23 | 0 | 0.0 | 41 ms | 0 |
| Thu 01 | 0 | 0.0 | 89 ms | 0 |
| Thu 03 | 0 | 0.0 | 73 ms | 0 |
| Thu 05 | 0 | 0.0 | 61 ms | 0 |
| Thu 07 | 0 | 0.0 | 80 ms | 0 |
| Thu 09 | 0 | 0.0 | 78 ms | 0 |
| Thu 11 | 0 | 0.0 | 114 ms | 0 |
| Thu 14 | 0 | 0.0 | 92 ms | 0 |
| Thu 16 | 0 | 0.0 | 223 ms | 0 |
| Thu 18 | 0 | 0.0 | 25 ms | 0 |
| Thu 20 | 0 | 0.0 | 110 ms | 0 |
| Thu 22 | 0 | 0.0 | 42 ms | 0 |
| Fri 00 | 0 | 0.0 | 43 ms | 0 |
| Fri 02 | 0 | 0.0 | 77 ms | 0 |
| Fri 04 | 0 | 0.0 | 103 ms | 0 |
| Fri 06 | 0 | 0.0 | 73 ms | 0 |
| Fri 07 | 0 | 0.0 | 48 ms | 0 |
| Fri 09 | 0 | 0.0 | 72 ms | 0 |
| Fri 10 | 0 | 0.0 | 52 ms | 0 |
| Fri 12 | 0 | 0.0 | 56 ms | 0 |
| Fri 14 | 0 | 0.0 | 70 ms | 0 |
| Fri 16 | 0 | 0.0 | 64 ms | 0 |
| Fri 17 | 0 | 0.0 | 35 ms | 0 |
| Fri 18 | 0 | 0.0 | 77 ms | 0 |
| Fri 20 | 0 | 0.0 | 127 ms | 0 |
| Fri 22 | 0 | 0.0 | 185 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 Klue 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 Klue goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Klue alerts to Slack, Discord or a webhook — free.
Klue is listed in our Cloud & developer category and checked at klue.com. Combine your research, build better battlecards, and fix weaknesses that your buyers care about. Make it easy to pick you instead of your competitors.
Klue publishes an official status page at kluestatus.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 82 ms average, 35–185 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 Klue incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
82 ms on average over the last 24 hours (35–185 ms).
Yes, at https://kluestatus.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Klue here at once, the problem is on Klue'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 Klue. 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.