Is transit the default path?

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

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.

Jitter: docs in Miami (MIA) · J-24

Runbook J-24 for Jitter in Miami (MIA). Marker xserv-j-5b8bf45205f5. This page covers docs for LATAM operators, not a worldwide average.

Jitter: A note on cost and transit

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: Why it matters on this continent

Design for Jitter on letter J starts in São Paulo (GRU). Runbook j-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.

Jitter: How XServ runs it day to day

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

Jitter handoff J-05

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

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.

Jitter cache J-08

Cache rules for Jitter on j-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.