asn.dev

Internet exchange

Japan Community IX - INIXP

active Tokyo, Japan

Recorded members 33 addresses on file
Connected ports 16 across all participants
Peak traffic Not reported no figure on file
Peering LANs 2 shared subnets

Overview

What this is

recorded

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
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

2 on file

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.

PrefixFamilyStatusParticipants
103.115.3.0/25IPv4Active14
2401:3fa0::/64IPv6Active16

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

33 shown

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. One row per recorded address, so a network running dual-stack appears once for its IPv4 interface and once for its IPv6 one.

ASNetworkAddressrDNSPolicy
AS6939Hurricane Electric LLC2401:3fa0::6939:16939.as.inixp.ioOpen
AS6939Hurricane Electric LLC103.115.3.136939.as.inixp.ioOpen
AS13335Cloudflare, Inc.103.115.3.2013335.as.inixp.ioOpen
AS13335Cloudflare, Inc.2401:3fa0::1:3335:113335.as.inixp.ioOpen
AS42WoodyNet, Inc.2401:3fa0::42:1Open
AS42WoodyNet, Inc.103.115.3.25Open
AS3856Packet Clearing House, Inc.103.115.3.26Open
AS3856Packet Clearing House, Inc.2401:3fa0::3856:1Open
AS112DNS-OARC103.115.3.12112.as.inixp.ioOpen
AS112DNS-OARC2401:3fa0::112:1Open
AS150369TelHi Corporation103.115.3.22Selective
AS150369TelHi Corporation2401:3fa0::15:369:1Selective
AS205329Kai-Jung Chen2401:3fa0::20:5329:1Open
AS205329Kai-Jung Chen103.115.3.16205329.as.inixp.ioOpen
AS63800SERVER-G Group2401:3fa0::6:3800:163800.as.inixp.ioOpen
AS63800SERVER-G Group103.115.3.763800.as.inixp.ioOpen
AS150325TSUKUDANI NETWORK103.115.3.21Open
AS150325TSUKUDANI NETWORK2401:3fa0::15:325:1Open
AS38656Loutres103.115.3.27Open
AS38656Loutres2401:3fa0::3:8656:2Open
AS38656Loutres2401:3fa0::3:8656:1Open
AS59098Mamireimu Net Work's2401:3fa0::5:9098:159098.as.inixp.ioOpen
AS59098Mamireimu Net Work's103.115.3.8150362.as.inixp.ioOpen
AS150368SERVER-G Group2401:3fa0::15:368:1Open
AS58790SERVER-G Group103.115.3.23No
AS58790SERVER-G Group2401:3fa0::5:8790:1No
AS152184Tamukai Network103.115.3.29Open
AS152184Tamukai Network2401:3fa0::15:2184:1Open
AS9928RAPID-FIRE-Y2401:3fa0::9928:29928.as.inixp.ioSelective
AS9928RAPID-FIRE-Y2401:3fa0::9928:19928.as.inixp.ioSelective
AS9928RAPID-FIRE-Y103.115.3.2rs2.as.inixp.ioSelective
AS9928RAPID-FIRE-Y103.115.3.1rs1.as.inixp.ioSelective
AS44817M Alhuda2401:3fa0::4:4817:1Open

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

Exchange records come from the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 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.