Bite Lietuva: PeeringDB fix list
AS13194 · peeringdb.com/net/3647
7 things to fix in Bite Lietuva's PeeringDB record, from what its exchanges publish: 4 to add, 3 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Bite Lietuva'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 (4)
On the exchange's own member list, but not in Bite Lietuva's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.210.50 IPv6 2001:7f8:3d::338a:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.208.39 IPv6 2001:7f8:44::338a:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 195.69.119.211 IPv6 2001:7f8:d:fb::211 Speed 50000000 Mbps (50T) RS peer Yes -
IPv4 195.245.240.211 IPv6 2001:7f8:d:fc::211 Speed 50000000 Mbps (50T) RS peer Yes
Correct these entries (3)
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 50G 50T - In the entry with IPv4 194.68.128.211: set Speed to 50000000 (50T) (now 50000).
-
Problem PeeringDB has The export has Port speed differs 50G 50T - In the entry with IPv4 194.68.123.211: set Speed to 50000000 (50T) (now 50000).
-
Problem PeeringDB has The export has Port speed differs 100G 12.5G - In the entry with IPv4 185.0.20.51: set Speed to 12500 (12.5G) (now 100000).
From ixreport.com/net/13194/: 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.