Hurricane Electric: PeeringDB fix list
AS6939 · peeringdb.com/net/291
19 things to fix in Hurricane Electric's PeeringDB record, from what its exchanges publish: 1 to add, 14 to correct, 2 to check, 2 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.
Make the changes on Hurricane Electric'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 Hurricane Electric's PeeringDB record. Add one entry per connection with these values.
-
IPv4 149.112.34.11 IPv6 2001:504:119::11 Speed 300000 Mbps (300G) RS peer No
Correct these entries (14)
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 300G 400G - In the entry with IPv4 80.249.209.150: set Speed to 400000 (400G) (now 300000).
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:43f8:9c1:1::206 2001:43f8:9c1:1:0:a500:6939:1 - In the entry with IPv4 196.223.38.206: set IPv6 to 2001:43f8:9c1:1:0:a500:6939:1 (now 2001:43f8:9c1:1::206).
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 110G - In the entry with IPv4 185.1.30.9: set Speed to 110000 (110G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 50G - In the entry with IPv4 194.53.172.33: set Speed to 50000 (50G) (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 100G 10G - In the entry with IPv4 193.242.98.151: 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 20G 10G - In the entry with IPv4 192.65.185.143: set Speed to 10000 (10G) (now 20000).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.224.229 178.18.236.74 178.18.224.229 178.18.236.26 178.18.236.74 IPv6 address missing from PeeringDB 2a03:5f80:4::224:229 2a03:5f80:4:2::236:74 2a03:5f80:4::224:229 2a03:5f80:4:2::236:26 2a03:5f80:4:2::236:74 - Add an entry: IPv4 178.18.236.26, IPv6 2a03:5f80:4:2::236:26, speed 300000 (300G), 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 400G 200G - In the entry with IPv4 86.104.125.69: set Speed to 200000 (200G) (now 400000).
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 differs 103.121.64.20 163.223.201.20 IPv6 address differs 2400:efa0::1:6939:1 2001:df0:a940::1:6939:1 - In the entry with IPv4 103.121.64.20: set IPv4 to 163.223.201.20 (now 103.121.64.20); set IPv6 to 2001:df0:a940::1:6939:1 (now 2400:efa0::1:6939:1).
-
Problem PeeringDB has The export has Port speed differs 100G 50T - In the entry with IPv4 212.237.192.187: set Speed to 50000000 (50T) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 50T - In the entry with IPv4 212.237.193.187: set Speed to 50000000 (50T) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 200G 25G - In the entry with IPv4 185.0.20.118: set Speed to 25000 (25G) (now 200000).
-
Problem PeeringDB has The export has Port speed differs 100G 100G + 10G - In the entry with IPv4 206.80.234.6: set Speed to 10000 (10G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 100G 200G - In the entry with IPv4 185.1.115.53: 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.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If Hurricane Electric has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 49.213.56.1 IPv6 2001:df5:7880::1b1b:0:1 Speed 30000 Mbps (30G) -
IPv4 91.220.194.139 IPv6 2001:7f8:46::6939 Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
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 198.32.98.37 IPv6 2001:478:98::37 Speed 20000 Mbps (20G) -
Only one outside network
IPv4 103.48.48.137 IPv6 2001:ded:1::9 Speed 100000 Mbps (100G)
From ixreport.com/net/6939/: 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.