Powerhouse Management, Inc.: PeeringDB fix list
AS22363 · peeringdb.com/net/7627
3 things to fix in Powerhouse Management, Inc.'s PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Powerhouse Management, Inc.'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 IPv6 address missing from PeeringDB none 2001:7f8:1::a502:2363:1 2001:7f8:1::a502:2363:2 - In the entry with IPv4 80.249.212.22: set IPv6 to 2001:7f8:1::a502:2363:2 (now empty).
- In the entry with IPv4 80.249.212.23: set IPv6 to 2001:7f8:1::a502:2363:1 (now empty).
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 Powerhouse Management, Inc. 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.225.71 IPv6 – Speed 1000 Mbps (1G) -
IPv4 195.66.237.71 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/22363/: 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.