AS204208

General

AS204208 maintains an open peering policy. We accept peering requests from all network operators at any exchange point where we are present. No contract or commercial agreement is required for route server peering.

Prefix Requirements

• Peers must announce a minimum /24 IPv4 and /48 IPv6.
• Dual-stack is mandatory — we will not establish peering with networks announcing only one address family.
• All announced prefixes must have valid IRR objects; RPKI-signed ROAs are strongly preferred.
• Prefixes not covered by IRR or RPKI may be filtered without notice.

Route Server Peering

• We peer on all route servers at every exchange point where we are present.
• Route server sessions are the preferred method for initial connectivity.
• No minimum traffic is required for route server peering.
• Networks are encouraged to start via route servers and transition to bilateral sessions once traffic levels justify it.

Bilateral Peering

• Bilateral sessions require a minimum of 50 Mbps sustained on the 95th percentile over a 30-day period.
• Traffic ratio must remain no more than 4:1 (in either direction). Networks exceeding this ratio will be asked to revert to route server sessions.
• A single BGP session per exchange point unless mutually agreed otherwise.
• MD5 authentication and BFD (minimum 300ms interval) are required on all bilateral sessions.
• MAX-PREFIX limits are enforced on all sessions and will trigger automatic shutdown if exceeded.

Operational Requirements

• PeeringDB record must be maintained and kept current, including valid NOC and abuse contacts.
• Abuse reports must be acknowledged and acted upon within 24 hours.
• No default routes or static routes may be pointed at our prefixes.
• No MED manipulation or community stripping on received routes from our ASN.
• Our routes must not be resold as transit to third parties.
• Peers must not announce hijacked or disputed prefixes.

De-Peering

We reserve the right to terminate any peering session without prior notice in the event of route leaks, prefix hijacking, persistent abuse from the peer’s network, sustained violation of the traffic ratio, or any action that negatively impacts the stability or security of our network.