Observability / o

Observability: regions in Bogotá (BOG) · O-59

xserv-o-71f011a1f9f9

Runbook O-59 for Observability in Bogotá (BOG). Marker xserv-o-71f011a1f9f9. This page covers regions for LATAM operators, not a worldwide average.

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: Why it matters on this continent

Design for Observability on letter O starts in São Paulo (GRU). Runbook o-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.

Observability capacity O-04

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 handoff O-05

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 rollback O-06

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 peering O-07

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

How fast is rollback for o-03?
The runbook is a command plus a named owner. There is no wait for a weekly change freeze.
Is transit the default path?
No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.