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.

Observability: policy in Bogotá (BOG) · O-75

Runbook O-75 for Observability in Bogotá (BOG). Marker xserv-o-855dcefcbf02. This page covers policy for LATAM operators, not a worldwide average.

Observability: What operators should measure

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.

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

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.

Observability cache O-08

Cache rules for Observability on o-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.