Does XServ platform on letter X share fate with other letters?

The control plane is shared. Data-plane queues for XServ platform stay isolated, so incident x-01 cannot drain neighbor letters.

Where is XServ platform measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter X.

XServ platform: handoff in São Paulo (GRU) · X-05

Runbook X-05 for XServ platform in São Paulo (GRU). Marker xserv-x-cb820849d89c. This page covers handoff for LATAM operators, not a worldwide average.

XServ platform: How this letter ties to the rest

Handoff from letter X XServ platform into the rest of the platform uses the same request IDs as the gateway. Runbook x-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

XServ platform: A note on cost and transit

Rollback for x-06 is a documented command, not a hope. Transit is billed as backup while XServ platform prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

XServ platform: Why it matters on this continent

Design for XServ platform on letter X starts in São Paulo (GRU). Runbook x-01 keeps a single owner, a written rollback, and a traffic split that can be reversed without a global freeze. Neighbors in Santiago only take overflow after the local pool fails a health window.

XServ platform rollback X-06

XServ platform peering X-07

Peering for XServ platform (x-07) prefers the IX fabric that already carries last-mile ISPs in Bogotá. Session counts and prefix limits are on the same page as the Miami backup path.

XServ platform cache X-08

Cache rules for XServ platform on x-08 keep language-correct objects near Miami. São Paulo is a sibling cache, not an origin. TTLs are short enough that a bad asset does not live through a weekend.

XServ platform headers X-09

Headers for x-09 carry the letter, the region (GRU) and a request id. XServ platform debugging in São Paulo should not require a packet capture in Santiago first.