Securebit [Europe]: PeeringDB fix list
AS34800 · peeringdb.com/net/21081
3 things to fix in Securebit [Europe]'s PeeringDB record, from what its exchanges publish: 2 to correct, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.
Make the changes on Securebit [Europe]'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 IPv4 address in PeeringDB, not in the export 185.1.170.130 185.1.171.8 185.1.171.8 IPv6 address in PeeringDB, not in the export 2001:7f8:9e::87f0:0:1 2001:7f8:9e::87f0:0:2 2001:7f8:9e::87f0:0:2 Port speed differs 2 × 1G 10G - The entry with IPv4 185.1.170.130, IPv6 2001:7f8:9e::87f0:0:1 isn't in the export: delete it if that connection is gone.
- In the entry with IPv4 185.1.171.8: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.210.192: set Speed to 10000 (10G) (now 1000).
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only the operator's own networks
IPv4 149.202.236.7 IPv6 2001:7f8:d9:8::87f0:1 Speed 1000 Mbps (1G)
From ixreport.com/net/34800/: 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.