Where is Gateway measured first?

From Santiago (SCL) toward Bogotá. A global average is not an SLO for letter G.

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.

Gateway: rollback in Santiago (SCL) · G-18

Runbook G-18 for Gateway in Santiago (SCL). Marker xserv-g-b2fa832dcd0c. This page covers rollback for LATAM operators, not a worldwide average.

Gateway: A note on cost and transit

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

Gateway: Why it matters on this continent

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: How XServ runs it day to day

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.

Gateway cache G-08

Cache rules for Gateway on g-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.

Gateway headers G-09

Headers for g-09 carry the letter, the region (GRU) and a request id. Gateway debugging in São Paulo should not require a packet capture in Santiago first.

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.