Ninja-Cache
AS12233
Ninja-IX Corporation
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.
-
IPv4 149.112.29.92 IPv6 2001:504:125:e0::92 Speed Not published RS peer Not 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.
-
Problem PeeringDB has The export has Port speed differs 200G 400G - In the entry with IPv4 149.112.34.8: set Speed to 400000 (400G) (now 200000).
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:504:75::8 none - In the entry with IPv4 206.71.139.8: set IPv6 to (empty) (now 2001:504:75::8).
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:504:68::8 none - In the entry with IPv4 206.71.8.8: set IPv6 to (empty) (now 2001:504:68::8).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.41.105.8 206.41.105.108 206.41.105.8 206.41.105.107 206.41.105.108 IPv6 address missing from PeeringDB 2001:504:3b::8 2001:504:3b::108 2001:504:3b::8 2001:504:3b::107 2001:504:3b::108 Port speed differs 2 × 200G 300G + 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.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:504:79::8 none - 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.
-
IPv4 149.112.25.8 IPv6 2001:504:115::8 Speed 80000 Mbps (80G) -
IPv4 206.71.13.8 IPv6 2001:504:70::8 Speed 80000 Mbps (80G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 7 |
| Nov 15, 2026 | 7 |
| Nov 14, 2026 | 7 |
| Nov 13, 2026 | 7 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 7 |
| Oct 29, 2026 | 7 |
| Oct 28, 2026 | 7 |
| Oct 27, 2026 | 7 |
| Oct 26, 2026 | 7 |
| Oct 25, 2026 | 7 |
| Oct 24, 2026 | 7 |
| Oct 23, 2026 | 7 |
| Oct 22, 2026 | 7 |
| Oct 21, 2026 | 7 |
| Oct 20, 2026 | 7 |
| Oct 19, 2026 | 7 |
| Oct 18, 2026 | 7 |
| Oct 17, 2026 | 7 |
| Oct 16, 2026 | 7 |
| Oct 15, 2026 | 7 |
| Oct 14, 2026 | 7 |
| Oct 13, 2026 | 7 |
| Oct 12, 2026 | 7 |
| Oct 11, 2026 | 7 |
| Oct 10, 2026 | 7 |
| Oct 9, 2026 | 7 |
| Oct 8, 2026 | 7 |
| Oct 7, 2026 | 7 |
| Oct 6, 2026 | 7 |
| Oct 5, 2026 | 7 |
| Oct 4, 2026 | 7 |
| Oct 3, 2026 | 7 |
In the last 30 days Ninja-Cache joined 1 exchange and left 0. Growing networks
Joined
- FREMIX Fremont Oct 31, 2026
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.
| FREMIX Fremont, United States | Not in PeeringDB | ||
| Ninja-IX Auburn Auburn, United States | 80G | PeeringDB only | |
| Ninja-IX Bay Area Northern California, United States | 200G | Both Speed differs | |
| Ninja-IX Dallas Dallas, United States | 80G | Both IPv6 not in export | |
| Ninja-IX Las Vegas Las Vegas, United States | 80G | Both IPv6 not in export | |
| Ninja-IX Phoenix Phoenix, United States | 2 × 200G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| Ninja-IX Richmond Richmond, United States | 80G | Both IPv6 not in export | |
| Ninja-IX Sacramento Sacramento, United States | 80G | PeeringDB only |
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.
| EVIXFremont, United States | 227 | |
| FCIXFremont, United States | 187 | |
| DE-CIX DallasDallas, United States | 177 | |
| SFMIXSan Francisco, United States | 100 | |
| MegaIX AshburnAshburn, United States | 49 | |
| DE-CIX PhoenixPhoenix, United States | 41 | |
| PR-IXSan Juan, Puerto Rico | 33 | |
| MegaIX DallasDallas, United States | 30 | |
| DE-CIX RichmondAshland, United States | 23 | |
| ARIXFremont, Portland, Flagstaff, United States | 22 | |
| Lambda-IXFremont, United States | 22 | |
| MegaIX Bay AreaSan Francisco, United States | 21 | |
| Zero Internet eXchange San JoseSan Jose, United States | 15 | |
| DACS-IX WestSilicon Valley, United States | 14 | |
| Global Peer ExchangeWashington, United States | 6 | |
| 48 IXPhoenix, United States | 5 | |
| ixFabricGlobal, Australia | 2 |
Facilities (9)
The buildings Ninja-Cache lists in PeeringDB, and how many of the exchanges in each it's on.
| Hurricane Electric Fremont 2Fremont | 2 of 12 | |
| EdgeConneX Phoenix (EDCPHX01)Tempe | 1 of 3 | |
| PhoenixNAPPhoenix | 1 of 3 | |
| QTS Irving - Dallas (DFW1)Irving | 1 of 3 | |
| QTS Richmond (RIC1)Sandston | 1 of 3 | |
| 1GServers Data Center PHX1Phoenix | 1 of 1 | |
| AUBix AuburnAuburn | 1 of 1 | |
| EdgeConneX Las Vegas (EDCLAS01)Las Vegas | 1 of 1 | |
| QTS Sacramento (SAC1)Sacramento | 1 of 1 |
Recent changes Search them
- Oct 31, 2026 [WEB] AS12233 Ninja-Cache added to FREMIX