bgpreport

Network · data from 2026-11-12

AS393872 MOTLOW - Motlow State Community College

Registry name: MOTLOW - Motlow State Community College, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS393872, 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.
170.178.136.0/24 No ROA Nonecovered by 170.178.136.0/23 671 100% 67
170.178.138.0/24 No ROA Nonecovered by 170.178.138.0/23 671 100% 67
170.178.139.0/24 No ROA Nonecovered by 170.178.138.0/23 671 100% 67
170.178.136.0/23 No ROA Other IRR onlyRADB 673 100% 67
170.178.138.0/23 No ROA Other IRR onlyRADB 673 100% 67
170.178.137.0/24 No ROA Other IRR onlyRADB 671 100% 69

AS-SET

AS393872 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none170.178.136.0/24No ROA covers it. Add a ROA for AS393872, maxLength 24.671 of 673
Route object: none170.178.136.0/24No route object for it. A route object for 170.178.136.0/23 with origin AS393872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393872 in the RIR database for the space.671 of 673
ROA: none170.178.138.0/24No ROA covers it. Add a ROA for AS393872, maxLength 24.671 of 673
Route object: none170.178.138.0/24No route object for it. A route object for 170.178.138.0/23 with origin AS393872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393872 in the RIR database for the space.671 of 673
ROA: none170.178.139.0/24No ROA covers it. Add a ROA for AS393872, maxLength 24.671 of 673
Route object: none170.178.139.0/24No route object for it. A route object for 170.178.138.0/23 with origin AS393872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393872 in the RIR database for the space.671 of 673
ROA: none170.178.136.0/23No ROA covers it. Add a ROA for AS393872, maxLength 23.673 of 673
Route object: RIR170.178.136.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.178.138.0/23No ROA covers it. Add a ROA for AS393872, maxLength 23.673 of 673
Route object: RIR170.178.138.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.178.137.0/24No ROA covers it. Add a ROA for AS393872, maxLength 24.671 of 673
Route object: RIR170.178.137.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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