Lovitel LLC
AS41275
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 80.81.192.131 80.81.192.131 80.81.195.180 IPv6 address missing from PeeringDB none 2001:7f8::a13b:0:1 2001:7f8::a13b:0:3 Port speed differs 15G 2 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.226.93 178.18.227.67 178.18.226.93 178.18.226.134 178.18.227.67 IPv6 address missing from PeeringDB none 2a03:5f80:4::226:93 2a03:5f80:4::226:134 2a03:5f80:4::227:67 Port speed differs 40G + 10G 100G + 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.208.209.34 195.208.209.34 195.208.209.188 IPv6 address missing from PeeringDB none 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 10 |
| Nov 18, 2026 | 10 |
| Nov 17, 2026 | 10 |
| Nov 16, 2026 | 10 |
| Nov 15, 2026 | 10 |
| Nov 14, 2026 | 10 |
| Nov 13, 2026 | 10 |
| Nov 12, 2026 | 10 |
| Nov 11, 2026 | 10 |
| Nov 10, 2026 | 10 |
| Nov 9, 2026 | 10 |
| Nov 8, 2026 | 10 |
| Nov 7, 2026 | 10 |
| Nov 6, 2026 | 10 |
| Nov 5, 2026 | 10 |
| Nov 4, 2026 | 10 |
| Nov 3, 2026 | 10 |
| Nov 2, 2026 | 10 |
| Nov 1, 2026 | 10 |
| Oct 31, 2026 | 10 |
| Oct 30, 2026 | 10 |
| Oct 29, 2026 | 10 |
| Oct 28, 2026 | 10 |
| Oct 27, 2026 | 10 |
| Oct 26, 2026 | 10 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 10 |
| Oct 21, 2026 | 10 |
| Oct 20, 2026 | 10 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 10 |
| Oct 17, 2026 | 10 |
| Oct 16, 2026 | 10 |
| Oct 15, 2026 | 10 |
| Oct 14, 2026 | 10 |
| Oct 13, 2026 | 10 |
| Oct 12, 2026 | 10 |
| Oct 11, 2026 | 10 |
| Oct 10, 2026 | 10 |
| Oct 9, 2026 | 10 |
| Oct 8, 2026 | 10 |
| Oct 7, 2026 | 10 |
| Oct 6, 2026 | 10 |
| Oct 5, 2026 | 10 |
| Oct 4, 2026 | 10 |
| Oct 3, 2026 | 10 |
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.
| DE-CIX Frankfurt Frankfurt, Germany | 15G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| Eurasia Peering IX Moscow, Russia | 20G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 40G + 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 40G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| PITER-IX Frankfurt Frankfurt, Germany | 80G | PeeringDB | |
| PITER-IX Helsinki Helsinki, Finland | 80G | PeeringDB | |
| PITER-IX Moscow Moscow, Russia | 80G | PeeringDB | |
| PITER-IX Riga Riga, Latvia | 80G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 10G | PeeringDB | |
| PITER-IX Tallinn Tallinn, Estonia | 80G | PeeringDB |
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.
| Global-IXAmsterdam, Netherlands | 138 | |
| MSK-IX Saint-PetersburgSt.Petersburg, Russia | 71 | |
| W-IXMoscow, Russia | 66 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| PIRIXSt.Petersburg, Russia | 6 |