Netflix: PeeringDB fix list
AS2906 · peeringdb.com/net/457
11 things to fix in Netflix's PeeringDB record, from what its exchanges publish: 7 to add, 4 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on Netflix'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 (7)
On the exchange's own member list, but not in Netflix's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 185.1.186.7 IPv6 2001:7f8:101:7::7 Speed 80000 Mbps (80G) RS peer No -
IPv4 195.69.119.43 IPv6 2001:7f8:d:fb::43 Speed Not published RS peer Yes -
IPv4 195.245.240.43 IPv6 2001:7f8:d:fc::43 Speed Not published RS peer Yes -
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
2 connections, so 2 entries:
IPv4 193.239.117.54 IPv6 2001:7f8:13::a500:2906:1 Speed Not published RS peer Yes IPv4 193.239.118.79 IPv6 2001:7f8:13::a500:2906:2 Speed Not published RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (4)
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 2 × 200G 200G + 100G - In the entry with IPv4 89.46.145.207: set Speed to 100000 (100G) (now 200000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 196.223.21.119 196.223.21.120 196.223.21.119 IPv6 address in PeeringDB, not in the export 2001:43f8:60:1::119 2001:43f8:60:1::120 2001:43f8:60:1::119 - The entry with IPv4 196.223.21.120, IPv6 2001:43f8:60:1::120 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 200G - In the entry with IPv4 193.201.28.76: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 193.201.28.94: set Speed to 200000 (200G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 2 × 30G 2 × 100G - In the entry with IPv4 198.32.195.56: set Speed to 100000 (100G) (now 30000).
- In the entry with IPv4 198.32.195.66: set Speed to 100000 (100G) (now 30000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/2906/: 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.