Huge Networks / Grupo YAX: PeeringDB fix list
AS264409 · peeringdb.com/net/8002
7 things to fix in Huge Networks / Grupo YAX's PeeringDB record, from what its exchanges publish: 2 to add, 5 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Huge Networks / Grupo YAX'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 (2)
On the exchange's own member list, but not in Huge Networks / Grupo YAX's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.170.111 IPv6 2001:7f8:9e:0:4:8d:0:1 Speed 100000 Mbps (100G) RS peer Yes -
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members list
IPv4 185.0.21.58 IPv6 2001:7f8:7f::c:58 Speed 12500 Mbps (12.5G) RS peer Yes
Correct these entries (5)
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 10G 100G - In the entry with IPv4 185.1.119.101: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 185.1.170.111 is AS16024 GELSEN NET 185.1.170.111 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.210.141: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.47.141: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.46.102: set Speed to 100000 (100G) (now 10000).
From ixreport.com/net/264409/: 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.