bgpreport

Network · data from 2026-11-12

AS13055 CSVLG-AS MTS PJSC

Registry name: CSVLG-AS MTS PJSC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13055, 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.

37.72.64.0/20 No ROA RIR databaseRIPE 673 100% 67
176.65.96.0/20 No ROA RIR databaseRIPE 673 100% 67
176.65.112.0/20 No ROA RIR databaseRIPE 673 100% 67
213.176.240.0/21 No ROA RIR databaseRIPE 673 100% 67
77.93.100.0/22 No ROA RIR databaseRIPE 671 100% 67
213.176.224.0/22 No ROA RIR databaseRIPE 671 100% 67
5.144.72.0/21 No ROA RIR databaseRIPE 2 0%low visibility 2
5.144.64.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.65.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.66.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.67.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.68.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.69.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.70.0/24 Valid RIR databaseRIPE 671 100% 67
5.144.71.0/24 Valid RIR databaseRIPE 671 100% 67
77.93.120.0/22 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS13055 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 24 are in fix.csv.

  • ROA: none7
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none37.72.64.0/20No ROA covers it. Add a ROA for AS13055, maxLength 20.673 of 673
ROA: none176.65.96.0/20No ROA covers it. Add a ROA for AS13055, maxLength 20.673 of 673
ROA: none176.65.112.0/20No ROA covers it. Add a ROA for AS13055, maxLength 20.673 of 673
ROA: none213.176.240.0/21No ROA covers it. Add a ROA for AS13055, maxLength 21.673 of 673
ROA: none77.93.100.0/22No ROA covers it. Add a ROA for AS13055, maxLength 22.671 of 673
ROA: none213.176.224.0/22No ROA covers it. Add a ROA for AS13055, maxLength 22.671 of 673
ROA: none5.144.72.0/21No ROA covers it. Add a ROA for AS13055, maxLength 21.2 of 673

Route objects not announced

Route objects with origin AS13055 whose prefix no peer sees AS13055 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.144.64.0/21RIPEValid
5.144.64.0/22RIPEValid
5.144.68.0/22RIPEValid
37.72.64.0/22RIPENo ROA
37.72.68.0/22RIPENo ROA
37.72.72.0/22RIPENo ROA
37.72.76.0/22RIPENo ROA
176.65.116.0/24RIPENo ROA
176.65.117.0/24RIPENo ROA
176.65.118.0/24RIPENo ROA
176.65.119.0/24RIPENo ROA
176.65.124.0/24RIPENo ROA
176.65.125.0/24RIPENo ROA
176.65.126.0/24RIPENo ROA
176.65.127.0/24RIPENo ROA
2a00:f02::/32RIPENo ROA
2a00:13f8:fffc::/48RIPENo ROA

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.