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

Runbook Q-33 for QoS in São Paulo (GRU). Marker xserv-q-1d05868ce791. This page covers headers for LATAM operators, not a worldwide average.

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: Failure modes we actually see

Capacity notes for q-04 assume rainy-season power in Miami and festival peaks toward São Paulo. The failure we actually see is a single uplink, not a cartoon partition of the whole continent. Spare ports and a second provider sit on the same runbook.

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 capacity Q-04

QoS handoff Q-05

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.