How fast is rollback for g-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.

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

Runbook G-39 for Gateway in Bogotá (BOG). Marker xserv-g-c785cff24295. 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 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.

Gateway probe G-02

Probes for Gateway (g-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.