Mojang, Microsoft, Xbox, PlayFab, and Minecraft service status

Login, sessions, skins, Xbox, PlayFab, Realms, and third-party servers fail independently; map components and evidence kinds without a fake global green light.

Last verified: 2026-08-11
Evidence cutoff: 2026-08-11

Direct answer: “Is Minecraft down?” is not one switch. Login, sessions, skins, launcher metadata, Xbox identity, PlayFab multiplayer services, Realms, and third-party game servers fail independently. A useful map names components, the kind of evidence available for each, and when the honest public state is Unknown or Not collected—not a fake global green light.

This article maps the service layers involved in Minecraft sign-in and platform access. For live single-vantage rows, use the service status board. For separating platform trouble from a single community server, start with platform vs server outages.

Evidence kinds

Kind	What it is	What it can support
Official report	Vendor status page or incident API	Vendor-scoped degradation/outage language for that product surface
Synthetic anonymous	Unauthenticated probe of a documented public contract	“This contract responded/failed from our vantage,” not full product health
Synthetic authenticated	Login/join/list under a controlled bot identity	Stronger functional signal when enabled; still not every player’s network
Not collected	No collector is enabled	Absence of data—not an outage

Never promote a lone probe failure to “Minecraft is down” without corroboration.

Component map

Launcher and version distribution

Contract example: GET https://piston-meta.mojang.com/mc/game/version_manifest_v2.json
Verified 2026-08-11: the manifest returns JSON with a latest object (release and snapshot ids) and a nonempty versions list. Release and snapshot IDs change, so do not hard-code today’s values into status guidance.
Proves: metadata distribution edge answered with a plausible schema.
Does not prove: every CDN edge, installer package, or launcher UI is healthy.

Minecraft Services public keys

Contract example: GET https://api.minecraftservices.com/publickeys
Verified 2026-08-11: HTTPS success with key sets named profilePropertyKeys, playerCertificateKeys, and authenticationKeys, each carrying public-key material.
Proves: key distribution endpoint responded with the expected structure.
Does not prove: every certificate consumer or chat-signing path worldwide.

Mojang identity lookup and sessions

Public identity edges include hosts such as api.mojang.com (name→UUID lookup) and sessionserver.mojang.com (signed profile delivery), as recorded in community protocol documentation.
Anonymous name→UUID and signed profile GETs can show whether those HTTP contracts answer.
Does not prove: your password, your Microsoft link, or a specific multiplayer join packet will succeed.
Deeper interpretation belongs in authentication servers status.

Skin and texture delivery

Texture hosts such as textures.minecraft.net deliver skin/cape blobs referenced from profile properties.
Fetching a texture proves that object was retrievable under the allowlisted URL shape.
Does not prove: character creator, marketplace cosmetics, or every regional cache.

Microsoft consumer identity discovery

Contract example: GET https://login.microsoftonline.com/consumers/v2.0/.well-known/openid-configuration
Verified 2026-08-11: document includes issuer and authorization/token endpoints for the consumers authority.
Proves: OIDC discovery document retrieval.
Does not prove: password login, MFA, or Xbox token minting for a given account.

Xbox network

Minecraft failures can involve Xbox account, multiplayer, or console networking paths.
Official surface: Xbox network status (URL reachable 2026-08-11; the status content itself renders interactively and may require a browser).
Until a machine-readable Xbox collector exists, dashboards should label Xbox-wide state Not collected rather than inventing a green row from an unrelated HTTPS HEAD.

PlayFab

PlayFab publishes a first-party status site and machine-readable summary:
- UI: status.playfab.com
- API: https://status.playfab.com/api/v2/summary.json
Verified 2026-08-11: the summary JSON includes a page updated_at, a components list with per-component status values (every listed component reported operational at this check), and incident lists that are empty when nothing is open.
PlayFab components cover a large multiplayer/backend portfolio—Authentication, Matchmaking, Lobby, Cloud Script, and many more. An incident scoped to one component is not automatically “Java multiplayer is down.”
Use PlayFab’s own component names when quoting official impact.

Realms

Realms are a separate subscription product path from arbitrary third-party servers.
Until Realms-specific collectors exist and are disclosed, treat Realms functional monitoring as Not collected and point readers to Realms status limits rather than faking a Realms row from launcher metadata alone.

Third-party game servers

Community servers are not Mojang components. Check them with the server status checker and the address guides.
A popular server outage is not a platform outage; a platform auth outage can still block joins to online-mode servers.

Diagnostic flow

Name the symptom class: cannot launch, cannot sign in, cannot join Realms, cannot join a specific address, skins missing, marketplace only, console-only, etc.
Check official vendor surfaces that match that class (Minecraft Help, Xbox status, PlayFab summary) before trusting social screenshots.
Open the service status board for single-vantage synthetic rows and read each row’s method and detail.
For auth-shaped errors, continue with authentication servers status and authentication servers are currently unavailable rather than blaming a random game server.
For one hostname failing while platform login works, treat it as server/DNS/network isolation.
If only one synthetic probe fails and official pages are quiet, keep the public claim at Unknown or component-scoped degraded—not a global outage.
If a component is Not collected, say so. Missing telemetry is not uptime.

Evidence limits

HTTP reachability ≠ full functional success.
Authenticated monitors, where enabled, still represent one bot identity and controlled canaries, not every account. As of this check, authenticated login/join transactions, Realms metadata reads, and continuous multi-region coverage are not collected.
User-report aggregators can describe symptoms; they do not independently prove vendor outages.
PlayFab/Xbox/Microsoft portfolios are broader than Minecraft; map incidents to the components they name.
This page does not assert that all services are operational at publication time.

Last verified

Evidence cutoff: 2026-08-11
Sources rechecked: version manifest, public keys, Microsoft OIDC discovery, PlayFab status UI and summary API, Xbox status URL reachability, community protocol documentation for identity and texture hosts, and the MinecraftStatus /status surface