Minecraft servers are down across both Bedrock and Java editions on June 3, 2026, locking players out of authentication and multiplayer for hours – and with Mojang yet to issue any official response at the time of writing, as reported by PCGamesN. The outage is the second major disruption in less than a week, which makes this feel less like a one-off technical hiccup and more like a sign that Microsoft‘s authentication infrastructure has a deeper reliability problem on its hands.
Here’s the context: The current issues began around 12 am PDT / 3 am EDT / 8 am BST on June 3, with Bedrock authentication servers going dark and the Realms multiplayer system – Microsoft‘s rental server product – failing on both Bedrock and Java. Bedrock players are hitting one of two error messages on launch: ‘Oh no! Something went wrong, and we couldn’t connect to the Minecraft services’ or ‘We were unable to verify what products you own. Please check your internet connection.’ Realms players on either edition are receiving Error 502 when attempting to join. Java edition authentication is unaffected, so Java players can still access single-player – cold comfort, but something. This follows a separate outage on Monday, June 1, traced to a Microsoft Azure failure that also knocked out Xbox Live, and a widespread global disruption back on January 10, 2026 that hit PC, console, and mobile simultaneously. Crowdsourced tracker Downdetector logged a spike of over 800 problem reports for Minecraft on the morning of June 3, confirming this is a widespread failure rather than isolated user error.
Honestly, the error message Bedrock players are seeing – ‘We were unable to verify what products you own’ – is doing a lot of heavy lifting to obscure what’s actually happening: Microsoft‘s central authentication stack can’t confirm that paying customers own the game they’ve already paid for. That’s not a connection error. That’s a structural dependency problem, where every Bedrock player’s ability to access the game at all is routed through servers that have now failed twice in three days. The June 1 outage was blamed on Azure; no cause has been identified publicly for June 3‘s issues yet, but a widely-circulated Reddit post from a self-described network engineer during the earlier outage flagged HTTP 503 and 502 errors from Minecraft‘s backend, pointing to fragility in the auth stack during any kind of server-side change. When a game as large as Minecraft goes fully dark for paying players twice in a week with no communication, that’s not maintenance turbulence – it’s a trust problem. The frustration playing out across Minecraft communities right now echoes what we saw when Destiny 2 players staged an in-game server protest after Bungie left them without reliable access or meaningful answers.
What remains unclear is when services will be restored, what caused the June 3 outage specifically, and whether this is once again tied to Azure infrastructure or a separate issue entirely. Mojang had not published any acknowledgement or status update at the time of writing – check the official Minecraft Help Centre and Mojang‘s social channels for any real-time updates. If you’re on Java, single-player is your best option right now. If you’re on Bedrock, there is currently no workaround – the authentication failure blocks access to the game entirely. The next concrete signal to watch for is an official cause statement from Mojang or Microsoft, and whether any infrastructure changes are announced in the wake of what is shaping up to be an unusually unstable stretch for Minecraft‘s online services.
Have you been locked out since the outage started, and does Mojang‘s silence make the situation worse? And given that this is the second major failure in three days, does this change how much you rely on Minecraft‘s online features going forward? Sound off in the comments below, and keep your eyes on GameLuster for more Minecraft coverage.
