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 12 min ago. Last stored result reached it in 180 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 284 ms | 0 |
| Nov 7 | 0 | 0.0 | 402 ms | 0 |
| Nov 7 | 0 | 0.0 | 248 ms | 0 |
| Nov 7 | 0 | 0.0 | 352 ms | 0 |
| Nov 7 | 0 | 0.0 | 296 ms | 0 |
| Nov 8 | 0 | 0.0 | 265 ms | 0 |
| Nov 8 | 0 | 0.0 | 290 ms | 0 |
| Nov 8 | 0 | 0.0 | 323 ms | 0 |
| Nov 8 | 0 | 0.0 | 304 ms | 0 |
| Nov 9 | 0 | 0.0 | 328 ms | 0 |
| Nov 9 | 0 | 0.0 | 293 ms | 0 |
| Nov 9 | 0 | 0.0 | 458 ms | 0 |
| Nov 9 | 0 | 0.0 | 230 ms | 0 |
| Nov 10 | 0 | 0.0 | 225 ms | 0 |
| Nov 10 | 0 | 0.0 | 177 ms | 0 |
| Nov 10 | 0 | 0.0 | 213 ms | 0 |
| Nov 10 | 0 | 0.0 | 253 ms | 0 |
| Nov 11 | 0 | 0.0 | 154 ms | 0 |
| Nov 11 | 0 | 0.0 | 147 ms | 0 |
| Nov 11 | 0 | 0.0 | 236 ms | 0 |
| Nov 11 | 0 | 0.0 | 175 ms | 0 |
| Nov 12 | 0 | 0.0 | 214 ms | 0 |
| Nov 12 | 0 | 0.0 | 183 ms | 0 |
| Nov 12 | 0 | 0.0 | 240 ms | 0 |
| Nov 12 | 0 | 0.0 | 245 ms | 0 |
| Nov 13 | 0 | 0.0 | 211 ms | 0 |
| Nov 13 | 0 | 0.0 | 202 ms | 0 |
| Nov 13 | 0 | 0.0 | 184 ms | 0 |
| Nov 13 | 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Keygen 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 Keygen goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Keygen alerts to Slack, Discord or a webhook — free.
Keygen, at keygen.sh, is one of the Cloud & developer services we monitor. Keygen is a powerful software licensing API for desktop apps, on-premise software and other software products written in Go, Rust, JS, C/C++, C#, Swift, Java, Kotlin and more.
Keygen publishes an official status page at status.keygen.sh; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 203 ms average, 140–314 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 Keygen incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
203 ms on average over the last 24 hours (140–314 ms).
Yes, at https://status.keygen.sh.
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 Keygen here at once, the problem is on Keygen'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 Keygen. 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.