M247 Global: PeeringDB fix list
AS9009 · peeringdb.com/net/601
13 things to fix in M247 Global's PeeringDB record, from what its exchanges publish: 2 to add, 11 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on M247 Global'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 M247 Global'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.
-
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 (11)
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 10G 100G - In the entry with IPv4 193.242.98.132: set Speed to 100000 (100G) (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 10G 100G - In the entry with IPv4 206.53.202.153: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.170.81: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 200G 100G - In the entry with IPv4 80.81.192.165: set Speed to 100000 (100G) (now 200000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.210.93: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.208.88: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 100G - In the entry with IPv4 185.6.36.150: set Speed to 100000 (100G) (now 20000).
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 IPv4 address missing from PeeringDB 86.104.125.119 86.104.125.119 86.104.125.141 IPv6 address missing from PeeringDB 2001:7f8:64:225::9009:1 2001:7f8:64:225::9009:1 2001:7f8:64:225::9009:2 Port speed differs 100G 100G + 10G - Add an entry: IPv4 86.104.125.141, IPv6 2001:7f8:64:225::9009:2, speed 10000 (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.
-
Problem PeeringDB has The export has Port speed differs 100G 50G - In the entry with IPv4 195.66.224.231: set Speed to 50000 (50G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 10G 20G - In the entry with IPv4 217.29.67.64: set Speed to 20000 (20G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G + 10G 3.75G - In the entry with IPv4 185.0.20.145: set Speed to 3750 (3.75G) (now 20000).
- In the entry with IPv4 185.0.20.42: set Speed to 3750 (3.75G) (now 10000).
From ixreport.com/net/9009/: 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.