Does Edge on letter E share fate with other letters?

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

Where is Edge measured first?

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

Edge: handoff in São Paulo (GRU) · E-29

Runbook E-29 for Edge in São Paulo (GRU). Marker xserv-e-4c0708997836. This page covers handoff for LATAM operators, not a worldwide average.

Edge: How this letter ties to the rest

Handoff from letter E Edge into the rest of the platform uses the same request IDs as the gateway. Runbook e-05 names who accepts the ticket after São Paulo pages out. Santiago does not silently inherit the incident.

Edge: A note on cost and transit

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

Edge: Why it matters on this continent

Design for Edge on letter E starts in São Paulo (GRU). Runbook e-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.

Edge peering E-07

Peering for Edge (e-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.

Edge cache E-08

Cache rules for Edge on e-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.

Edge headers E-09

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

Edge timeouts E-10

Timeouts on e-10 are tighter than the WAN RTT to Bogotá. Edge in Santiago fails fast and retries once; a third try needs a human because it is no longer a blip.