Omega Telecom: PeeringDB fix list
AS199995 · peeringdb.com/net/13892
5 things to fix in Omega Telecom's PeeringDB record, from what its exchanges publish: 1 to add, 4 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Omega Telecom'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 (1)
On the exchange's own member list, but not in Omega Telecom's PeeringDB record. Add one entry per connection with these values.
-
LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its website members listIPv4 185.1.32.134 IPv6 2001:7f8:8f::a519:9995:1 Speed Not published RS peer Not published
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 40G 400G - In the entry with IPv4 80.81.197.107: set Speed to 400000 (400G) (now 40000).
-
Problem PeeringDB has The export has Port speed differs 10G 40G + 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.
-
Problem PeeringDB has The export has Port speed differs 1G 5G - In the entry with IPv4 195.66.228.87: set Speed to 5000 (5G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.20.149: set Speed to 12500 (12.5G) (now 100000).
From ixreport.com/net/199995/: 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.