PREMIUMDN: PeeringDB fix list
AS213899 · peeringdb.com/net/37810
One thing to fix in PREMIUMDN's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 22:13 UTC.
Make the changes on PREMIUMDN'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 (1)
On the exchange's own member list, but not in PREMIUMDN's PeeringDB record. Add one entry per connection with these values.
-
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
IPv4 193.239.119.250 IPv6 2001:7f8:13::a521:3899: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/213899/: 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.