BGP Peering Policy
Open peering policy for AS402003
AS Number
AS402003
Network Name
EZ Game Host, LLC
Peering Policy
Open (Selective)
General Requirements
- Public AS number (not private ASN)
- Operational 24/7 Network Operations Center (NOC)
- Maintain accurate routing registries (IRR, PeeringDB)
- Proper route filtering and prefix limits
- IPv4 and/or IPv6 support
- No default route announcements
Traffic Requirements
- Minimum 1 Gbps peak traffic exchange
- Reasonable traffic ratio (we prefer balanced traffic)
- Consistent traffic patterns
Technical Requirements
- BGP-4 support (RFC 4271)
- MD5 authentication or BGPsec preferred
- Maximum prefix limits per session
- Proper route filtering and RPKI validation
- No route leaks or hijacks
We peer at the following Internet Exchange Points (IXPs) and data centers:
United States
Multiple locations - Contact for details
For specific peering locations and availability, please contact our NOC.
Open Peering
We maintain an open peering policy and are generally willing to peer with networks that meet our requirements. We evaluate each peering request on a case-by-case basis.
Selective Criteria
While our policy is open, we may be selective based on:
- Geographic location and route diversity
- Traffic volume and growth potential
- Network reputation and operational history
- Mutual benefit and cost savings
Settlement-Free Peering
All peering arrangements are settlement-free (no payment required). We expect mutual benefit from traffic exchange and improved routing.
Route Filtering
We implement strict route filtering:
- RPKI validation for route security
- IRR-based prefix filtering
- Maximum prefix limits per peer
- Rejection of bogon and martian routes
To request peering with AS402003, please send an email to our Network Operations Center with the following information:
- Your AS number and network name
- Peering location(s) of interest
- IPv4 and/or IPv6 prefixes you will announce
- Expected traffic volume
- NOC contact information (24/7)
- PeeringDB and IRR registry information
- Any special requirements or constraints
PeeringDB
Our network information is available on PeeringDB. Please ensure your network information is also up to date.
View on PeeringDBIRR Registrations
We maintain accurate IRR (Internet Routing Registry) entries. Please ensure your routes are properly registered in IRR databases for route filtering purposes.
RPKI
We use RPKI (Resource Public Key Infrastructure) for route origin validation. We recommend all peers implement RPKI for enhanced routing security.
Policy Updates
This peering policy may be updated from time to time. Existing peers will be notified of any significant changes. The latest version is always available on this page.
Last updated: December 3, 2025
Note: This is an open peering policy, but we reserve the right to refuse peering requests that do not meet our requirements or that we determine are not in the best interest of our network. All peering arrangements are subject to a mutual peering agreement.