ixreport

LVRTC Network: PeeringDB fix list

AS8194 · peeringdb.com/net/16266

PeeringDB

One thing to fix in LVRTC Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-12 00:59 UTC.

Make the changes on LVRTC Network's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. Latvia GLV-IX Riga, Latvia · PeeringDB 3750
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.236.10 185.1.236.130185.1.236.10 185.1.236.130 185.1.236.149
    IPv6 address missing from PeeringDB2001:7f8:126::10 2001:7f8:126::1302001:7f8:126::10 2001:7f8:126::130 2001:7f8:126::149
    Port speed differs2 × 10G3 × 10G
    • Add an entry: IPv4 185.1.236.149, IPv6 2001:7f8:126::149, speed 10000 (10G).

From ixreport.com/net/8194/: 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.