bgpreport

Network · data from 2026-11-12

AS48124 COMSTAR-Regions-TVER MTS PJSC

Registry name: COMSTAR-Regions-TVER MTS PJSC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS48124, 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.
93.187.180.0/23 No ROA Nonecovered by 93.187.180.0/22 671 100% 67
93.187.182.0/23 No ROA Nonecovered by 93.187.180.0/22 671 100% 67
93.187.180.0/22 No ROA RIR databaseRIPE 671 100% 67
95.139.72.0/23 No ROA RIR databaseRIPE 671 100% 67
95.139.72.0/24 No ROA RIR databaseRIPE 671 100% 67
95.139.73.0/24 No ROA RIR databaseRIPE 671 100% 67
95.139.74.0/24 No ROA RIR databaseRIPE 671 100% 67
85.140.112.0/23 Valid Nonecovered by 85.140.112.0/22 671 100% 67
85.140.112.0/22 Valid RIR databaseRIPE 671 100% 67
85.140.114.0/23 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS48124 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 10 are in fix.csv.

  • ROA: none7
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none93.187.180.0/23No ROA covers it. Add a ROA for AS48124, maxLength 23.671 of 673
Route object: none93.187.180.0/23No route object for it. A route object for 93.187.180.0/22 with origin AS48124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48124 in the RIR database for the space.671 of 673
ROA: none93.187.182.0/23No ROA covers it. Add a ROA for AS48124, maxLength 23.671 of 673
Route object: none93.187.182.0/23No route object for it. A route object for 93.187.180.0/22 with origin AS48124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48124 in the RIR database for the space.671 of 673
ROA: none93.187.180.0/22No ROA covers it. Add a ROA for AS48124, maxLength 22.671 of 673
ROA: none95.139.72.0/23No ROA covers it. Add a ROA for AS48124, maxLength 23.671 of 673
ROA: none95.139.72.0/24No ROA covers it. Add a ROA for AS48124, maxLength 24.671 of 673
ROA: none95.139.73.0/24No ROA covers it. Add a ROA for AS48124, maxLength 24.671 of 673
ROA: none95.139.74.0/24No ROA covers it. Add a ROA for AS48124, maxLength 24.671 of 673
Route object: none85.140.112.0/23No route object for it. A route object for 85.140.112.0/22 with origin AS48124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48124 in the RIR database for the space.671 of 673

Route objects not announced

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