Liquid Telecom: PeeringDB fix list
AS37006
One thing to fix in Liquid Telecom's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.
AS37006 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (1)
On the exchange's own member list, but not in Liquid Telecom's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 196.223.12.142 IPv6 2001:43f8:150::142 Speed 10000 Mbps (10G) RS peer Yes IPv4 196.223.12.143 IPv6 2001:43f8:150::143 Speed 1000 Mbps (1G) RS peer No PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/37006/: 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.