Skip to content

Outage tracker / Minecraft

Is Minecraft down?

I'm having a problem

Awaiting datachecked 1 minute ago

We reached Minecraft from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Oct 5, 2026, 8:15 PM UTC, Minecraft answered RealUptime's probes in all 9 regions that returned a reading. RealUptime could not obtain a reading from Europe, which is a fact about our own probe there and is not evidence about Minecraft.

Functional endpoints verified

No outage recorded in the 46 days we have measured Minecraft (since Aug 20, 2026).

Email me the next time we see Minecraft go down

Measured by our own probes from ten regions, not Minecraft's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East140 msOperational
US-West4453 msOperational
Europe65 msAwaiting data
Asia-Pacific1043 msOperational
US-Central4048 msOperational
Canada431 msOperational
UK2610 msOperational
Southeast Asia1315 msOperational
Australia1166 msOperational
South America4168 msOperational
their status pagetheir claim, not our reading

Minecraft publishes no status feed we can read, so the only independent reading here is ours on the left.

Minecraft response time, by region

US-East
483msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 434ms2026-09-07 UTC: p95 437ms2026-09-08 UTC: p95 487ms2026-09-09 UTC: p95 553ms2026-09-10 UTC: p95 417ms2026-09-11 UTC: p95 467ms2026-09-12 UTC: p95 390ms2026-09-13 UTC: p95 418ms2026-09-14 UTC: p95 383ms2026-09-15 UTC: p95 380ms2026-09-16 UTC: p95 471ms2026-09-17 UTC: p95 422ms2026-09-18 UTC: p95 388ms2026-09-19 UTC: p95 466ms2026-09-20 UTC: p95 486ms2026-09-21 UTC: p95 463ms2026-09-22 UTC: p95 441ms2026-09-23 UTC: p95 623ms2026-09-24 UTC: p95 928ms2026-09-25 UTC: p95 438ms2026-09-26 UTC: p95 415ms2026-09-27 UTC: p95 355ms2026-09-28 UTC: p95 352ms2026-09-29 UTC: p95 337ms2026-09-30 UTC: p95 332ms2026-10-01 UTC: p95 544ms2026-10-02 UTC: p95 324ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 518ms2026-10-05 UTC: p95 483ms
Sep 6Sep 20Oct 5
US-West
1.4sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 508ms2026-09-07 UTC: p95 535ms2026-09-08 UTC: p95 753ms2026-09-09 UTC: p95 757ms2026-09-10 UTC: p95 2.4s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 3.3s2026-09-13 UTC: p95 3.4s2026-09-14 UTC: p95 608ms2026-09-15 UTC: p95 3.5s2026-09-16 UTC: p95 2.5s2026-09-17 UTC: p95 898ms2026-09-18 UTC: p95 960ms2026-09-19 UTC: p95 3.3s2026-09-20 UTC: p95 3.8s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 979ms2026-09-23 UTC: p95 640ms2026-09-24 UTC: p95 558ms2026-09-25 UTC: p95 757ms2026-09-26 UTC: p95 795ms2026-09-27 UTC: p95 563ms2026-09-28 UTC: p95 744ms2026-09-29 UTC: p95 722ms2026-09-30 UTC: p95 755ms2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 629ms2026-10-03 UTC: p95 2.6s2026-10-04 UTC: p95 889ms2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
Europe
1.8sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 426ms2026-09-07 UTC: p95 420ms2026-09-08 UTC: p95 432ms2026-09-09 UTC: p95 478ms2026-09-10 UTC: p95 474ms2026-09-11 UTC: p95 505ms2026-09-12 UTC: p95 500ms2026-09-13 UTC: p95 451ms2026-09-14 UTC: p95 699ms2026-09-15 UTC: p95 723ms2026-09-16 UTC: p95 755ms2026-09-17 UTC: p95 834ms2026-09-18 UTC: p95 760ms2026-09-19 UTC: p95 850ms2026-09-20 UTC: p95 886ms2026-09-21 UTC: p95 899ms2026-09-22 UTC: p95 839ms2026-09-23 UTC: p95 797ms2026-09-24 UTC: p95 861ms2026-09-25 UTC: p95 925ms2026-09-26 UTC: p95 874ms2026-09-27 UTC: p95 621ms2026-09-28 UTC: p95 760ms2026-09-29 UTC: p95 744ms2026-09-30 UTC: p95 740ms2026-10-01 UTC: p95 752ms2026-10-02 UTC: p95 796ms2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 851ms2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Asia-Pacific
1.6sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 2.2s2026-09-09 UTC: p95 3.2s2026-09-10 UTC: p95 4.0s2026-09-11 UTC: p95 3.1s2026-09-12 UTC: p95 4.6s2026-09-13 UTC: p95 4.7s2026-09-14 UTC: p95 4.4s2026-09-15 UTC: p95 5.0s2026-09-16 UTC: p95 4.8s2026-09-17 UTC: p95 2.3s2026-09-18 UTC: p95 2.1s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 3.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 2.2s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 917ms2026-09-28 UTC: p95 916ms2026-09-29 UTC: p95 864ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 965ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.8s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5
US-Central
603msp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 925ms2026-09-07 UTC: p95 865ms2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 808ms2026-09-10 UTC: p95 940ms2026-09-11 UTC: p95 591ms2026-09-12 UTC: p95 729ms2026-09-13 UTC: p95 2.1s2026-09-14 UTC: p95 651ms2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 677ms2026-09-17 UTC: p95 607ms2026-09-18 UTC: p95 581ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 716ms2026-09-21 UTC: p95 784ms2026-09-22 UTC: p95 638ms2026-09-23 UTC: p95 984ms2026-09-24 UTC: p95 832ms2026-09-25 UTC: p95 717ms2026-09-26 UTC: p95 795ms2026-09-27 UTC: p95 640ms2026-09-28 UTC: p95 798ms2026-09-29 UTC: p95 533ms2026-09-30 UTC: p95 588ms2026-10-01 UTC: p95 882ms2026-10-02 UTC: p95 549ms2026-10-03 UTC: p95 591ms2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 603ms
Sep 6Sep 20Oct 5
Canada
1.5sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 532ms2026-09-07 UTC: p95 480ms2026-09-08 UTC: p95 630ms2026-09-09 UTC: p95 512ms2026-09-10 UTC: p95 522ms2026-09-11 UTC: p95 492ms2026-09-12 UTC: p95 2.5s2026-09-13 UTC: p95 566ms2026-09-14 UTC: p95 841ms2026-09-15 UTC: p95 732ms2026-09-16 UTC: p95 759ms2026-09-17 UTC: p95 706ms2026-09-18 UTC: p95 694ms2026-09-19 UTC: p95 638ms2026-09-20 UTC: p95 606ms2026-09-21 UTC: p95 642ms2026-09-22 UTC: p95 609ms2026-09-23 UTC: p95 709ms2026-09-24 UTC: p95 655ms2026-09-25 UTC: p95 539ms2026-09-26 UTC: p95 567ms2026-09-27 UTC: p95 540ms2026-09-28 UTC: p95 498ms2026-09-29 UTC: p95 575ms2026-09-30 UTC: p95 502ms2026-10-01 UTC: p95 611ms2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 872ms2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
UK
1.5sp95 · latest
5s2.5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 2.4s2026-09-07 UTC: p95 684ms2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 2.5s2026-09-10 UTC: p95 3.9s2026-09-11 UTC: p95 2.5s2026-09-12 UTC: p95 4.5s2026-09-13 UTC: p95 4.1s2026-09-14 UTC: p95 2.5s2026-09-15 UTC: p95 3.9s2026-09-16 UTC: p95 4.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 2.7s2026-09-20 UTC: p95 2.6s2026-09-21 UTC: p95 2.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 851ms2026-09-24 UTC: p95 1s2026-09-25 UTC: p95 847ms2026-09-26 UTC: p95 725ms2026-09-27 UTC: p95 896ms2026-09-28 UTC: p95 917ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 4.2s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 789ms2026-10-05 UTC: p95 1.5s
Sep 6Sep 20Oct 5
Southeast Asia
1.8sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 2.1s2026-09-10 UTC: p95 1.8s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 4s2026-09-16 UTC: p95 3.4s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 2.5s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.8s
Sep 6Sep 20Oct 5
Australia
4.1sp95 · latest
10s5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 3.4s2026-09-07 UTC: p95 1.9s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 3.4s2026-09-10 UTC: p95 5.4s2026-09-11 UTC: p95 2.5s2026-09-12 UTC: p95 5.5s2026-09-13 UTC: p95 5.6s2026-09-14 UTC: p95 3.5s2026-09-15 UTC: p95 5.6s2026-09-16 UTC: p95 4.6s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 3.5s2026-09-20 UTC: p95 4.0s2026-09-21 UTC: p95 2.2s2026-09-22 UTC: p95 3.4s2026-09-23 UTC: p95 1.9s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 2.2s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 2.3s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 3.1s2026-10-04 UTC: p95 4.0s2026-10-05 UTC: p95 4.1s
Sep 6Sep 20Oct 5
South America
1.6sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.8s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 2.9s2026-09-11 UTC: p95 1.4s2026-09-12 UTC: p95 4.3s2026-09-13 UTC: p95 4.7s2026-09-14 UTC: p95 3.7s2026-09-15 UTC: p95 4.4s2026-09-16 UTC: p95 3.3s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 3.0s2026-09-20 UTC: p95 2.9s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 2.5s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 1.8s2026-10-05 UTC: p95 1.6s
Sep 6Sep 20Oct 5
Why some readings show as awaiting data. 1 of 10 readings for Minecraft came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about Minecraft's actual health, so we publish no verdict for those readings rather than guessing in either direction. 1 of those reading received an actual response: we confirmed the connection, the TLS handshake, and the edge all answered, with a real measured latency. That is a positive result, we verified reachability, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Is it Minecraft, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Minecraft -- it cannot diagnose Minecraft's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 140msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Minecraft normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 4453msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Minecraft normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 4048msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Minecraft normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 431msstatus code: 200checked: Oct 5, 2026, 8:01 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Minecraft normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 4168msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Minecraft normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Awaiting dataEurope, UK
    • Europe
      Awaiting datalatency: 65msstatus code: 429reachable: automated verification filteredchecked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayMinecraft refused our Europe probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Europe to say anything on their own.
    • UK
      Operationallatency: 2610msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Minecraft normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1043msstatus code: 200checked: Oct 5, 2026, 8:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Minecraft normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1315msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Minecraft normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1166msstatus code: 200checked: Oct 5, 2026, 7:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Minecraft normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Minecraft, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Minecraft yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Minecraft.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Minecraft since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Minecraft covering any window you pick, with our measurements and Minecraft's own claim at the time, side by side.

Full availability history for Minecraft: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Minecraft uptime measured by RealUptimeLive, from this page's own readings.
[![Minecraft uptime measured by RealUptime](https://realuptime.io/outages/minecraft/badge.svg?days=30)](https://realuptime.io/outages/minecraft)
<a href="https://realuptime.io/outages/minecraft"><img src="https://realuptime.io/outages/minecraft/badge.svg?days=30" alt="Minecraft uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Minecraft's SLA implies, from our measurement

At or above your target

We measured none of downtime for Minecraft over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Minecraft's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.mojang.com/users/profiles/minecraft/notch
RealUptime is not affiliated with Minecraft; the name identifies what we measured, and nothing here speaks for Minecraft's own team. We send a single web request to Minecraft from 10 regions on our own schedule and time the response. We do not see inside Minecraft's systems, do not use an account or real transaction, and are not the same signal Minecraft's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Minecraft is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.