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: timeouts in Santiago (SCL) · Q-10

Runbook Q-10 for QoS in Santiago (SCL). Marker xserv-q-c2e17db04b06. This page covers timeouts for LATAM operators, not a worldwide average.

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