ixreport

JPIX AS24257: PeeringDB fix list

AS24257 · peeringdb.com/net/23229

PeeringDB

One thing to fix in JPIX AS24257's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on JPIX AS24257's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If JPIX AS24257 has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30Not on its website members list
    IPv4210.171.224.15
    IPv62001:de8:8::2:4257:1
    Speed100000 Mbps (100G)
    IPv4210.171.224.16
    IPv62001:de8:8::2:4257:2
    Speed100000 Mbps (100G)
    IPv4210.171.225.14
    IPv62001:de8:8::2:4257:21
    Speed100000 Mbps (100G)
    IPv4210.171.225.15
    IPv62001:de8:8::2:4257:22
    Speed100000 Mbps (100G)
    IPv4210.171.225.244
    IPv62001:de8:8::2:4257:11
    Speed300000 Mbps (300G)
    IPv4210.171.225.245
    IPv62001:de8:8::2:4257:12
    Speed300000 Mbps (300G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

From ixreport.com/net/24257/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.