Is transit the default path?

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

Does Observability on letter O share fate with other letters?

The control plane is shared. Data-plane queues for Observability stay isolated, so incident o-01 cannot drain neighbor letters.

Observability: capacity in Miami (MIA) · O-76

Runbook O-76 for Observability in Miami (MIA). Marker xserv-o-260eeaf749a7. This page covers capacity for LATAM operators, not a worldwide average.

Observability: Failure modes we actually see

Capacity notes for o-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.

Observability: How this letter ties to the rest

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

Observability: A note on cost and transit

Rollback for o-06 is a documented command, not a hope. Transit is billed as backup while Observability prefers peering in Santiago. If cost spikes, the runbook cuts overflow to Bogotá before touching customer prefixes.

Observability probe O-02

Probes for Observability (o-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.

Observability policy O-03

Policy for Observability is versioned as o-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.