ixreport

Ninja-IX Corporation: PeeringDB fix list

AS53698 · peeringdb.com/net/5354

PeeringDB

4 things to fix in Ninja-IX Corporation's PeeringDB record, from what its exchanges publish: 2 to correct, 2 at exchanges that look shut down. As of 2026-10-08 21:56 UTC.

Make the changes on Ninja-IX 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 (2)

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 Ninja-IX Las Vegas Las Vegas, United States · PeeringDB 1488
    ProblemPeeringDB hasThe export has
    Port speed differs100G10G
    • In the entry with IPv4 206.71.8.9: set Speed to 10000 (10G) (now 100000).
  2. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    Port speed differs200G40G
    • In the entry with IPv4 206.41.105.9: set Speed to 40000 (40G) (now 200000).

Exchanges that look shut down (2)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. United States Ninja-IX Houstonghost Houston, United States · PeeringDB 2319

    Only the operator's own networks

    IPv4206.71.138.9
    IPv62001:504:74::9
    Speed10000 Mbps (10G)
  2. United States Ninja-IX Norfolkghost Norfolk, United States · PeeringDB 3761

    Only the operator's own networks

    IPv4149.112.14.9
    IPv62001:504:106::9
    Speed10000 Mbps (10G)

From ixreport.com/net/53698/: 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.