Where is QoS measured first?

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

How fast is rollback for q-03?

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

QoS: rollback in Santiago (SCL) · Q-42

Runbook Q-42 for QoS in Santiago (SCL). Marker xserv-q-337084c775ca. This page covers rollback for LATAM operators, not a worldwide average.

QoS: A note on cost and transit

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

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 headers Q-09

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

QoS timeouts Q-10

Timeouts on q-10 are tighter than the WAN RTT to Bogotá. QoS in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

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.