Peering Policy

AS204258 operates an open peering policy and welcomes peering requests from networks of all sizes. We believe in the benefits of direct interconnection for improved routing, reduced latency, and enhanced redundancy.

General Peering Information

• ASN: 204258
• Peering Policy: Open
• Peering Contact: peering@as204258.net
• NOC Contact: noc@as204258.net
• PeeringDB: AS204258 on PeeringDB

IPv4 Prefixes

• Announced Prefixes: 185.109.40.0/22
• IRR Database: RIPE
• AS-SET: AS-VIVE

IPv6 Prefixes

• Announced Prefixes: 2a06:4e80::/29
• IRR Database: RIPE
• AS-SET: AS-VIVE

Internet Exchange Points

We are present at the following Internet Exchange Points:

Peering Requirements

We have minimal requirements for peering:

1. Technical Requirements:

   • Must operate a 24/7 NOC with published contact details
   • Must maintain an up-to-date PeeringDB entry
   • Must maintain accurate routing information in an IRR database
   • Must support both IPv4 and IPv6 (preferred, but not mandatory)

2. Operational Requirements:

   • Timely response to operational issues
   • Advance notification of maintenance windows
   • Adherence to BGP best practices

Private Network Interconnect (PNI)

For networks with substantial traffic exchange, we are open to establishing Private Network Interconnects. Please contact our peering team to discuss PNI opportunities.

Requirements for PNI:

• Minimum traffic threshold: 1 Gbps
• Mutually beneficial traffic exchange
• Presence in common facilities

How to Peer

1. Internet Exchange Point Peering:

   • Configure your router with our peering details from the IXP route servers
   • Send a peering request to peering@as204258.net with:
     • Your ASN
     • IXP location
     • Your IPv4/IPv6 addresses at the IXP
     • Expected traffic levels

2. Private Peering:

   • Contact peering@as204258.net with:
     • Your ASN and network details
     • Proposed interconnection location
     • Expected traffic volumes
     • Technical contact information

Routing Policy

• We announce our own prefixes and customer prefixes
• We do not accept default routes
• We do not accept prefixes longer than /24 for IPv4 and /48 for IPv6
• We implement prefix filtering based on IRR data
• We respect BGP communities for traffic engineering

BGP Communities

More detailed community documentation available upon request

Contact Information

• General Peering Inquiries: peering@as204258.net
• Network Operations Center: noc@as204258.net

We typically respond to peering requests within 2-3 business days.

For the most up-to-date information, please visit our PeeringDB entry