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

Runbook E-74 for Edge in Santiago (SCL). Marker xserv-e-c20fa0117e67. 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 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.

Edge regions E-11

Region names on e-11 match DNS and tickets: Bogotá / BOG, with Miami as the documented pair. Edge dashboards never say “LATAM” as if it were one RTT.

Edge docs E-12

Public docs for letter E stay aligned with identifier xserv-e-pack. Page e-12 is the Edge slice operators search before the homepage. Edits in Miami show up in São Paulo on the next publish.