ixreport

Ninja-Cache

AS12233

Ninja-IX Corporation

8Exchanges
1On an exchange's list, not in PeeringDB
2In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
5Using the route servers
8To fix in PeeringDB
9Facilities in PeeringDB

Tools: Where can I peer with Ninja-Cache? · Where should Ninja-Cache peer next? · Compare Ninja-Cache with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

8 things to fix in Ninja-Cache's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct, 2 to check. As of 2026-11-19 12:40 UTC.

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

Add these exchanges (1)

On the exchange's own member list, but not in Ninja-Cache's PeeringDB record. Add one entry per connection with these values.

  1. United States FREMIX Fremont, United States · PeeringDB 3685From its website members list
    IPv4149.112.29.92
    IPv62001:504:125:e0::92
    SpeedNot published
    RS peerNot published

Correct these entries (5)

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 Bay Area Northern California, United States · PeeringDB 3973
    ProblemPeeringDB hasThe export has
    Port speed differs200G400G
    • In the entry with IPv4 149.112.34.8: set Speed to 400000 (400G) (now 200000).
  2. United States Ninja-IX Dallas Dallas, United States · PeeringDB 2318
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:504:75::8none
    • In the entry with IPv4 206.71.139.8: set IPv6 to (empty) (now 2001:504:75::8).
  3. United States Ninja-IX Las Vegas Las Vegas, United States · PeeringDB 1488
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:504:68::8none
    • In the entry with IPv4 206.71.8.8: set IPv6 to (empty) (now 2001:504:68::8).
  4. United States Ninja-IX Phoenix Phoenix, United States · PeeringDB 662
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.41.105.8 206.41.105.108206.41.105.8 206.41.105.107 206.41.105.108
    IPv6 address missing from PeeringDB2001:504:3b::8 2001:504:3b::1082001:504:3b::8 2001:504:3b::107 2001:504:3b::108
    Port speed differs2 × 200G300G + 2 × 200G
    • In the entry with IPv4 206.41.105.108: set Speed to 300000 (300G) (now 200000).
    • Add an entry: IPv4 206.41.105.107, IPv6 2001:504:3b::107, speed 200000 (200G), RS peer yes.
  5. United States Ninja-IX Richmond Richmond, United States · PeeringDB 1490
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:504:79::8none
    • In the entry with IPv4 206.71.9.8: set IPv6 to (empty) (now 2001:504:79::8).

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Ninja-Cache has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United States Ninja-IX Auburn Auburn, United States · PeeringDB 3974Not on its IX-F export
    IPv4149.112.25.8
    IPv62001:504:115::8
    Speed80000 Mbps (80G)
  2. United States Ninja-IX Sacramento Sacramento, United States · PeeringDB 2032Not on its IX-F export
    IPv4206.71.13.8
    IPv62001:504:70::8
    Speed80000 Mbps (80G)

Exchanges over time

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

In the last 30 days Ninja-Cache joined 1 exchange and left 0. Growing networks

Joined

Map

Where Ninja-Cache'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, at the 7 of 8 exchanges with a speed in PeeringDB or the exchange's IX-F export.

United States FREMIX Fremont, United States 149.112.29.92 2001:504:125:e0::92 Not in PeeringDB
United States Ninja-IX Auburn Auburn, United States 149.112.25.8 2001:504:115::8 80G PeeringDB only
United States Ninja-IX Bay Area Northern California, United States 149.112.34.8 2001:504:119::8 200G Yes Both Speed differs
United States Ninja-IX Dallas Dallas, United States 206.71.139.8 2001:504:75::8 80G 1 routes Both IPv6 not in export
United States Ninja-IX Las Vegas Las Vegas, United States 206.71.8.8 2001:504:68::8 80G Up, 0 routes Both IPv6 not in export
United States Ninja-IX Phoenix Phoenix, United States 206.41.105.8
206.41.105.108
2001:504:3b::8
2001:504:3b::108
2 × 200G 3 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
United States Ninja-IX Richmond Richmond, United States 206.71.9.8 2001:504:79::8 80G 1 routes Both IPv6 not in export
United States Ninja-IX Sacramento Sacramento, United States 206.71.13.8 2001:504:70::8 80G PeeringDB only

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

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

United States EVIXFremont, United States 227 Hurricane Electric Fremont 2
United States FCIXFremont, United States 187 Hurricane Electric Fremont 2
United States DE-CIX DallasDallas, United States 177 QTS Irving - Dallas (DFW1)
United States SFMIXSan Francisco, United States 100 Hurricane Electric Fremont 2
United States MegaIX AshburnAshburn, United States 49 QTS Richmond (RIC1)
United States DE-CIX PhoenixPhoenix, United States 41 PhoenixNAP; EdgeConneX Phoenix (EDCPHX01)
Puerto Rico PR-IXSan Juan, Puerto Rico 33 Hurricane Electric Fremont 2
United States MegaIX DallasDallas, United States 30 QTS Irving - Dallas (DFW1)
United States DE-CIX RichmondAshland, United States 23 QTS Richmond (RIC1)
United States ARIXFremont, Portland, Flagstaff, United States 22 Hurricane Electric Fremont 2
United States Lambda-IXFremont, United States 22 Hurricane Electric Fremont 2
United States MegaIX Bay AreaSan Francisco, United States 21 Hurricane Electric Fremont 2
United States Zero Internet eXchange San JoseSan Jose, United States 15 Hurricane Electric Fremont 2
United States DACS-IX WestSilicon Valley, United States 14 Hurricane Electric Fremont 2
United States Global Peer ExchangeWashington, United States 6 PhoenixNAP
United States 48 IXPhoenix, United States 5 EdgeConneX Phoenix (EDCPHX01)
Australia ixFabricGlobal, Australia 2 Hurricane Electric Fremont 2
Facilities (9)

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

United States Hurricane Electric Fremont 2Fremont 2 of 12
United States EdgeConneX Phoenix (EDCPHX01)Tempe 1 of 3
United States PhoenixNAPPhoenix 1 of 3
United States QTS Irving - Dallas (DFW1)Irving 1 of 3
United States QTS Richmond (RIC1)Sandston 1 of 3
United States 1GServers Data Center PHX1Phoenix 1 of 1
United States AUBix AuburnAuburn 1 of 1
United States EdgeConneX Las Vegas (EDCLAS01)Las Vegas 1 of 1
United States QTS Sacramento (SAC1)Sacramento 1 of 1

Recent changes Search them

  • Oct 31, 2026 [WEB] AS12233 Ninja-Cache added to FREMIX