bgpreport

Network · data from 2026-11-12

AS16573 SMCC - Santa Monica Community College District

Registry name: SMCC - Santa Monica Community College District, US · not in PeeringDB

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

Announced routes

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

204.102.230.68/31 No ROA None 1 0%low visibility 1
204.102.230.70/31 No ROA None 1 0%low visibility 1
204.102.230.80/31 No ROA None 1 0%low visibility 1
204.102.230.82/31 No ROA None 1 0%low visibility 1
204.102.230.118/31 No ROA None 1 0%low visibility 1
204.102.230.120/31 No ROA None 1 0%low visibility 1
192.92.124.0/24 No ROA Other IRR onlyRADB 669 99% 68
207.233.32.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 7

AS-SET

AS16573 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 20 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none204.102.230.68/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.68/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none204.102.230.70/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.70/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none204.102.230.80/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.80/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none204.102.230.82/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.82/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none204.102.230.118/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.118/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none204.102.230.120/31No ROA covers it. Add a ROA for AS16573, maxLength 31.1 of 673
Route object: none204.102.230.120/31No route object for it. Add a route object with origin AS16573 in the RIR database for the space.1 of 673
ROA: none192.92.124.0/24No ROA covers it. Add a ROA for AS16573, maxLength 24.669 of 673
Route object: RIR192.92.124.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none207.233.32.0/24No ROA covers it. Add a ROA for AS16573, maxLength 24.5 of 673
Route object: RIR207.233.32.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

198.147.67.0/24NTTCOM, RADBNo ROA
204.140.185.0/24NTTCOM, RADBNo ROA
207.151.68.0/24NTTCOM, RADBNo ROA
207.151.69.0/24NTTCOM, RADBNo 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.