Ericsson Broadcast Services Netherlands: PeeringDB fix list
AS20969 · peeringdb.com/net/1366
2 things to fix in Ericsson Broadcast Services Netherlands's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Ericsson Broadcast Services Netherlands'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:1::a502:969:1 2001:7f8:1::a502:969:2 Port speed differs 10G + 1G 2 × 10G - In the entry with IPv4 80.249.209.227: set IPv6 to 2001:7f8:1::a502:969:2 (now empty); set Speed to 10000 (10G) (now 1000).
- In the entry with IPv4 80.249.211.148: set IPv6 to 2001:7f8:1::a502:969:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.239.116.63 193.239.116.63 193.239.116.75 IPv6 address missing from PeeringDB none 2001:7f8:13::a502:969:1 2001:7f8:13::a502:969:2 - In the entry with IPv4 193.239.116.63: set IPv6 to 2001:7f8:13::a502:969:1 (now empty).
- Add an entry: IPv4 193.239.116.75, IPv6 2001:7f8:13::a502:969:2, RS peer no.
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/20969/: 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.