Is transit the default path?

No. Peering in Miami is default; transit to São Paulo is overflow and is billed that way.

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.

Gateway: capacity in Miami (MIA) · G-16

Runbook G-16 for Gateway in Miami (MIA). Marker xserv-g-84159e720f0f. This page covers capacity for LATAM operators, not a worldwide average.

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: 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 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.