XServ platform / x
XServ platform: docs in Miami (MIA) · X-60
xserv-x-54b8730c183e
Runbook X-60 for XServ platform in Miami (MIA). Marker xserv-x-54b8730c183e. This page covers docs for LATAM operators, not a worldwide average.
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: How XServ runs it day to day
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 handoff X-05
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 rollback X-06
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 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.
- 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.