SBS Broadcasting B.V.: PeeringDB fix list
AS50072 · peeringdb.com/net/3337
2 things to fix in SBS Broadcasting B.V.'s PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on SBS Broadcasting B.V.'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::a505:72:1 - In the entry with IPv4 80.249.209.108: set IPv6 to 2001:7f8:1::a505:72: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.117.238 193.239.117.239 193.239.116.138 193.239.116.246 193.239.117.238 193.239.117.239 IPv6 address missing from PeeringDB none 2001:7f8:13::a505:72:1 2001:7f8:13::a505:72:2 - Add an entry: IPv4 193.239.116.138, IPv6 2001:7f8:13::a505:72:2, RS peer yes.
- Add an entry: IPv4 193.239.116.246, IPv6 2001:7f8:13::a505:72:1, 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.
From ixreport.com/net/50072/: 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.