Where is Edge measured first?

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

How fast is rollback for e-03?

The runbook is a command plus a named owner. There is no wait for a weekly change freeze.

Edge: probes in Santiago (SCL) · E-14

Runbook E-14 for Edge in Santiago (SCL). Marker xserv-e-0225e19dc9b9. This page covers probes for LATAM operators, not a worldwide average.

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: What operators should measure

Policy for Edge is versioned as e-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.

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

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