Does QoS on letter Q share fate with other letters?

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

Where is QoS measured first?

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

QoS: design in São Paulo (GRU) · Q-49

Runbook Q-49 for QoS in São Paulo (GRU). Marker xserv-q-86a16c068f83. This page covers design for LATAM operators, not a worldwide average.

QoS: Why it matters on this continent

Design for QoS on letter Q starts in São Paulo (GRU). Runbook q-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.

QoS: How XServ runs it day to day

Probes for QoS (q-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.

QoS: What operators should measure

Policy for QoS is versioned as q-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.

QoS regions Q-11

Region names on q-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. QoS dashboards never say “LATAM” as if it were one RTT.

QoS docs Q-12

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