Liquid Intelligent Technologies: PeeringDB fix list
AS30844 · peeringdb.com/net/725
7 things to fix in Liquid Intelligent Technologies's PeeringDB record, from what its exchanges publish: 3 to add, 4 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Liquid Intelligent Technologies'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 (3)
On the exchange's own member list, but not in Liquid Intelligent Technologies's PeeringDB record. Add one entry per connection with these values.
-
IPv4 196.60.44.13 IPv6 2001:43f8:310::13 Speed 1000 Mbps (1G) RS peer No -
IPv4 196.60.114.69 IPv6 2001:43f8:16d0::787c:1 Speed 10000 Mbps (10G) RS peer Yes -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (4)
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 196.216.148.55: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 40G - In the entry with IPv4 196.223.21.44: set Speed to 40000 (40G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 100G 200G - In the entry with IPv4 195.66.224.68: set Speed to 200000 (200G) (now 100000).
-
Problem PeeringDB has The export has Port speed differs 400G + 300G 400G + 300G + 10G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/30844/: 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.