Ninja-Cache: PeeringDB fix list

AS12233 · peeringdb.com/net/27953

7 things to fix in Ninja-Cache's PeeringDB record, from what its exchanges publish: 5 to correct, 2 to check. As of 2026-10-08 22:13 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.

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.

Ninja-IX Bay Area Northern California, United States · PeeringDB 3973

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).
Ninja-IX Dallas Dallas, United States · PeeringDB 2318

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).
Ninja-IX Las Vegas Las Vegas, United States · PeeringDB 1488

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
Port speed differs	200G	400G

Problem	PeeringDB has	The export has
IPv6 address in PeeringDB, not in the export	2001:504:75::8	none

Problem	PeeringDB has	The export has
IPv6 address in PeeringDB, not in the export	2001:504:68::8	none

Ninja-IX Phoenix Phoenix, United States · PeeringDB 662

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

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.

Ninja-IX Richmond Richmond, United States · PeeringDB 1490

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).

Problem	PeeringDB has	The export has
IPv6 address in PeeringDB, not in the export	2001:504:79::8	none

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.

Ninja-IX Auburn Auburn, United States · PeeringDB 3974Not on its IX-F export

IPv4 149.112.25.8

IPv6 2001:504:115::8

Speed 80000 Mbps (80G)
Ninja-IX Sacramento Sacramento, United States · PeeringDB 2032Not on its IX-F export

IPv4 206.71.13.8

IPv6 2001:504:70::8

Speed 80000 Mbps (80G)

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)

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