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.

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.

Gateways that speak HTTP, TLS and the rest of the stack

The public door of a service is a gateway: rate limits, routing keys and protocol translation live here, not in every app.

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: 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: 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 design G-01

Gateway probe G-02

Gateway policy G-03

Gateway capacity G-04

Gateway handoff G-05

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.

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.