Is transit the default path?

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

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.

QoS: capacity in Miami (MIA) · Q-28

Runbook Q-28 for QoS in Miami (MIA). Marker xserv-q-5cd02b03fdcb. This page covers capacity 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 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.