Does Gateway on letter G share fate with other letters?

The control plane is shared. Data-plane queues for Gateway stay isolated, so incident g-01 cannot drain neighbor letters.

Where is Gateway measured first?

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

Gateway: handoff in São Paulo (GRU) · G-41

Runbook G-41 for Gateway in São Paulo (GRU). Marker xserv-g-3e164600aac2. This page covers handoff for LATAM operators, not a worldwide average.

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: 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 rollback G-06

Gateway peering G-07

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

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.