Peering Policy & Information
Open Peering Policy
We peer with any network that meets the requirements below. No traffic ratio is enforced; a signed agreement is required.
AS36262 Network Information
Autonomous System Number
AS36262
AS Name
HASHTABLE-PREMIUM-TIER
IRR Database
ARIN
Prefix Filtering
RPKI + ARIN IRR
We do not publish an AS-SET. Build your filters from ROAs and route objects with origin AS36262; our prefixes are listed on the geofeed page.
Peering Contact
Policy Summary
These fields mirror our PeeringDB record. If the two ever disagree, PeeringDB is authoritative.
Peering Requirements
General
- Operate a publicly routable ASN
- Keep an up-to-date PeeringDB entry with working NOC contacts
- Maintain current IRR records (ARIN, RADB, RIPE or equivalent)
- Publish RPKI ROAs for the prefixes you originate
- Reachable NOC for operational and abuse issues
Technical
- Support BGP-4 with dual-stack IPv4 and IPv6 sessions
- Filter prefixes on RPKI validation state and IRR data
- Announce a consistent set of routes at every shared location
- No default route, static routes or pointing traffic at us without a session
- Do not announce our prefixes onward as transit
Where We Are
These are the metros our prefixes are used in, as published in the geofeed. Our PeeringDB record carries the authoritative list of exchange ports and facilities — check it before requesting a session.
How to Request Peering
Check the requirements
Confirm your network meets the general and technical requirements above, and that your PeeringDB entry is current.
Send the request
Mail the NOC with:
- • Your ASN and network name
- • Requested locations
- • Expected traffic volume
- • Technical contact
Turn up the session
Once the agreement is in place we coordinate BGP configuration and testing with your NOC.
Send peering requests to: