LYNTIA NETWORKS (Backbone): PeeringDB fix list
AS12541 · peeringdb.com/net/14207
2 things to fix in LYNTIA NETWORKS (Backbone)'s PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on LYNTIA NETWORKS (Backbone)'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 LYNTIA NETWORKS (Backbone)'s PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.242.98.145 IPv6 2001:7f8:2a:0:2:2:0:8903 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 193.242.98.145 is AS8903 LYNTIA NETWORKS (Main AS) 193.242.98.145 Address belongs to another network in PeeringDB 2001:7f8:2a:0:2:2:0:8903 is AS8903 LYNTIA NETWORKS (Main AS) 2001:7f8:2a:0:2:2:0:8903 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.
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/12541/: 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.