XServ platform / x
XServ platform: capacity in Miami (MIA) · X-52
xserv-x-1d55cbfbd3f6
Runbook X-52 for XServ platform in Miami (MIA). Marker xserv-x-1d55cbfbd3f6. This page covers capacity for LATAM operators, not a worldwide average.
XServ platform: Failure modes we actually see
Capacity notes for x-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.
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 design X-01
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 probe X-02
Probes for XServ platform (x-02) leave Santiago every 15s toward Bogotá. XServ pages the named owner if loss or RTT crosses the letter budget. A probe never shares a queue with bulk transfers, so a saturated WAN does not hide a dead PoP.
XServ platform policy X-03
Policy for XServ platform is versioned as x-03. Operators measure error rate, p95 from Bogotá, and time-to-rollback — not a worldwide average. Changes land in Bogotá first, then Miami, with a hold if either region regresses.
XServ platform capacity X-04
Capacity notes for x-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.
- Is transit the default path?
- No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.
- 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.