BroadSoft HIPCOM Ltd: PeeringDB fix list
AS35180 · peeringdb.com/net/5382
3 things to fix in BroadSoft HIPCOM Ltd's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on BroadSoft HIPCOM Ltd'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 BroadSoft HIPCOM Ltd's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.81.193.91 IPv6 2001:7f8::896c:0:1 Speed 1000 Mbps (1G) RS peer Yes
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 differs 195.66.226.221 195.66.226.106 IPv6 address missing from PeeringDB none 2001:7f8:4::896c:1 Port speed differs 1G 10G - In the entry with IPv4 195.66.226.221: set IPv4 to 195.66.226.106 (now 195.66.226.221); set IPv6 to 2001:7f8:4::896c:1 (now empty); set Speed to 10000 (10G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If BroadSoft HIPCOM Ltd 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.238.221 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/35180/: 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.