Tunnel Peering
Tunnel peering is available for networks that cannot establish a direct physical connection with us. It is free, but it comes with no Service Level Agreement (SLA) and no guarantees of reliability or performance.
Limits
Section titled “Limits”| Cost | Free. |
| Bandwidth | Capped at 100Mbps for all tunnel peers, regardless of the underlying link speed. The cap exists to prevent abuse and to keep tunnel peering from straining our network or hurting the quality of service for other peers. |
| Sessions | Up to 2 sessions per peer. Sessions may use separate ASNs. |
| SLA | None. We offer no SLA, uptime, or performance guarantees for tunnel peering. |
We reserve the right to terminate tunnel peering arrangements that exceed the bandwidth cap or cause performance issues.
Tunnel and session setup
Section titled “Tunnel and session setup”- Tunnel addressing: Tunnels use ULA (Unique Local Address)
/127point-to-point networks. - IPv4 sessions: IPv4 routes are exchanged using BGP’s extended next hop capability, so they are carried over the tunnel’s IPv6 addressing.
- No private ASNs: We do not peer with private ASNs.
Route filtering
Section titled “Route filtering”We filter tunnel peers on both IRR and RPKI:
- IRR: Announced prefixes must be covered by matching route objects in an IRR database.
- RPKI: Announced prefixes must be RPKI-valid. RPKI-invalid routes are dropped.
We do not accept AS-SETs at this time, so we cannot build filters from a peer’s AS-SET.
Transit over tunnel
Section titled “Transit over tunnel”We can offer transit over a tunnel peering session. IPv6 transit is free for tunnel peers, and is routed over free transit tunnels from other providers. Other transit may be cost-based; see Peering Costs for when we may charge.
At this time we can only act as an upstream for direct peers.
Expectations
Section titled “Expectations”Tunnel peering is treated the same as IX peering. The expectations in Free Peering at IXs apply to tunnel peers as well, including reciprocal announcements, no resale, no abuse, and announcing only your own resources. Tunnel peers must also meet our general Peering Requirements.
Requesting a tunnel
Section titled “Requesting a tunnel”To request a tunnel, contact our NOC at netops@saddle.network.