Instrument sheet 02 · endpoint reachability

Mojang and Microsoft endpoint observations

A single-vantage synthetic ledger. It reports what the root endpoint did during a bounded request, without turning reachability into a global health claim.

Current evidence ledger

Endpoint reachability unknown for all 6 observations.

Single vantage point · HTTPS HEAD

Timestamped Mojang and Microsoft endpoint observations
Endpoint	Observation	Method	Evidence window
Minecraft Sessionsessionserver.mojang.com	Unknown Root endpoint returned HTTP 403. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.848Z · just now Valid through 2026-07-16 20:51:37.848Z
Minecraft APIapi.minecraftservices.com	Unknown Root endpoint returned HTTP 403. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.848Z · just now Valid through 2026-07-16 20:51:37.848Z
Mojang APIapi.mojang.com	Unknown Root endpoint returned HTTP 404. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.878Z · just now Valid through 2026-07-16 20:51:37.878Z
Minecraft Skinstextures.minecraft.net	Unknown Root endpoint returned HTTP 400. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.991Z · just now Valid through 2026-07-16 20:51:37.991Z
Minecraft Servicespiston-meta.mojang.com	Unknown Root endpoint returned HTTP 404. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.901Z · just now Valid through 2026-07-16 20:51:37.901Z
Xbox Live Authuser.auth.xboxlive.com	Unknown Root endpoint returned HTTP 404. That confirms the edge is reachable but is not evidence the service itself is healthy.	https-head-reachability-probe	Observed 2026-07-16 20:50:37.996Z · just now Valid through 2026-07-16 20:51:37.996Z

Collecting six endpoint observations

The instrument is collecting a bounded live reading. No status claim is shown until the check completes.

What the ladder proves

Each rung narrows the claim rather than accumulating false certainty.

First-party incident context
Linked · not ingested
See Minecraft Help and PlayFab status. Their content is not converted into this ledger's verdicts.
Root HTTPS reachability
Measured now
One bounded HTTPS HEAD request is sent to each fixed endpoint from the application host.
Functional service transaction
Not tested
No login, join, profile, skin, or launcher workflow is completed. A root response cannot prove those contracts.
Reachability conclusion
Time-bounded
Operational requires a clear success response. Ambiguous client responses remain Unknown; server failures or connection failure are Degraded and unconfirmed.

Claim boundary

A connection failure is evidence from this host only. It is never presented as a confirmed global outage.

Endpoint purpose register

Minecraft Session

Session and server-join identity infrastructure; the root probe does not execute session validation.

Minecraft API

Profile and account-service edge; root reachability does not prove a profile operation works.

Mojang API

Legacy player identity API edge; no UUID or history lookup is performed here.

Minecraft Skins

Texture delivery edge; this page does not request a player texture.

Minecraft Services

Version manifest distribution edge used by launchers.

Xbox Live Auth

Microsoft authentication edge; no user credential or login flow is exercised.

Interpretation questions

What exactly does this page check?

For each listed endpoint, the server sends one HTTPS HEAD request to the root and records the response class, latency, method, observed time, and validity boundary. It does not run a login or other functional transaction.

Why can a reachable endpoint still be Unknown?

API roots commonly return a client error because no route exists there. That demonstrates an edge response but does not prove the service contract is healthy, so the instrument declines to guess.

Where is the authoritative incident report?

This page is not an official feed. Use the linked Minecraft Help and PlayFab sources for first-party context, and treat this ledger as one synthetic vantage point.

First-party incident context

Root HTTPS reachability

Functional service transaction

Reachability conclusion