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 44 min ago. Last stored result reached it in 314 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 230 ms | 0 |
| Mon 20 | 0 | 0.0 | 387 ms | 0 |
| Mon 22 | 0 | 0.0 | 191 ms | 0 |
| Tue 00 | 0 | 0.0 | 225 ms | 0 |
| Tue 02 | 0 | 0.0 | 168 ms | 0 |
| Tue 04 | 0 | 0.0 | 286 ms | 0 |
| Tue 06 | 0 | 0.0 | 177 ms | 0 |
| Tue 08 | 0 | 0.0 | 206 ms | 0 |
| Tue 10 | 0 | 0.0 | 110 ms | 0 |
| Tue 13 | 0 | 0.0 | 208 ms | 0 |
| Tue 15 | 0 | 0.0 | 271 ms | 0 |
| Tue 17 | 0 | 0.0 | 188 ms | 0 |
| Tue 19 | 0 | 0.0 | 205 ms | 0 |
| Tue 22 | 0 | 0.0 | 271 ms | 0 |
| Wed 00 | 0 | 0.0 | 209 ms | 0 |
| Wed 02 | 0 | 0.0 | 153 ms | 0 |
| Wed 04 | 0 | 0.0 | 130 ms | 0 |
| Wed 07 | 0 | 0.0 | 205 ms | 0 |
| Wed 09 | 0 | 0.0 | 147 ms | 0 |
| Wed 11 | 0 | 0.0 | 122 ms | 0 |
| Wed 13 | 0 | 0.0 | 264 ms | 0 |
| Wed 15 | 0 | 0.0 | 236 ms | 0 |
| Wed 17 | 0 | 0.0 | 197 ms | 0 |
| Wed 20 | 0 | 0.0 | 226 ms | 0 |
| Wed 22 | 0 | 0.0 | 123 ms | 0 |
| Thu 00 | 0 | 0.0 | 197 ms | 0 |
| Thu 02 | 0 | 0.0 | 209 ms | 0 |
| Thu 04 | 0 | 0.0 | 262 ms | 0 |
| Thu 06 | 0 | 0.0 | 344 ms | 0 |
| Thu 08 | 0 | 0.0 | 138 ms | 0 |
| Thu 10 | 0 | 0.0 | 183 ms | 0 |
| Thu 12 | 0 | 0.0 | 163 ms | 0 |
| Thu 15 | 0 | 0.0 | 240 ms | 0 |
| Thu 17 | 0 | 0.0 | 269 ms | 0 |
| Thu 19 | 0 | 0.0 | 324 ms | 0 |
| Thu 21 | 0 | 0.0 | 245 ms | 0 |
| Thu 23 | 0 | 0.0 | 170 ms | 0 |
| Fri 01 | 0 | 0.0 | 219 ms | 0 |
| Fri 03 | 0 | 0.0 | 211 ms | 0 |
| Fri 05 | 0 | 0.0 | 199 ms | 0 |
| Fri 07 | 0 | 0.0 | 202 ms | 0 |
| Fri 09 | 0 | 0.0 | 211 ms | 0 |
| Fri 11 | 0 | 0.0 | 140 ms | 0 |
| Fri 12 | 0 | 0.0 | 164 ms | 0 |
| Fri 14 | 0 | 0.0 | 163 ms | 0 |
| Fri 15 | 0 | 0.0 | 232 ms | 0 |
| Fri 17 | 0 | 0.0 | 204 ms | 0 |
| Fri 18 | 0 | 0.0 | 314 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: 214 ms average, 140–324 ms range across 14 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.
214 ms on average over the last 24 hours (140–324 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.