Magic Transit / L3–L4 absorb
The Causeway (Magic Transit)
The Causeway is Zipper’s Magic Transit. It drops abusive source IPs and rate-limits SYN/UDP floods at the host nftables layer, accepts customer prefixes for announce when BGP is armed, and returns scrubbed traffic to your origin over WireGuard or GRE. Keep, Moat, and Court Chord feed the denylist. Pair with The Moat for HTTP floods. This is a Cloudflare Cloudflare Magic Transit alternative included on every Zipper plan.
Cloudflare analogue: Cloudflare Magic Transit
What it is
The Causeway is Zipper’s Magic Transit. It drops abusive source IPs and rate-limits SYN/UDP floods at the host nftables layer, accepts customer prefixes for announce when BGP is armed, and returns scrubbed traffic to your origin over WireGuard or GRE. Keep, Moat, and Court Chord feed the denylist. Pair with The Moat for HTTP floods.
Cloudflare analogue: Cloudflare Magic Transit. SLA 99.95% · p99 2ms. Operators register prefixes and tunnels. Admins arm BGP announce and rate Policy.
- ▸SYN + UDP flood protect
- ▸Prefix registry
- ▸WireGuard / GRE return
- ▸BGP announce when armed
- ▸Keep ban feed
How it works
The Causeway drops banned source IPs and rate-limits SYN/UDP floods at nftables on Zipper ingress (zipper-causeway helper).
Register customer prefixes via /api/v1/causeway/prefixes. Add WireGuard or GRE return tunnels so scrubbed traffic reaches your origin.
Live BGP: turn bgpAnnounce on, mark prefixes announce=true — Court writes an atomic prefix file; zipper-bgp reloads FRR under flock (IPv4+IPv6). Operator ZIPPER_BGP_PREFIXES never overwrite Court withdraws.
Magic Transit hydrate: nft dens + SYN/UDP rates re-arm on boot and every minute; tunnel health probes persist to causeway_tunnels.
Keep, Moat, and Court Chord feed the denylist. Arm the host with ZIPPER_ASN + ZIPPER_BGP_PEER_IP / ZIPPER_BGP_PEER_ASN (paired 1:1).
GET /api/v1/causeway/status reports nft, operable BGP, sessions, advertised/RIB drift, and tunnel health. POST /api/v1/causeway/bgp-drain reconciles every minute.
Use cases
Concrete ways teams use this service on day one.
Bring your own prefix
You own 203.0.113.0/24 and want Zipper to scrub floods before origin.
- Arm ZIPPER_ASN + peer env on the host, enable bgpAnnounce on The Causeway.
- POST the CIDR to /api/v1/causeway/prefixes with announce true.
- Create a WireGuard tunnel to your origin under /api/v1/causeway/tunnels.
- Leave absorb / SYN / UDP protect on (climate floors).
HTTP site plus packet absorb
You already use Moat + Keep and want L3–L4 beside them.
- Enable The Causeway service (auto-provisioned).
- Confirm Keep packet-filter bans show up in Causeway status / nft sets.
- Tune SYN and UDP rates under Configure if needed.
Set it up in the dashboard
Dashboard → Services → The Causeway.
Register prefixes and tunnels. Check Status for nft + BGP sessions / drift.
API
Control-plane: GET|POST|PATCH|DELETE /api/v1/causeway/prefixes · GET|POST|DELETE /api/v1/causeway/tunnels · GET /api/v1/causeway/status · POST /api/v1/causeway/bgp-drain. Send Authorization: Bearer tz_live_YOUR_TOKEN.
Creates count against the plan quota. A 402 plan_limit means you are at the cap — upgrade or delete an unused resource.
Register a prefix
curl -sS -X POST https://tinyzipper.com/api/v1/causeway/prefixes \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"cidr":"203.0.113.0/24","announce":false}'Announce a prefix
curl -sS -X PATCH https://tinyzipper.com/api/v1/causeway/prefixes/PREFIX_ID \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"announce":true}'Add a WireGuard return tunnel
curl -sS -X POST https://tinyzipper.com/api/v1/causeway/tunnels \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"name":"origin-wg","kind":"wg","remote":"203.0.113.10:51820","local":"10.8.0.1"}'Causeway status
curl -sS https://tinyzipper.com/api/v1/causeway/status \ -H "Authorization: Bearer tz_live_YOUR_TOKEN"
List the same resource in JavaScript
const res = await fetch("https://tinyzipper.com/api/v1/causeway/prefixes", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.ZIPPER_TOKEN}`,
"Content-Type": "application/json"
}
});
const json = await res.json();
if (!res.ok) throw new Error(json.error ?? res.statusText);
console.log(json);Tips
BGP announce stays off until ZIPPER_ASN and ZIPPER_BGP_PEER_* are set (operable) on the host.
Prefix create/delete/announce and bgpAnnounce toggles await FRR sync; the minute drain + boot hydrate catch drift and re-arm nft.
Moat remains the HTTP flood control; Causeway is the packet layer.
- ▸L3–L4
- ▸Magic Transit
- ▸Global edge
Runbook
Leave absorb, SYN, and UDP protect on. Register prefixes and WireGuard/GRE tunnels. Live BGP + Magic Transit hydrate: bgpAnnounce + announce=true syncs FRR; drain re-arms nft/rates and probes tunnels when ASN + peers are operable.
Next: The Herald (DNS) · All docs · Create a free account