bgpreport

Network · data from 2026-11-12

AS22244 MOTOROLA-MOBILITY - Motorola, Inc.

Registry name: MOTOROLA-MOBILITY - Motorola, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22244, 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.
144.188.20.0/24 No ROA RIR databaseARIN 671 100% 67
144.188.28.0/24 No ROA RIR databaseARIN 671 100% 67
144.188.64.0/20 No ROA RIR databaseARIN 671 100% 67
144.188.128.0/24 No ROA RIR databaseARIN 671 100% 67
144.188.130.0/24 No ROA RIR databaseARIN 671 100% 67
144.188.131.0/24 No ROA RIR databaseARIN 671 100% 67

AS-SET

AS22244 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 36 are in fix.csv.

  • ROA: none6
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: none144.188.20.0/24No ROA covers it. Add a ROA for AS22244, maxLength 24.671 of 673
ROA: none144.188.28.0/24No ROA covers it. Add a ROA for AS22244, maxLength 24.671 of 673
ROA: none144.188.64.0/20No ROA covers it. Add a ROA for AS22244, maxLength 20.671 of 673
ROA: none144.188.128.0/24No ROA covers it. Add a ROA for AS22244, maxLength 24.671 of 673
ROA: none144.188.130.0/24No ROA covers it. Add a ROA for AS22244, maxLength 24.671 of 673
ROA: none144.188.131.0/24No ROA covers it. Add a ROA for AS22244, maxLength 24.671 of 673

Route objects not announced

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

103.30.232.0/24APNICValid
103.30.233.0/24APNICValid
104.232.224.0/23ARINNo ROA
104.232.224.0/24ARINNo ROA
104.232.225.0/24ARINNo ROA
104.232.228.0/24ARINNo ROA
104.232.253.0/24ARINNo ROA
104.232.254.0/24ARINNo ROA
104.232.255.0/24ARINNo ROA
144.187.48.0/20RADBNo ROA
144.187.64.0/18RADBNo ROA
144.187.160.0/20RADBNo ROA
144.187.176.0/20RADBNo ROA
144.187.224.0/20RADBNo ROA
144.187.240.0/20RADBNo ROA
144.188.0.0/16RADBNo ROA
144.188.129.0/24ARINNo ROA
144.188.134.0/24ARINNo ROA
144.189.108.0/22RADBNo ROA
144.189.128.0/17RADBNo ROA
192.54.82.0/24RADBNo ROA
192.54.83.0/24RADBNo ROA
192.54.84.0/24RADBNo ROA
192.54.85.0/24RADBNo ROA
192.88.150.0/24RADBNo ROA
192.88.156.0/24RADBNo ROA
192.88.157.0/24RADBNo ROA
192.88.158.0/24RADBNo ROA
192.88.159.0/24RADBNo ROA
192.88.160.0/24RADBNo 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.