_We are merging AS212263 & AS31595 into AS8801, please reach out to the team to update your records_ **Peering Policy** Rocket Fibre welcomes peering with networks that share a mutual interest in improving performance, resilience, and efficiency across the Internet. Our peering policy is selectively open, with criteria based on technical capability, operational discipline, and traffic volume. **Peering Overview** We maintain a pragmatic and scalable approach to peering. Our policy supports both public and private peering, depending on the level of traffic and strategic alignment. **Traffic-Based Guidelines** - < 500 Mbps (95th percentile): Please peer via route servers at a common public IXP. - 500 Mbps – 1 Gbps: Direct bilateral BGP sessions may be established at a shared public IXP. - > 1 Gbps: Private Network Interconnects (PNIs) will be considered at mutually available POPs. - > 10 Gbps: If we do not currently share a common location, please reach out to discuss tailored interconnection options. **Physical Interconnect Standards** We support - 10GE - 25G - 100GE - 400G interfaces only, or multiples thereof. All interconnections must be over optical fiber using standard Ethernet handoffs (LR preferred). **Technical Requirements** - To ensure operational stability and routing integrity, peers must: - Operate a publicly routed Autonomous System (ASN). - Not advertise prefixes more specific than /24 for IPv4 or /48 for IPv6. - Announce a consistent set of prefixes at all interconnection points, unless explicitly agreed otherwise. - Only send traffic destined for prefixes originated by Rocket Fibre. - Not send default routes or use static routing toward Rocket Fibre. - Maintain accurate IRR records (route/route6 objects) and filterable prefixes in a recognized IRR database. - Maintain a PeeringDB entry with up-to-date contact and network information. - Support BGP sessions with MD5 authentication if required. **Operational Expectations** - We expect prompt response to operational issues and abuse complaints. - Peering links should be monitored, and sessions maintained in a clean, non-flapping state. - We reserve the right to temporarily or permanently disable any peering session that impacts our network stability. **Multi-Exit Discriminators (MEDs)** - Not accepted by default. - If you intend to use MEDs for traffic engineering, please coordinate with us.

ok

2025-06-25T22:55:10Z