Microsoft: PeeringDB fix list
AS8075 · peeringdb.com/net/694
19 things to fix in Microsoft's PeeringDB record, from what its exchanges publish: 4 to add, 10 to correct, 5 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Microsoft'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 (4)
On the exchange's own member list, but not in Microsoft'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.
-
2 connections, so 2 entries:
IPv4 196.223.1.47 IPv6 2001:43f8:390::2f Speed 10000 Mbps (10G) RS peer No IPv4 196.223.1.48 IPv6 2001:43f8:390::30 Speed 10000 Mbps (10G) RS peer No -
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 IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (10)
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 2 × 10G 4 × 10G -
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 200G - In the entry with IPv4 185.1.170.161: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 185.1.170.170: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 200G + 2 × 10G - In the entry with IPv4 103.27.170.220: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 103.27.170.5: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 200G - In the entry with IPv4 217.29.66.112: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 217.29.66.212: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 200G + 2 × 10G - In the entry with IPv4 196.60.70.147: set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 196.60.70.47: set Speed to 200000 (200G) (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 2 × 100G 25G - In the entry with IPv4 185.0.20.214: set Speed to 25000 (25G) (now 100000).
- In the entry with IPv4 185.0.20.215: set Speed to 25000 (25G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 200G + 100G - In the entry with IPv4 103.16.102.139: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 192.121.80.59 192.121.80.117 192.121.80.37 192.121.80.59 192.121.80.117 IPv6 address missing from PeeringDB 2001:7f8:3e:0:a500:0:8075:1 2001:7f8:3e:0:a500:0:8075:2 2001:7f8:3e:0:a500:0:8075:1 2001:7f8:3e:0:a500:0:8075:2 2001:7f8:3e:0:a500:0:8075:3 Port speed differs 2 × 20G 120G + 100G + 20G - In the entry with IPv4 192.121.80.59: set Speed to 120000 (120G) (now 20000).
- Add an entry: IPv4 192.121.80.37, IPv6 2001:7f8:3e:0:a500:0:8075:3, speed 100000 (100G), 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 2 × 100G 110G - In the entry with IPv4 212.91.0.147: set Speed to 110000 (110G) (now 100000).
- In the entry with IPv4 212.91.0.148: set Speed to 110000 (110G) (now 100000).
- Add an entry: IPv4 212.91.0.147, IPv6 –, speed 110000 (110G).
- Add an entry: IPv4 212.91.0.148, IPv6 –, speed 110000 (110G).
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 IPv6 address differs 2001:7f8:73::f8b:0:1 2001:7f8:73::f8b:0:2 2001:7f8:73::1f8b:0:1 2001:7f8:73::1f8b:0:2 - In the entry with IPv4 185.1.8.22: set IPv6 to 2001:7f8:73::1f8b:0:2 (now 2001:7f8:73::f8b:0:2).
- In the entry with IPv4 185.1.8.32: set IPv6 to 2001:7f8:73::1f8b:0:1 (now 2001:7f8:73::f8b:0:1).
Check these entries (5)
In PeeringDB, but on none of the exchange's own lists. If Microsoft has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958Not on its website members listIPv4 185.0.42.20 IPv6 2001:7f8:115:1::20 Speed 100000 Mbps (100G) IPv4 185.0.42.23 IPv6 2001:7f8:115:1::23 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 185.1.210.105 IPv6 2001:7f8:3d::1f8b:0:1 Speed 10000 Mbps (10G) IPv4 185.1.210.133 IPv6 2001:7f8:3d::1f8b:0:2 Speed 10000 Mbps (10G) -
IPv4 212.237.192.181 IPv6 2001:7f8:d:202::181 Speed 100000 Mbps (100G) -
IPv4 212.237.193.181 IPv6 2001:7f8:d:203::181 Speed 100000 Mbps (100G) -
IPv4 206.126.235.65 IPv6 2001:504:33::65 Speed 100000 Mbps (100G) IPv4 206.126.235.66 IPv6 2001:504:33::66 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/8075/: 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.