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 1 hr ago. Last stored result reached it in 401 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 10 | 0 | 0.0 | 29 ms | 0 |
| Tue 12 | 0 | 0.0 | 121 ms | 0 |
| Tue 14 | 0 | 0.0 | 49 ms | 0 |
| Tue 16 | 0 | 0.0 | 425 ms | 0 |
| Tue 19 | 0 | 0.0 | 121 ms | 0 |
| Tue 21 | 0 | 0.0 | 141 ms | 0 |
| Tue 23 | 0 | 0.0 | 120 ms | 0 |
| Wed 01 | 0 | 0.0 | 384 ms | 0 |
| Wed 04 | 0 | 0.0 | 258 ms | 0 |
| Wed 06 | 0 | 0.0 | 635 ms | 0 |
| Wed 08 | 0 | 0.0 | 197 ms | 0 |
| Wed 10 | 0 | 0.0 | 398 ms | 0 |
| Wed 12 | 0 | 0.0 | 112 ms | 0 |
| Wed 13 | 0 | 0.0 | 407 ms | 0 |
| Wed 15 | 0 | 0.0 | 400 ms | 0 |
| Wed 17 | 0 | 0.0 | 461 ms | 0 |
| Wed 19 | 0 | 0.0 | 294 ms | 0 |
| Wed 21 | 0 | 0.0 | 594 ms | 0 |
| Wed 23 | 0 | 0.0 | 462 ms | 0 |
| Thu 01 | 0 | 0.0 | 188 ms | 0 |
| Thu 03 | 0 | 0.0 | 478 ms | 0 |
| Thu 05 | 0 | 0.0 | 109 ms | 0 |
| Thu 08 | 0 | 0.0 | 259 ms | 0 |
| Thu 10 | 0 | 0.0 | 120 ms | 0 |
| Thu 12 | 0 | 0.0 | 334 ms | 0 |
| Thu 14 | 0 | 0.0 | 521 ms | 0 |
| Thu 16 | 0 | 0.0 | 268 ms | 0 |
| Thu 18 | 0 | 0.0 | 612 ms | 0 |
| Thu 20 | 0 | 0.0 | 52 ms | 0 |
| Thu 22 | 0 | 0.0 | 275 ms | 0 |
| Fri 00 | 0 | 0.0 | 97 ms | 0 |
| Fri 02 | 0 | 0.0 | 48 ms | 0 |
| Fri 03 | 0 | 0.0 | 103 ms | 0 |
| Fri 06 | 0 | 0.0 | 214 ms | 0 |
| Fri 08 | 0 | 0.0 | 269 ms | 0 |
| Fri 10 | 0 | 0.0 | 37 ms | 0 |
| Fri 11 | 0 | 0.0 | 279 ms | 0 |
| Fri 12 | 0 | 0.0 | 398 ms | 0 |
| Fri 14 | 0 | 0.0 | 48 ms | 0 |
| Fri 16 | 0 | 0.0 | 213 ms | 0 |
| Fri 17 | 0 | 0.0 | 146 ms | 0 |
| Fri 19 | 0 | 0.0 | 362 ms | 0 |
| Fri 20 | 0 | 0.0 | 96 ms | 0 |
| Fri 21 | 0 | 0.0 | 626 ms | 0 |
| Fri 23 | 0 | 0.0 | 51 ms | 0 |
| Sat 00 | 0 | 0.0 | 283 ms | 0 |
| Sat 03 | 0 | 0.0 | 335 ms | 0 |
| Sat 05 | 0 | 0.0 | 401 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Nodecraft 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 Nodecraft goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nodecraft alerts to Slack, Discord or a webhook — free.
Nodecraft, at nodecraft.com, is one of the Gaming services we monitor. Deploy a high-performance game server in seconds with Nodecraft. Enjoy low latency, DDoS protection, and the ability to swap between 68+ games instantly. Start your free trial!
Nodecraft publishes an official status page at status.nodecraft.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 249 ms average, 28–626 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 Nodecraft incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
249 ms on average over the last 24 hours (28–626 ms).
Yes, at https://status.nodecraft.com.
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 Nodecraft here at once, the problem is on Nodecraft'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 Nodecraft. 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.