Is transit the default path?

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

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.

Edge: capacity in Miami (MIA) · E-28

Runbook E-28 for Edge in Miami (MIA). Marker xserv-e-6c8957d9e477. This page covers capacity for LATAM operators, not a worldwide average.

Edge: Failure modes we actually see

Capacity notes for e-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.

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 rollback E-06

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.