Critical Core: PeeringDB fix list
AS49033 · peeringdb.com/net/18330
3 things to fix in Critical Core's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-10-08 20:58 UTC.
Make the changes on Critical Core'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 (3)
On the exchange's own member list, but not in Critical Core's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From 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.
-
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.
From ixreport.com/net/49033/: 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.