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: docs in Miami (MIA) · E-48

Runbook E-48 for Edge in Miami (MIA). Marker xserv-e-4594307f55b5. This page covers docs for LATAM operators, not a worldwide average.

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: How XServ runs it day to day

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

Edge capacity E-04

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 handoff E-05

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