LeaderTelecom: PeeringDB fix list
AS58272 · peeringdb.com/net/28408
2 things to fix in LeaderTelecom's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.
Make the changes on LeaderTelecom'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 (2)
On the exchange's own member list, but not in LeaderTelecom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.249.215.9 IPv6 2001:7f8:1::a505:8272:1 Speed 10000 Mbps (10G) 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.
-
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 listIPv4 193.239.116.172 IPv6 2001:7f8:13::a505:8272:1 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.
From ixreport.com/net/58272/: 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.