ixreport

Lovitel LLC: PeeringDB fix list

AS41275 · peeringdb.com/net/19969

PeeringDB

3 things to fix in Lovitel LLC's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Lovitel LLC'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 (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.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.81.192.13180.81.192.131 80.81.195.180
    IPv6 address missing from PeeringDBnone2001:7f8::a13b:0:1 2001:7f8::a13b:0:3
    Port speed differs15G2 × 200G
    • In the entry with IPv4 80.81.192.131: set IPv6 to 2001:7f8::a13b:0:1 (now empty); set Speed to 200000 (200G) (now 15000).
    • Add an entry: IPv4 80.81.195.180, IPv6 2001:7f8::a13b:0:3, speed 200000 (200G), RS peer yes.
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.226.93 178.18.227.67178.18.226.93 178.18.226.134 178.18.227.67
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:93 2a03:5f80:4::226:134 2a03:5f80:4::227:67
    Port speed differs40G + 10G100G + 40G + 10G
    • In the entry with IPv4 178.18.226.93: set IPv6 to 2a03:5f80:4::226:93 (now empty).
    • In the entry with IPv4 178.18.227.67: set IPv6 to 2a03:5f80:4::227:67 (now empty).
    • Add an entry: IPv4 178.18.226.134, IPv6 2a03:5f80:4::226:134, speed 100000 (100G), 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.

  3. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.209.34195.208.209.34 195.208.209.188
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::209:188
    • Add an entry: IPv4 195.208.209.188, IPv6 2001:7f8:20:101::209:188, 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.

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