bgpreport

Network · data from 2026-11-12

AS40993 AltairTula-AS MTS PJSC

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40993, 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.
80.80.192.0/21 No ROA Nonecovered by 80.80.192.0/20 673 100% 67
80.80.200.0/21 No ROA Nonecovered by 80.80.192.0/20 673 100% 67
80.80.196.0/23 No ROA Nonecovered by 80.80.192.0/20 671 100% 67
80.80.198.0/23 No ROA Nonecovered by 80.80.192.0/20 671 100% 67
81.177.78.0/24 No ROA Other origin only 670 100% 67
80.80.192.0/20 No ROA RIR databaseRIPE 673 100% 67
89.107.192.0/21 No ROA RIR databaseRIPE 673 100% 67
109.111.0.0/19 No ROA RIR databaseRIPE 673 100% 67
2a02:5500::/32 No ROA RIR databaseRIPE 636 100% 67

AS-SET

AS40993 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 14 are in fix.csv.

  • ROA: none9
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none80.80.192.0/21No ROA covers it. Add a ROA for AS40993, maxLength 21.673 of 673
Route object: none80.80.192.0/21No route object for it. A route object for 80.80.192.0/20 with origin AS40993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40993 in the RIR database for the space.673 of 673
ROA: none80.80.200.0/21No ROA covers it. Add a ROA for AS40993, maxLength 21.673 of 673
Route object: none80.80.200.0/21No route object for it. A route object for 80.80.192.0/20 with origin AS40993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40993 in the RIR database for the space.673 of 673
ROA: none80.80.196.0/23No ROA covers it. Add a ROA for AS40993, maxLength 23.671 of 673
Route object: none80.80.196.0/23No route object for it. A route object for 80.80.192.0/20 with origin AS40993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40993 in the RIR database for the space.671 of 673
ROA: none80.80.198.0/23No ROA covers it. Add a ROA for AS40993, maxLength 23.671 of 673
Route object: none80.80.198.0/23No route object for it. A route object for 80.80.192.0/20 with origin AS40993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40993 in the RIR database for the space.671 of 673
ROA: none81.177.78.0/24No ROA covers it. Add a ROA for AS40993, maxLength 24.670 of 673
Route object: none81.177.78.0/24Route objects for it name AS40933. Add a route object with origin AS40993 in the RIR database for the space.670 of 673
ROA: none80.80.192.0/20No ROA covers it. Add a ROA for AS40993, maxLength 20.673 of 673
ROA: none89.107.192.0/21No ROA covers it. Add a ROA for AS40993, maxLength 21.673 of 673
ROA: none109.111.0.0/19No ROA covers it. Add a ROA for AS40993, maxLength 19.673 of 673
ROA: none2a02:5500::/32No ROA covers it. Add a ROA for AS40993, maxLength 32.636 of 636

Route objects not announced

Every route object with origin AS40993 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.