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: handoff in São Paulo (GRU) · Q-29

Runbook Q-29 for QoS in São Paulo (GRU). Marker xserv-q-b0b36b914c61. This page covers handoff 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 handoff Q-05

QoS rollback Q-06

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.