bgpreport

Network · data from 2026-11-12

AS64466 UMS-AS UNIVERSAL MOBILE SYSTEMS LLC

Registry name: UMS-AS UNIVERSAL MOBILE SYSTEMS LLC, UZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64466, 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.

2a09:adc0::/29 No ROA None 633 100% 68
2a09:adc0:1::/48 No ROA None 633 100% 68
185.163.24.0/22 No ROA RIR databaseRIPE 673 100% 66
185.163.26.0/24 No ROA RIR databaseRIPE 673 100% 68
185.213.228.0/22 No ROA RIR databaseRIPE 673 100% 68
161.104.64.0/22 No ROA RIR databaseRIPE 672 100% 68
185.213.229.0/24 No ROA RIR databaseRIPE 672 100% 68
185.213.230.0/24 No ROA RIR databaseRIPE 672 100% 68
185.213.231.0/24 No ROA RIR databaseRIPE 672 100% 66
2a09:adc0::/48 No ROA RIR databaseRIPE 635 100% 70

AS-SET

AS64466 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: none10
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a09:adc0::/29No ROA covers it. Add a ROA for AS64466, maxLength 29.633 of 636
Route object: none2a09:adc0::/29No route object for it. Add a route object with origin AS64466 in the RIR database for the space.633 of 636
ROA: none2a09:adc0:1::/48No ROA covers it. Add a ROA for AS64466, maxLength 48.633 of 636
Route object: none2a09:adc0:1::/48No route object for it. Add a route object with origin AS64466 in the RIR database for the space.633 of 636
ROA: none185.163.24.0/22No ROA covers it. Add a ROA for AS64466, maxLength 22.673 of 673
ROA: none185.163.26.0/24No ROA covers it. Add a ROA for AS64466, maxLength 24.673 of 673
ROA: none185.213.228.0/22No ROA covers it. Add a ROA for AS64466, maxLength 22.673 of 673
ROA: none161.104.64.0/22No ROA covers it. Add a ROA for AS64466, maxLength 22.672 of 673
ROA: none185.213.229.0/24No ROA covers it. Add a ROA for AS64466, maxLength 24.672 of 673
ROA: none185.213.230.0/24No ROA covers it. Add a ROA for AS64466, maxLength 24.672 of 673
ROA: none185.213.231.0/24No ROA covers it. Add a ROA for AS64466, maxLength 24.672 of 673
ROA: none2a09:adc0::/48No ROA covers it. Add a ROA for AS64466, maxLength 48.635 of 636

Route objects not announced

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

185.163.27.0/24RIPENo ROA
2a09:adc0:0:e::/64RIPENo 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.