User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 18 min ago. Last stored result reached it in 596 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 | 190 ms | 0 |
| Tue 04 | 0 | 0.0 | 31 ms | 0 |
| Tue 06 | 0 | 0.0 | 95 ms | 0 |
| Tue 08 | 0 | 0.0 | 45 ms | 0 |
| Tue 10 | 0 | 0.0 | 695 ms | 0 |
| Tue 12 | 0 | 0.0 | 163 ms | 0 |
| Tue 15 | 0 | 0.0 | 213 ms | 0 |
| Tue 17 | 0 | 0.0 | 36 ms | 0 |
| Tue 19 | 0 | 0.0 | 148 ms | 0 |
| Tue 22 | 0 | 0.0 | 68 ms | 0 |
| Wed 00 | 0 | 0.0 | 545 ms | 0 |
| Wed 02 | 0 | 0.0 | 261 ms | 0 |
| Wed 04 | 0 | 0.0 | 53 ms | 0 |
| Wed 06 | 0 | 0.0 | 533 ms | 0 |
| Wed 09 | 0 | 0.0 | 27 ms | 0 |
| Wed 11 | 0 | 0.0 | 549 ms | 0 |
| Wed 13 | 0 | 0.0 | 36 ms | 0 |
| Wed 15 | 0 | 0.0 | 34 ms | 0 |
| Wed 17 | 0 | 0.0 | 28 ms | 0 |
| Wed 20 | 0 | 0.0 | 152 ms | 0 |
| Wed 22 | 0 | 0.0 | 44 ms | 0 |
| Thu 00 | 0 | 0.0 | 45 ms | 0 |
| Thu 02 | 0 | 0.0 | 883 ms | 0 |
| Thu 04 | 0 | 0.0 | 201 ms | 0 |
| Thu 06 | 0 | 0.0 | 179 ms | 0 |
| Thu 08 | 0 | 0.0 | 166 ms | 0 |
| Thu 10 | 0 | 0.0 | 28 ms | 0 |
| Thu 12 | 0 | 0.0 | 168 ms | 0 |
| Thu 14 | 0 | 0.0 | 52 ms | 0 |
| Thu 16 | 0 | 0.0 | 124 ms | 0 |
| Thu 19 | 0 | 0.0 | 32 ms | 0 |
| Thu 21 | 0 | 0.0 | 20 ms | 0 |
| Thu 23 | 0 | 0.0 | 732 ms | 0 |
| Fri 01 | 0 | 0.0 | 101 ms | 0 |
| Fri 03 | 0 | 0.0 | 692 ms | 0 |
| Fri 06 | 0 | 0.0 | 650 ms | 0 |
| Fri 08 | 0 | 0.0 | 706 ms | 0 |
| Fri 10 | 0 | 0.0 | 578 ms | 0 |
| Fri 11 | 0 | 0.0 | 41 ms | 0 |
| Fri 12 | 0 | 0.0 | 613 ms | 0 |
| Fri 14 | 0 | 0.0 | 20 ms | 0 |
| Fri 16 | 0 | 0.0 | 199 ms | 0 |
| Fri 18 | 0 | 0.0 | 104 ms | 0 |
| Fri 19 | 0 | 0.0 | 137 ms | 0 |
| Fri 20 | 0 | 0.0 | 36 ms | 0 |
| Fri 21 | 0 | 0.0 | 32 ms | 0 |
| Fri 23 | 0 | 0.0 | 596 ms | 0 |
| Sat 00 | 0 | 0.0 | 31 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 NoRisk Client 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 NoRisk Client goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NoRisk Client alerts to Slack, Discord or a webhook — free.
NoRisk Client is listed in our Gaming category and checked at norisk.gg. Free Minecraft launcher and client for Windows, macOS and Linux. Mods in one click, 1.8.9 to the latest release, cosmetics, a HUD editor and hosted worlds.
NoRisk Client publishes an official status page at status.norisk.gg; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 290 ms average, 20–706 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 NoRisk Client incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
290 ms on average over the last 24 hours (20–706 ms).
Yes, at https://status.norisk.gg.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report NoRisk Client here at once, the problem is on NoRisk Client'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 NoRisk Client. 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.