Technical documentation, peering policies, and everything you need to connect to packet:IX.
Joining packet:IX is straightforward. We keep requirements minimal by design — the barrier to peering should be as low as possible. Here's the process from application to live traffic.
Confirm you hold a valid Autonomous System Number (ASN) from a Regional Internet Registry (APNIC, RIPE, ARIN, etc.) and operate BGP-capable routing equipment.
Fill out our membership application form with your organisation details, ASN, and intended connection type (on-site or remote). Our team will review within 2 business days.
Review and sign our Peering Policy and Member Agreement. Both documents are published openly at packetix.io/policy.
For on-site connections, arrange a cross-connect to our switching fabric at one of our three Seoul facilities. For remote connections, contact one of our reseller partners.
Set up BGP sessions to our route servers (RS1 and RS2). Detailed configuration templates for common router vendors are available in our technical documentation.
Once sessions are established and prefixes are announced, you will begin exchanging traffic with all connected members instantly.
We will peer with any network that meets our general requirements, without discrimination based on traffic volume, network size, or geographic location. As a non-profit IXP, our policy exists to serve the community — not to restrict it.
Only send us traffic destined for the routes we announce to you.
Do not point default routes to us for traffic that does not match the routes we announce.
Only send us traffic originating from your own networks, including downstreams.
You must operate a Network Operations Center (NOC) reachable at any time.
We recommend that peers set a max-prefix limit based upon the listed values in our PeeringDB entry on sessions approved by us.
We apply max-prefix filters on all peering sessions. Prefixes matching any of the following conditions will be discarded automatically.
packet:IX operates two redundant route servers. We recommend peering with both to ensure resilience. Route server sessions use BGP communities for traffic engineering.
103.152.36.2532406:1b80:4010::253103.152.36.2542406:1b80:4010::254Route Server ASN
AS137786Use this ASN when configuring your BGP neighbor statements for the route servers.
Our complete network information, including current prefix limits, contact details, and facility information, is maintained on PeeringDB. Always refer to our PeeringDB entry for the most up-to-date operational data.
View on PeeringDB