ixreport

Lovitel LLC

AS41275

10Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
10Using the route servers
3To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Lovitel LLC? · Where should Lovitel LLC peer next? · Compare Lovitel LLC with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Lovitel LLC's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-11-19 12:40 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 + 70G + 10G
    • In the entry with IPv4 178.18.226.93: set IPv6 to 2a03:5f80:4::226:93 (now empty); set Speed to 70000 (70G) (now 40000).
    • 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.

Exchanges over time

0246810Oct 3, 2026Nov 19, 202610
Show as a table
DateExchanges
Nov 19, 202610
Nov 18, 202610
Nov 17, 202610
Nov 16, 202610
Nov 15, 202610
Nov 14, 202610
Nov 13, 202610
Nov 12, 202610
Nov 11, 202610
Nov 10, 202610
Nov 9, 202610
Nov 8, 202610
Nov 7, 202610
Nov 6, 202610
Nov 5, 202610
Nov 4, 202610
Nov 3, 202610
Nov 2, 202610
Nov 1, 202610
Oct 31, 202610
Oct 30, 202610
Oct 29, 202610
Oct 28, 202610
Oct 27, 202610
Oct 26, 202610
Oct 25, 202610
Oct 24, 202610
Oct 23, 202610
Oct 22, 202610
Oct 21, 202610
Oct 20, 202610
Oct 19, 202610
Oct 18, 202610
Oct 17, 202610
Oct 16, 202610
Oct 15, 202610
Oct 14, 202610
Oct 13, 202610
Oct 12, 202610
Oct 11, 202610
Oct 10, 202610
Oct 9, 202610
Oct 8, 202610
Oct 7, 202610
Oct 6, 202610
Oct 5, 202610
Oct 4, 202610
Oct 3, 202610

Map

Where Lovitel LLC's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 535G across 10 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.131 15G 48 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia Eurasia Peering IX Moscow, Russia 185.232.60.156 20G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.93
178.18.227.67
40G + 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.34 40G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.179 80G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.85 80G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.12.216 80G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.157 80G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.97 10G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.124 80G Yes PeeringDB

Exchanges in its buildings that it isn't on (7)

These exchanges have a switch in a facility where Lovitel LLC lists itself in PeeringDB, but don't have Lovitel LLC as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; Raduga-2
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Raduga-2
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; Raduga-2
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Raduga-2
Russia PIRIXSt.Petersburg, Russia 6 Raduga-2
Facilities (2)

The buildings Lovitel LLC lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 5 of 9
Russia Raduga-2St. Petersburg 3 of 8