bgpreport

Network · data from 2026-11-12

AS12380 LENSVYAZ PJSC Rostelecom

Registry name: LENSVYAZ PJSC Rostelecom, RU · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 75.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS12380, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS12380, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
212.58.192.0/24 Valid Nonecovered by 212.58.192.0/19 672 100% 67
80.248.144.0/20 Valid RIR databaseRIPE 672 100% 67
89.20.16.0/20 Valid RIR databaseRIPE 672 100% 67
212.58.192.0/19 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS12380 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none212.58.192.0/24No route object for it. A route object for 212.58.192.0/19 with origin AS12380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12380 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS12380 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.