Omegacom: PeeringDB fix list
AS35590
3 things to fix in Omegacom's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
AS35590 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (2)
On the exchange's own member list, but not in Omegacom's PeeringDB record. Add one entry per connection with these values.
-
IPv4 217.29.67.164 IPv6 2001:7f8:b:100:1d1:a5d3:5590:164 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 185.1.115.25 IPv6 2001:7f8:5f:ffff::25 Speed 10000 Mbps (10G) 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 217.29.67.164 is AS209368 NOINET 217.29.67.164 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/35590/: 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.