Her Majesty's Revenue and Customs: PeeringDB fix list
AS204222 · peeringdb.com/net/12071
2 things to fix in Her Majesty's Revenue and Customs's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 21:35 UTC.
Make the changes on Her Majesty's Revenue and Customs'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 (1)
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 195.66.237.237 195.66.239.45 195.66.239.49 195.66.237.237 195.66.239.45 IPv6 address in PeeringDB, not in the export 2001:7f8:4:1:0:3:1dbe:1 2001:7f8:4:1:0:3:1dbe:2 2001:7f8:4:1:0:3:1dbe:3 2001:7f8:4:1:0:3:1dbe:1 2001:7f8:4:1:0:3:1dbe:3 Port speed differs 2 × 20G + 10G 2 × 20G - The entry with IPv4 195.66.239.49, IPv6 2001:7f8:4:1:0:3:1dbe:2 isn't in the export: delete it if that connection is gone.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Her Majesty's Revenue and Customs has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.227.45 IPv6 2001:7f8:4::3:1dbe:1 Speed 1000 Mbps (1G) IPv4 195.66.227.49 IPv6 2001:7f8:4::3:1dbe:2 Speed 1000 Mbps (1G)
From ixreport.com/net/204222/: 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.