ixreport

AT TOKYO Corporation

AS9999

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
RestrictivePeering policy
2Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with AT TOKYO Corporation? · Where should AT TOKYO Corporation peer next? · Compare AT TOKYO Corporation with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in AT TOKYO Corporation's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

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

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::270f:0:1
    • In the entry with IPv4 80.81.196.75: set IPv6 to 2001:7f8::270f:0:1 (now empty).

Exchanges over time

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

Map

Where AT TOKYO Corporation'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 40G across 4 exchanges.

Japan BBIX Tokyo Tokyo, Japan 101.203.88.186 2001:de8:c::9999:1 10G Yes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.196.75 10G Down Both IPv6 not in PeeringDB
Japan JPIX TOKYO Tokyo, Japan 210.171.224.146 10G Both
Japan JPNAP Tokyo Tokyo, Japan 210.173.176.247 2001:7fa:7:1::9999:1 10G PeeringDB

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

These exchanges have a switch in a facility where AT TOKYO Corporation lists itself in PeeringDB, but don't have AT TOKYO Corporation 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 AT TOKYO (CC1/CC2)
Japan Japan Community IXJapan, Japan 32 AT TOKYO (CC1/CC2)
Japan Japan Community IX - INIXPJapan, Japan 15 AT TOKYO (CC1/CC2)
Facilities (1)

The buildings AT TOKYO Corporation lists in PeeringDB, and how many of the exchanges in each it's on.

Japan AT TOKYO (CC1/CC2)Tokyo 3 of 6