Requests reviewed individually
AS11611 / Interconnection
Peering Policy.
Arctic Fox Networks welcomes settlement-free interconnection with networks that share our commitment to reliable routing, sound operational practices and efficient traffic exchange.
Peering At A Glance
General PolicyOpen
Multiple LocationsPreferred
Traffic RatioNone
ContractNot required
Where mutually available
No ratio requirement
Per current peering profile
Interconnection Guidelines
How We Peer.
Our approach prioritizes network stability, routing integrity and responsive operations. These guidelines describe the foundation for bilateral interconnection with AS11611.
Operations Requirements
Network Operations Contacts
Peering networks should maintain a 24/7/365 network operations center and a clear escalation path for time-sensitive routing and network issues.
Maintenance And Incident Coordination
Both parties should communicate planned interconnection maintenance where practical and coordinate promptly during outages or other service-impacting events.
Security And Abuse Response
Peers are expected to investigate route leaks, denial-of-service activity, spoofed traffic and other security issues that affect our interconnection.
Technical Requirements
Routing Integrity
Peers should maintain accurate IRR and RPKI records for their networks, apply appropriate prefix filters and use reasonable maximum-prefix safeguards.
Authorized Route Announcements
Peering is intended for each network's own routes and its customer routes. Unrelated third-party transit routes, default routes and unauthorized next-hop manipulation are outside the scope of peering.
Dual-Stack BGP
IPv4 and IPv6 sessions may be established where supported at a mutually agreed interconnection. Session addresses and any authentication settings are coordinated directly.
Capacity And Stability
Each party should provision adequate capacity and work cooperatively to resolve sustained congestion or instability as traffic patterns evolve.
Interconnection Requirements
Internet Exchange Peering
AS11611 accepts inquiries at shared internet exchanges. Our current listed presence includes SIX Seattle standard and jumbo fabrics, with additional exchanges planned as the network expands.
Private Network Interconnection
Private interconnection may be considered at mutually accessible facilities, based on technical fit, available capacity and operating arrangements.
Multiple Locations
Diverse interconnection locations are preferred when feasible. There is no published traffic-ratio requirement; arrangements are assessed individually.
Current exchange interfaces and facility locations are listed under Network information.
General Policy
Open Peering Approach
Our general policy is open, but interconnection is subject to routing, capacity, security and operational review. An inquiry does not automatically establish a session.
Coordinated Changes
Peers should work through their operational contacts when interconnection arrangements, routing policies or capacity requirements change.
Network Protection
Either party may need to adjust or suspend an interconnection to protect network stability or address abuse, with coordination where circumstances allow.
Peering Coordination
Contact The NOC Connect With AS11611.
Send us your ASN, PeeringDB profile, proposed exchange or facility, IPv4/IPv6 requirements and NOC contact. Our team can coordinate the next steps.