bgpreport

Network · data from 2026-11-12

AS39374 RU-DI-EX-AS T2 Mobile LLC

Registry name: RU-DI-EX-AS T2 Mobile LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39374, 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.59.76.0/23 No ROA Other origin only 673 100% 67
176.59.78.0/23 No ROA Other origin only 673 100% 67
176.59.80.0/23 No ROA Other origin only 673 100% 67
176.59.82.0/23 No ROA Other origin only 673 100% 67
94.77.32.0/22 No ROA Other origin only 185 27% 48
94.77.36.0/22 No ROA Other origin only 139 21% 47
176.59.122.0/23 No ROA Other origin only 64 10%low visibility 25
176.59.124.0/23 No ROA Other origin only 64 10%low visibility 25
94.77.0.0/20 No ROA Other origin only 63 9%low visibility 25
94.77.16.0/20 No ROA Other origin only 26 4%low visibility 19
46.237.44.0/22 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS39374 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none176.59.76.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.673 of 673
Route object: none176.59.76.0/23Route objects for it name AS42437. Add a route object with origin AS39374 in the RIR database for the space.673 of 673
ROA: none176.59.78.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.673 of 673
Route object: none176.59.78.0/23Route objects for it name AS42437. Add a route object with origin AS39374 in the RIR database for the space.673 of 673
ROA: none176.59.80.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.673 of 673
Route object: none176.59.80.0/23Route objects for it name AS42437. Add a route object with origin AS39374 in the RIR database for the space.673 of 673
ROA: none176.59.82.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.673 of 673
Route object: none176.59.82.0/23Route objects for it name AS42437. Add a route object with origin AS39374 in the RIR database for the space.673 of 673
ROA: none94.77.32.0/22No ROA covers it. Add a ROA for AS39374, maxLength 22.185 of 673
Route object: none94.77.32.0/22Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.185 of 673
ROA: none94.77.36.0/22No ROA covers it. Add a ROA for AS39374, maxLength 22.139 of 673
Route object: none94.77.36.0/22Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.139 of 673
ROA: none176.59.122.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.64 of 673
Route object: none176.59.122.0/23Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.64 of 673
ROA: none176.59.124.0/23No ROA covers it. Add a ROA for AS39374, maxLength 23.64 of 673
Route object: none176.59.124.0/23Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.64 of 673
ROA: none94.77.0.0/20No ROA covers it. Add a ROA for AS39374, maxLength 20.63 of 673
Route object: none94.77.0.0/20Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.63 of 673
ROA: none94.77.16.0/20No ROA covers it. Add a ROA for AS39374, maxLength 20.26 of 673
Route object: none94.77.16.0/20Route objects for it name AS48092. Add a route object with origin AS39374 in the RIR database for the space.26 of 673

Route objects not announced

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