Peering Policy & Information
Open Peering Policy
We peer with any network that meets the requirements below — no ratio, no contract and no minimum number of locations.
AS40818 Network Information
Autonomous System Number
AS40818
AS Name
INSTADART-AS
IRR Database
ARIN (MNT-INSTA-44)
Prefix Filtering
RPKI + ARIN IRR
We do not publish an AS-SET. Build your filters from ROAs and route objects with origin AS40818; 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
Peering Locations
San Jose, California
US-CA
Phoenix, Arizona
US-AZ
Ashburn, Virginia
US-VA
Tokyo, Japan
JP-13
Osaka, Japan
JP-27
Singapore
SG-01
Both public exchange and private interconnect are available in these metros. Our current exchange ports and their capacities are listed on PeeringDB.
How to Request Peering
Check the requirements
Confirm your network meets the general and technical requirements above.
Update PeeringDB
Make sure your profile lists the locations you want to peer at and a contact we can reach.
Send the request
Include:
- • Your ASN and network name
- • Requested peering locations
- • Expected traffic volume and direction
- • A technical contact for turn-up
Turn-up
We confirm addressing, configure the session and verify prefix counts in both directions before considering it live.
Send peering requests to: