QoS: regions in Bogotá (BOG) · Q-47

Runbook Q-47 for QoS in Bogotá (BOG). Marker xserv-q-b124fcd85066. This page covers regions for LATAM operators, not a worldwide average.

QoS: How this letter ties to the rest

Handoff from letter Q QoS into the rest of the platform uses the same request IDs as the gateway. Runbook q-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

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 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.

QoS design Q-01

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 probe Q-02

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.