Does Jitter on letter J share fate with other letters?

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

Where is Jitter measured first?

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

Jitter: headers in São Paulo (GRU) · J-69

Runbook J-69 for Jitter in São Paulo (GRU). Marker xserv-j-abdd6bbb898f. This page covers headers for LATAM operators, not a worldwide average.

Jitter: What operators should measure

Policy for Jitter is versioned as j-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.

Jitter: Failure modes we actually see

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

Jitter: How this letter ties to the rest

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

Jitter capacity J-04

Jitter handoff J-05

Jitter rollback J-06

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

Jitter peering J-07

Peering for Jitter (j-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.