ixreport

WANSEC

AS1421 · WANSIX

WANSecurity, Inc.

2Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
6Facilities in PeeringDB

Tools: Where can I peer with WANSEC? · Where should WANSEC peer next? · Compare WANSEC with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on WANSEC'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. United States KCIX Kansas City, United States · PeeringDB 249
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.51.7.4206.51.7.4 206.51.7.222
    IPv6 address missing from PeeringDB2001:504:1b:1::42001:504:1b:1::4 2001:504:1b:1::222
    • Add an entry: IPv4 206.51.7.222, IPv6 2001:504:1b:1::222, speed 10000 (10G).

Exchanges over time

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

Map

Where WANSEC'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

Japan Equinix Tokyo Tokyo, Japan 203.190.230.52 2001:de8:5::1421:1 Yes PeeringDB
United States KCIX Kansas City, United States 206.51.7.4 2001:504:1b:1::4 Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

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

These exchanges have a switch in a facility where WANSEC lists itself in PeeringDB, but don't have WANSEC 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.

Germany DE-CIX MunichMunich, Germany 207 Equinix MU1/MU3 - Munich
Bulgaria NetIXSofia, Bulgaria 204 Equinix TY1 - Tokyo; Netrality Kansas City - 1102 Grand
United States SFMIXSan Francisco, United States 100 Digital Realty SFO (200 Paul)
Germany MegaIX MunichMunich, Germany 35 Equinix MU1/MU3 - Munich
United States Global Peer ExchangeWashington, United States 6 Digital Realty SFO (200 Paul)
Facilities (6)

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

United States Digital Realty SFO (200 Paul)San Francisco 0 of 2
Germany Equinix MU1/MU3 - MunichMunich 0 of 2
Japan Equinix TY1 - TokyoTokyo 1 of 2
United States Netrality Kansas City - 1102 GrandKansas City 1 of 2
United States Crown Castle Los Angeles (624 S Grand)Los Angeles No exchange
United States DataBank Kansas City (MCI2)Overland Park No exchange