Internet exchange
INIXP Asia
active Tokyo, Japan NRT
Overview
What this is
An internet exchange is shared switching where networks interconnect directly instead of paying a transit provider to carry traffic between them. Members take a port on the fabric and an address on the peering LANs below, then agree bilaterally (or through a route server) about which routes to exchange. Turning up at one is a deliberate choice about how a network wants to be reached, which is why exchange presence says something a routing table cannot.
- Location
- Tokyo, Japan
- Region
- Asia-Pacific
- Airport code
NRT- Status
- Active
Everything on this page is what Packet Clearing House had recorded when the directory was collected, not a live view of the fabric. Member counts in particular lag reality, and around 45% of the exchanges in this dataset publish no participant list at all.
Fabric
Peering LANs
The shared subnets members take an address on. A network with an interface in one of these blocks is at this exchange by definition, which is what makes exchange presence a recorded fact rather than an inference. Most exchanges run one IPv4 and one IPv6 LAN; extra blocks are usually growth or a migration.
| Prefix | Family | Status | Participants |
|---|---|---|---|
| 103.115.3.0/24 | IPv4 | Active | 13 |
| 2401:3fa0::/64 | IPv6 | Active | 11 |
Deprecated and retired blocks are listed rather than dropped. A decommissioned LAN still records how this fabric used to be reached, and filtering it would quietly rewrite the exchange's history.
Participants
Member networks
Every network PCH records with an address on one of the peering LANs above, ordered as the source ranks them: the most-connected participants first. Each network's addresses on the fabric are listed together, IPv4 first. Typing in the box narrows the rows below; Search looks through all 31 recorded addresses.
| AS | Network | Addresses | rDNS | Policy |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | 103.115.3.132401:3fa0::6939:1 | 6939.as.inixp.io6939.as.inixp.io | Open |
| AS13335 | Cloudflare, Inc. | 103.115.3.202401:3fa0::1:3335:1 | 13335.as.inixp.io13335.as.inixp.io | Open |
| AS42 | WoodyNet, Inc. | 103.115.3.252401:3fa0::42:1 | —— | Open |
| AS3856 | Packet Clearing House, Inc. | 103.115.3.262401:3fa0::3856:1 | —— | Open |
| AS112 | DNS-OARC | 103.115.3.122401:3fa0::112:1 | 112.as.inixp.io— | Open |
| AS150369 | TelHi Corporation | 103.115.3.222401:3fa0::15:369:1 | —— | Selective |
| AS63800 | SERVER-G Group | 103.115.3.72401:3fa0::6:3800:1 | 63800.as.inixp.io63800.as.inixp.io | Open |
| AS150325 | TSUKUDANI NETWORK | 103.115.3.212401:3fa0::15:325:1 | —— | Open |
| AS38656 | Loutres | 103.115.3.272401:3fa0::3:8656:12401:3fa0::3:8656:2 | ——— | Open |
| AS59098 | Mamireimu Net Work's | 103.115.3.82401:3fa0::5:9098:1 | 150362.as.inixp.io59098.as.inixp.io | Open |
| AS150368 | SERVER-G Group | 2401:3fa0::15:368:1 | — | Open |
| AS58790 | SERVER-G Group | 103.115.3.232401:3fa0::5:8790:1 | —— | No |
| AS152184 | Tamukai Network | 103.115.3.292401:3fa0::15:2184:1 | —— | Open |
| AS9928 | RAPID-FIRE-Y | 103.115.3.2103.115.3.12401:3fa0::9928:22401:3fa0::9928:1 | rs2.as.inixp.iors1.as.inixp.io9928.as.inixp.io9928.as.inixp.io | Selective |
| AS44817 | M Alhuda | 2401:3fa0::4:4817:1 | — | Open |
Peering policy is what the network declared to PCH, not something anyone verified, and an open policy is an invitation rather than a commitment. Absence of a network here means PCH has no record of it at this exchange, not that it is not present.
Provenance
Where this comes from
- Full record at Packet Clearing House — the upstream this page is built from, with the traffic graphs and the complete participant list.
- The exchange's own site — joining terms, port pricing and the route servers, which no directory carries.
Exchange records come from the directory collected 2026-10-14 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,276 recorded member addresses, licensed CC BY-NC-SA 3.0.
This is a snapshot, not a live view. Members join and leave continuously, and the figures above are what PCH had on file on the collection date. PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.