Peering Policy & Information
Open Peering Policy
We maintain an open peering policy and welcome new peering partners globally
AS36262 Network Information
Autonomous System Number
AS36262
Network Name
HASHTABLE-PREMIUM-TIER
IRR Database
RADB, ARIN
AS-SET
AS-HASHTABLE
Peering Contact
Peering Requirements
General Requirements
- Maintain a publicly routable ASN
- Have an up-to-date PeeringDB entry
- Maintain valid IRR records (RADB, ARIN, RIPE, etc.)
- Operate a 24/7 NOC with competent staff
- Agree to our peering terms and conditions
Technical Requirements
- Support BGP-4 with MD5 authentication
- Implement prefix filtering based on IRR records
- Set appropriate BGP timers (30s keepalive, 90s hold)
- Announce consistent routes at all peering locations
- Support both IPv4 and IPv6 peering sessions
Peering Locations
San Francisco Bay Area
Los Angeles
Seattle
Chicago
Peering Types
Public Peering
Exchange peering via Internet Exchange Points (IXPs). Ideal for networks with moderate traffic volumes.
- Sub-100 Mbps: Route servers
- 100+ Mbps: Direct BGP session
Private Peering
Direct cross-connects in mutual facilities. Recommended for high-volume traffic exchange partners.
- 1Gbps minimum capacity
- Dedicated cross-connect
How to Request Peering
Review Requirements
Ensure your network meets all general and technical requirements listed above
Update PeeringDB
Ensure your PeeringDB profile is complete and accurate with current NOC contacts
Submit Request
Send your peering request with the following information:
- • Your ASN and network name
- • Requested peering locations
- • Expected traffic volumes
- • Technical contact information
Configuration
Once approved, we'll coordinate BGP session configuration and testing
Send peering requests to: