Peering Policy

AS202941 maintains an Open peering policy

Our Philosophy

At Astrava, we believe in an open and interconnected Internet. We firmly oppose networks that purposefully lock down their infrastructure to charge for peering. The Internet was built on the principle of open connectivity, and we're committed to maintaining that vision.

"We believe in an Internet which is open for connectivity. We do not support networks which purposely lock down their network so you have to pay for peering." - Kyle Müller

Policy Summary

Technical Requirements

To establish a peering session with AS202941, you must meet the following requirements:

Internet Exchange Peering

We strongly prefer IX peering over private interconnects. IX peering provides several advantages:

• Lower operational complexity
• Shared infrastructure costs
• Access to route servers for automatic peering
• Neutral meeting point for networks
• Scalability without additional cross-connects

We are present at 2 Internet Exchanges worldwide. View our full IX presence →

Private Network Interconnects (PNI)

We will consider private interconnects only in the following cases:

• No common Internet Exchange points exist
• Significant traffic volume justifies dedicated capacity
• Geographic requirements make IX peering impractical
• Redundancy requirements beyond IX connectivity

Anycast Considerations

We announce anycast routes from our network. Each of our Points of Presence (PoPs) will announce our regional IP set. If you're receiving traffic from AS202941, it will typically come from the nearest PoP.

For networks seeking optimal routing, we recommend:

• Peering at multiple IX locations if possible
• Obtaining IP transit from a larger provider (potentially one of our transit providers as well)
• Using BGP communities to influence traffic engineering if needed

How to Request Peering

Alternatively, you can contact our NOC directly:

• Email: peering@astrava.cloud
• PeeringDB: peeringdb.com/asn/202941