Gateway: policy in Bogotá (BOG) · G-75

Runbook G-75 for Gateway in Bogotá (BOG). Marker xserv-g-14118ff106ab. This page covers policy for LATAM operators, not a worldwide average.

Gateway: What operators should measure

Policy for Gateway is versioned as g-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.

Gateway: Failure modes we actually see

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

Gateway: How this letter ties to the rest

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

Gateway timeouts G-10

Timeouts on g-10 are tighter than the WAN RTT to Bogotá. Gateway in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.

Gateway regions G-11

Region names on g-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Gateway dashboards never say “LATAM” as if it were one RTT.

Gateway docs G-12

Public docs for letter G stay aligned with identifier xserv-g-pack. Page g-12 is the Gateway slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.

Gateway design G-01

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