bgpreport

Network · data from 2026-11-12

AS60891 KORYAJMA-MTS-AS MTS PJSC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60891, 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.
176.222.192.0/23 No ROA Nonecovered by 176.222.192.0/21 671 100% 67
176.222.192.0/21 No ROA RIR databaseRIPE 673 100% 67
37.72.90.0/24 No ROA RIR databaseRIPE 671 100% 67
94.72.63.0/24 No ROA RIR databaseRIPE 671 100% 67
5.144.126.0/23 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS60891 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 6 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none176.222.192.0/23No ROA covers it. Add a ROA for AS60891, maxLength 23.671 of 673
Route object: none176.222.192.0/23No route object for it. A route object for 176.222.192.0/21 with origin AS60891 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60891 in the RIR database for the space.671 of 673
ROA: none176.222.192.0/21No ROA covers it. Add a ROA for AS60891, maxLength 21.673 of 673
ROA: none37.72.90.0/24No ROA covers it. Add a ROA for AS60891, maxLength 24.671 of 673
ROA: none94.72.63.0/24No ROA covers it. Add a ROA for AS60891, maxLength 24.671 of 673

Route objects not announced

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

2a00:13f8:fffd::/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.