bgpreport

Network · data from 2026-11-12

AS50265 GT-AS Invest Mobile LLC

Registry name: GT-AS Invest Mobile LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50265, 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.
129.101.80.0/20 No ROA None 2 0%low visibility 2
91.233.88.0/24 Valid RIR databaseRIPE 673 100% 66
185.15.188.0/22 Valid RIR databaseRIPE 673 100% 66
193.106.68.0/22 Valid RIR databaseRIPE 673 100% 66
217.12.32.0/22 Valid RIR databaseRIPE 673 100% 66
217.12.36.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.39.0/24 Valid RIR databaseRIPE 673 100% 66
217.12.42.0/23 Valid RIR databaseRIPE 673 100% 66
217.12.44.0/22 Valid RIR databaseRIPE 673 100% 66
217.172.16.0/21 Valid RIR databaseRIPE 673 100% 66
2a00:46e0::/48 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS50265 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none129.101.80.0/20No ROA covers it. Add a ROA for AS50265, maxLength 20.2 of 673
Route object: none129.101.80.0/20No route object for it. Add a route object with origin AS50265 in the RIR database for the space.2 of 673

Route objects not announced

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