- 01
Submit the request
Use /contact or email [email protected] with your network name, ASN, target PoP and port speed. We reply within one business day with a quote and an Order Form.
- 02
Sign Order Form & MSA
Order Form references the MSA, AUP and SLA. Sign electronically (Eversign / DocuSign). Setup invoice issued upon countersignature.
- 03
Order the cross-connect
We send a pre-signed LOA. Forward to your data-centre tenant portal. SLA on the DC side is typically 1–3 business days for a copper / SMF fiber.
- 04
PeeringDB & IRR setup
Confirm your PeeringDB record is current. Register or update your AS-SET (AS-YOURASN) with all customer-cone ASNs in RIPE/RADB/ARIN. We mirror the AS-SET into our prefix-list generator.
- 05
Publish RPKI ROAs
Create ROAs for every prefix you intend to announce, using your RIR portal. Keep maxLength as tight as your real announcement.
- 06
Receive credentials
We send your peering IP, MD5 secret, route-server addresses, NOC dashboard credentials and PGP fingerprints over an authenticated channel.
- 07
Configure BGP
Use the snippets in /docs/bgp-config. Bring up sessions to RS1 and RS2. Send your aggregates only — let the route servers do the multilateral fan-out.
- 08
Validation
We verify prefix counts, RPKI status, MD5 and BFD. Looking Glass spot-check confirms your prefixes are reachable from the other PoPs.
- 09
Production
Port flips from staging VLAN into production peering LAN. First monthly invoice goes out on the next billing cycle.
What slows things down
- Cross-connect SLA at the DC (mostly outside our control).
- Missing or stale PeeringDB record — please update before requesting turn-up.
- AS-SET hierarchy that doesn't expand to all customer ASNs (route filter ends up empty).
- RIR portals (especially during ROA propagation — allow 1 hour).