Where is XServ platform measured first?

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

How fast is rollback for x-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

XServ platform: probes in Santiago (SCL) · X-02

Runbook X-02 for XServ platform in Santiago (SCL). Marker xserv-x-63b0450e1f98. This page covers probes for LATAM operators, not a worldwide average.

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: What operators should measure

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: 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 docs X-12

Public docs for letter X stay aligned with identifier xserv-x-pack. Page x-12 is the XServ platform slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

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.