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 2 hr ago. Last stored result reached it in 1090 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 08 | 0 | 0.0 | 651 ms | 0 |
| Tue 10 | 0 | 0.0 | 794 ms | 0 |
| Tue 12 | 0 | 0.0 | 718 ms | 0 |
| Tue 14 | 0 | 0.0 | 594 ms | 0 |
| Tue 16 | 0 | 0.0 | — | 1 |
| Tue 18 | 0 | 0.0 | 1028 ms | 0 |
| Tue 21 | 0 | 0.0 | 1609 ms | 0 |
| Tue 23 | 0 | 0.0 | 1283 ms | 0 |
| Wed 01 | 0 | 0.0 | 1603 ms | 0 |
| Wed 03 | 0 | 0.0 | 1042 ms | 0 |
| Wed 06 | 0 | 0.0 | 1979 ms | 0 |
| Wed 08 | 0 | 0.0 | 1549 ms | 0 |
| Wed 10 | 0 | 0.0 | 1482 ms | 0 |
| Wed 12 | 0 | 0.0 | 1334 ms | 0 |
| Wed 14 | 0 | 0.0 | 1695 ms | 0 |
| Wed 16 | 0 | 0.0 | 1258 ms | 0 |
| Wed 19 | 0 | 0.0 | 1364 ms | 0 |
| Wed 21 | 0 | 0.0 | 1333 ms | 0 |
| Wed 23 | 0 | 0.0 | 1507 ms | 0 |
| Thu 01 | 0 | 0.0 | 1392 ms | 0 |
| Thu 03 | 0 | 0.0 | 1968 ms | 0 |
| Thu 05 | 0 | 0.0 | 1302 ms | 0 |
| Thu 07 | 0 | 0.0 | 1151 ms | 0 |
| Thu 09 | 0 | 0.0 | 1714 ms | 0 |
| Thu 11 | 0 | 0.0 | 1148 ms | 0 |
| Thu 14 | 0 | 0.0 | 1223 ms | 0 |
| Thu 16 | 0 | 0.0 | 1565 ms | 0 |
| Thu 18 | 0 | 0.0 | 994 ms | 0 |
| Thu 20 | 0 | 0.0 | 1175 ms | 0 |
| Thu 22 | 0 | 0.0 | 1134 ms | 0 |
| Fri 00 | 0 | 0.0 | 1078 ms | 0 |
| Fri 02 | 0 | 0.0 | 1418 ms | 0 |
| Fri 04 | 0 | 0.0 | 1134 ms | 0 |
| Fri 06 | 0 | 0.0 | 987 ms | 0 |
| Fri 08 | 0 | 0.0 | 1151 ms | 0 |
| Fri 10 | 0 | 0.0 | 990 ms | 0 |
| Fri 11 | 0 | 0.0 | 808 ms | 0 |
| Fri 13 | 0 | 0.0 | 1506 ms | 0 |
| Fri 15 | 0 | 0.0 | 1552 ms | 0 |
| Fri 17 | 0 | 0.0 | 972 ms | 0 |
| Fri 19 | 0 | 0.0 | 1214 ms | 0 |
| Fri 20 | 0 | 0.0 | 1454 ms | 0 |
| Fri 22 | 0 | 0.0 | 984 ms | 0 |
| Sat 00 | 0 | 0.0 | 1424 ms | 0 |
| Sat 01 | 0 | 0.0 | 1307 ms | 0 |
| Sat 03 | 0 | 0.0 | 1332 ms | 0 |
| Sat 05 | 0 | 0.0 | 1198 ms | 0 |
| Sat 07 | 0 | 0.0 | 1090 ms | 0 |
98.72% 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 Just-Wiped 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 Just-Wiped goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Just-Wiped alerts to Slack, Discord or a webhook — free.
We track Just-Wiped (just-wiped.net) as part of the Gaming group. Quickly find fresh wipes and keep track of your favorite Rust servers.
Just-Wiped publishes an official status page at status.just-wiped.net; 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: 98.72% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1216 ms average, 808–1552 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 Just-Wiped incident since monitoring began 8 days ago.
From our own checks: 98.72% over 8 days of checks.
1216 ms on average over the last 24 hours (808–1552 ms).
Yes, at https://status.just-wiped.net.
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 Just-Wiped here at once, the problem is on Just-Wiped'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 Just-Wiped. 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.