Jola Cloud Solutions Ltd: PeeringDB fix list
AS212174
5 things to fix in Jola Cloud Solutions Ltd's PeeringDB record, from what its exchanges publish: 4 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
AS212174 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (4)
On the exchange's own member list, but not in Jola Cloud Solutions Ltd's PeeringDB record. Add one entry per connection with these values.
-
IPv4 195.66.228.123 IPv6 2001:7f8:4::3:3cce:1 Speed 4000 Mbps (4G) RS peer No -
IPv4 195.66.237.41 IPv6 2001:7f8:4:1:0:3:3cce:1 Speed 4000 Mbps (4G) RS peer No -
LINX Manchester Manchester, United Kingdom · PeeringDB 583From its IX-F export and website members listIPv4 195.66.244.27 IPv6 2001:7f8:4:2:0:3:3cce:1 Speed 4000 Mbps (4G) RS peer No -
IPv4 5.57.82.218 IPv6 2001:7f8:17::3:3cce:1 Speed 1000 Mbps (1G) 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.
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 Address belongs to another network in PeeringDB 195.66.244.27 is AS43545 Teledata UK Ltd 195.66.244.27 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.
From ixreport.com/net/212174/: 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.