ixreport

NTT PC Communications (InfoSphere)

AS2514 · InfoSphere

6Exchanges
0On an exchange's list, not in PeeringDB
1In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
0Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with NTT PC Communications (InfoSphere)? · Where should NTT PC Communications (InfoSphere) peer next? · Compare NTT PC Communications (InfoSphere) with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in NTT PC Communications (InfoSphere)'s PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on NTT PC Communications (InfoSphere)'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 NTT PC Communications (InfoSphere) has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.90.67
    IPv62001:de8:c::2514:1
    Speed100000 Mbps (100G)

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

Exchanges over time

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

Map

Where NTT PC Communications (InfoSphere)'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 1T across 6 exchanges.

Japan BBIX Tokyo Tokyo, Japan 101.203.90.67 2001:de8:c::2514:1 100G PeeringDB only
Japan Equinix Tokyo Tokyo, Japan 203.190.230.62
203.190.230.138
2001:de8:5::2514:1
2001:de8:5::2514:2
2 × 100G PeeringDB
Japan JPIX OSAKA Osaka, Japan 103.246.232.37 2001:de8:8:6::2514:1 100G PeeringDB
Japan JPIX TOKYO Tokyo, Japan 210.171.224.38
210.171.225.138
2001:de8:8::2514:1
2001:de8:8::2514:2
2 × 100G Both
Japan JPNAP Osaka Osaka, Japan 210.173.184.37
210.173.184.52
2001:7fa:7:2::2514:1
2001:7fa:7:2::2514:2
2 × 100G PeeringDB
Japan JPNAP Tokyo Tokyo, Japan 210.173.176.18
210.173.176.37
2001:7fa:7:1::2514:1
2001:7fa:7:1::2514:2
2 × 100G PeeringDB

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

These exchanges have a switch in a facility where NTT PC Communications (InfoSphere) lists itself in PeeringDB, but don't have NTT PC Communications (InfoSphere) 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 TY4 - Tokyo
Japan BBIX OsakaOsaka, Japan 130 NTT DATA Dojima (building #4)
Japan DIX-IETokyo, Japan 22 Telehouse – TOKYO Otemachi (KDDI Otemachi)
Japan MegaIX OsakaOsaka, Japan 5 NTT DATA Dojima (building #4)
Facilities (3)

The buildings NTT PC Communications (InfoSphere) lists in PeeringDB, and how many of the exchanges in each it's on.

Japan Equinix TY4 - TokyoTokyo 4 of 5
Japan NTT DATA Dojima (building #4)Osaka 2 of 4
Japan Telehouse – TOKYO Otemachi (KDDI Otemachi)Tokyo 1 of 2