215248 - Bastiaan Mathijs Brink: PeeringDB fix list
AS215248 · peeringdb.com/net/36405
17 things to fix in 215248 - Bastiaan Mathijs Brink's PeeringDB record, from what its exchanges publish: 1 to add, 13 to correct, 1 to check, 2 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on 215248 - Bastiaan Mathijs Brink'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 215248 - Bastiaan Mathijs Brink's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (13)
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 Port speed differs 100M 200G - In the entry with IPv4 80.81.196.210: set Speed to 200000 (200G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.1.240.56: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G + 2 × 1G 3 × 1G - In the entry with IPv4 206.81.104.182: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 40G 1G - In the entry with IPv4 149.112.75.50: set Speed to 1000 (1G) (now 40000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100G 10G - In the entry with IPv4 185.1.147.122: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 25G 10G - In the entry with IPv4 178.18.236.70: set Speed to 10000 (10G) (now 25000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 40G 10G - In the entry with IPv4 206.83.136.65: set Speed to 10000 (10G) (now 40000).
-
Problem PeeringDB has The export has Port speed differs 40G 10G - In the entry with IPv4 206.51.7.127: set Speed to 10000 (10G) (now 40000).
-
Problem PeeringDB has The export has IPv4 address in PeeringDB, not in the export 195.66.236.118 195.66.237.1 195.66.237.1 IPv6 address in PeeringDB, not in the export 2001:7f8:4:1:0:3:48d0:1 2001:7f8:4:1:0:3:48d0:2 2001:7f8:4:1:0:3:48d0:2 Port speed differs 2 × 2G 2G - The entry with IPv4 195.66.236.118, IPv6 2001:7f8:4:1:0:3:48d0:1 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 149.112.50.52: set Speed to 1000 (1G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 40G 10G - In the entry with IPv4 149.112.4.20: set Speed to 10000 (10G) (now 40000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 40G 10G - In the entry with IPv4 206.83.12.97: set Speed to 10000 (10G) (now 40000).
-
Problem PeeringDB has The export has Port speed differs 1G 100G - In the entry with IPv4 91.206.53.36: set Speed to 100000 (100G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If 215248 - Bastiaan Mathijs Brink has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
IPv4 195.66.244.32 IPv6 2001:7f8:4:2:0:3:48d0:1 Speed 2000 Mbps (2G)
Exchanges that look shut down (2)
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 one outside network
IPv4 91.213.73.21 IPv6 2001:7f8:174::21 Speed 100000 Mbps (100G) -
Only one outside network
IPv4 31.56.97.3 IPv6 2a06:9f44:d000:79::3 Speed 10000 Mbps (10G)
From ixreport.com/net/215248/: 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.