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 375 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 458 ms | 0 |
| Mon 23 | 0 | 0.0 | 385 ms | 0 |
| Tue 01 | 0 | 0.0 | 372 ms | 0 |
| Tue 03 | 0 | 0.0 | 459 ms | 0 |
| Tue 05 | 0 | 0.0 | 396 ms | 0 |
| Tue 08 | 0 | 0.0 | 420 ms | 0 |
| Tue 10 | 0 | 0.0 | 398 ms | 0 |
| Tue 12 | 0 | 0.0 | 345 ms | 0 |
| Tue 14 | 0 | 0.0 | 400 ms | 0 |
| Tue 16 | 0 | 0.0 | 368 ms | 0 |
| Tue 18 | 0 | 0.0 | 444 ms | 0 |
| Tue 21 | 0 | 0.0 | 329 ms | 0 |
| Tue 23 | 0 | 0.0 | 433 ms | 0 |
| Wed 01 | 0 | 0.0 | 364 ms | 0 |
| Wed 03 | 0 | 0.0 | 300 ms | 0 |
| Wed 06 | 0 | 0.0 | 432 ms | 0 |
| Wed 08 | 0 | 0.0 | 432 ms | 0 |
| Wed 10 | 0 | 0.0 | 417 ms | 0 |
| Wed 12 | 0 | 0.0 | 124 ms | 0 |
| Wed 14 | 0 | 0.0 | 396 ms | 0 |
| Wed 16 | 0 | 0.0 | 476 ms | 0 |
| Wed 19 | 0 | 0.0 | 246 ms | 0 |
| Wed 21 | 0 | 0.0 | 454 ms | 0 |
| Wed 23 | 0 | 0.0 | 411 ms | 0 |
| Thu 01 | 0 | 0.0 | 403 ms | 0 |
| Thu 03 | 0 | 0.0 | 420 ms | 0 |
| Thu 05 | 0 | 0.0 | 382 ms | 0 |
| Thu 07 | 0 | 0.0 | 247 ms | 0 |
| Thu 10 | 0 | 0.0 | 377 ms | 0 |
| Thu 12 | 0 | 0.0 | 260 ms | 0 |
| Thu 14 | 0 | 0.0 | 138 ms | 0 |
| Thu 16 | 0 | 0.0 | 385 ms | 0 |
| Thu 17 | 0 | 0.0 | 452 ms | 0 |
| Thu 19 | 0 | 0.0 | 251 ms | 0 |
| Thu 21 | 0 | 0.0 | 394 ms | 0 |
| Thu 23 | 0 | 0.0 | 414 ms | 0 |
| Fri 01 | 0 | 0.0 | 476 ms | 0 |
| Fri 03 | 0 | 0.0 | 429 ms | 0 |
| Fri 05 | 0 | 0.0 | 277 ms | 0 |
| Fri 07 | 0 | 0.0 | 345 ms | 0 |
| Fri 09 | 0 | 0.0 | 377 ms | 0 |
| Fri 11 | 0 | 0.0 | 347 ms | 0 |
| Fri 12 | 0 | 0.0 | 448 ms | 0 |
| Fri 14 | 0 | 0.0 | 284 ms | 0 |
| Fri 16 | 0 | 0.0 | 459 ms | 0 |
| Fri 18 | 0 | 0.0 | 421 ms | 0 |
| Fri 19 | 0 | 0.0 | 433 ms | 0 |
| Fri 21 | 0 | 0.0 | 375 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for MCJars 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 MCJars goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MCJars alerts to Slack, Discord or a webhook — free.
We track MCJars (mcjars.app) as part of the Gaming group. MCJars is a service that provides Minecraft server owners with the ability to download server jars and other files with ease. Not affiliated with Mojang AB.
MCJars publishes an official status page at status.mcjars.app; when we can read it, its incident level is folded into the status shown here.
Common problems for gaming services: login and matchmaking failures, server disconnects, and store or download errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 385 ms average, 137–476 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 MCJars incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
385 ms on average over the last 24 hours (137–476 ms).
Yes, at https://status.mcjars.app.
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 MCJars here at once, the problem is on MCJars'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 MCJars. 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.