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.

Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

QoS: peering in Bogotá (BOG) · Q-19

Runbook Q-19 for QoS in Bogotá (BOG). Marker xserv-q-9733ca5d4685. This page covers peering 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 rollback Q-06

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 peering Q-07

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

QoS cache Q-08

Cache rules for QoS on q-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.

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.