bgpreport

Network · data from 2026-11-12

AS398305 N4-MOBILE - N4 Mobile

Registry name: N4-MOBILE - N4 Mobile, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS398305, 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.
209.209.92.0/24 No ROA Nonecovered by 209.209.92.0/22 2 0%low visibility 2
209.209.93.0/24 No ROA Nonecovered by 209.209.92.0/22 2 0%low visibility 2
209.209.94.0/24 No ROA Nonecovered by 209.209.92.0/22 2 0%low visibility 2
209.209.95.0/24 No ROA Nonecovered by 209.209.92.0/22 2 0%low visibility 2
134.195.220.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
134.195.221.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
134.195.222.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
134.195.223.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
134.195.220.0/22 No ROA RIR databaseARIN 673 100% 67
209.209.92.0/22 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS398305 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 18 are in fix.csv.

  • ROA: none10
  • Route object: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none209.209.92.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: none209.209.92.0/24No route object for it. A route object for 209.209.92.0/22 with origin AS398305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398305 in the RIR database for the space.2 of 673
ROA: none209.209.93.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: none209.209.93.0/24No route object for it. A route object for 209.209.92.0/22 with origin AS398305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398305 in the RIR database for the space.2 of 673
ROA: none209.209.94.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: none209.209.94.0/24No route object for it. A route object for 209.209.92.0/22 with origin AS398305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398305 in the RIR database for the space.2 of 673
ROA: none209.209.95.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: none209.209.95.0/24No route object for it. A route object for 209.209.92.0/22 with origin AS398305 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398305 in the RIR database for the space.2 of 673
ROA: none134.195.220.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: RIR134.195.220.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none134.195.221.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: RIR134.195.221.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none134.195.222.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: RIR134.195.222.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none134.195.223.0/24No ROA covers it. Add a ROA for AS398305, maxLength 24.2 of 673
Route object: RIR134.195.223.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none134.195.220.0/22No ROA covers it. Add a ROA for AS398305, maxLength 22.673 of 673
ROA: none209.209.92.0/22No ROA covers it. Add a ROA for AS398305, maxLength 22.673 of 673

Route objects not announced

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