ixreport

KDDI Web Communications

AS9597 · KWC

KDDI Web Communications Inc.

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
SelectivePeering policy
3Using the route servers
2Facilities in PeeringDB

Tools: Where can I peer with KDDI Web Communications? · Where should KDDI Web Communications peer next? · Compare KDDI Web Communications with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list

Nothing to fix: KDDI Web Communications's PeeringDB record matches the member lists of the 2 exchanges we could compare (the others publish no list we could read).

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where KDDI Web Communications's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 60G across 3 exchanges.

Japan BBIX Tokyo Tokyo, Japan 101.203.90.127
101.203.90.128
2001:de8:c::9597:1
2001:de8:c::9597:2
2 × 10G Yes Both
Japan JPIX TOKYO Tokyo, Japan 210.171.225.110
210.171.225.111
2001:de8:8::9597:1
2001:de8:8::9597:2
2 × 10G Yes Both
Japan JPNAP Tokyo Tokyo, Japan 210.173.177.133
210.173.177.134
2001:7fa:7:1::9597:1
2001:7fa:7:1::9597:2
2 × 10G Yes PeeringDB

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where KDDI Web Communications lists itself in PeeringDB, but don't have KDDI Web Communications as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Bulgaria NetIXSofia, Bulgaria 204 Equinix TY2 - Tokyo; Equinix TY4 - Tokyo
Japan Equinix TokyoTokyo, Japan 127 Equinix TY2 - Tokyo; Equinix TY4 - Tokyo
United States Global Peer ExchangeWashington, United States 6 Equinix TY2 - Tokyo
Facilities (2)

The buildings KDDI Web Communications lists in PeeringDB, and how many of the exchanges in each it's on.

Japan Equinix TY2 - TokyoTokyo 3 of 6
Japan Equinix TY4 - TokyoTokyo 3 of 5