bgpreport

Network · data from 2026-11-12

AS13993 MOTIVE-COMM - Motive

Registry name: MOTIVE-COMM - Motive, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13993, 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.
68.235.16.0/21 No ROA None 673 100% 67
68.235.21.0/24 No ROA None 673 100% 67
68.235.24.0/21 No ROA None 673 100% 67
199.117.180.0/24 No ROA None 673 100% 67
207.71.32.0/24 No ROA None 673 100% 67
209.67.208.0/24 No ROA None 673 100% 67
216.39.83.0/24 No ROA None 673 100% 67
2620:12b::/48 No ROA None 636 100% 67

AS-SET

AS13993 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none68.235.16.0/21No ROA covers it. Add a ROA for AS13993, maxLength 21.673 of 673
Route object: none68.235.16.0/21No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none68.235.21.0/24No ROA covers it. Add a ROA for AS13993, maxLength 24.673 of 673
Route object: none68.235.21.0/24No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none68.235.24.0/21No ROA covers it. Add a ROA for AS13993, maxLength 21.673 of 673
Route object: none68.235.24.0/21No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none199.117.180.0/24No ROA covers it. Add a ROA for AS13993, maxLength 24.673 of 673
Route object: none199.117.180.0/24No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none207.71.32.0/24No ROA covers it. Add a ROA for AS13993, maxLength 24.673 of 673
Route object: none207.71.32.0/24No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none209.67.208.0/24No ROA covers it. Add a ROA for AS13993, maxLength 24.673 of 673
Route object: none209.67.208.0/24No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none216.39.83.0/24No ROA covers it. Add a ROA for AS13993, maxLength 24.673 of 673
Route object: none216.39.83.0/24No route object for it. Add a route object with origin AS13993 in the RIR database for the space.673 of 673
ROA: none2620:12b::/48No ROA covers it. Add a ROA for AS13993, maxLength 48.636 of 636
Route object: none2620:12b::/48No route object for it. Add a route object with origin AS13993 in the RIR database for the space.636 of 636

Route objects not announced

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