bgpreport

Network · data from 2026-11-12

AS13940 SJCOE - San Joaquin County Office of Education

Registry name: SJCOE - San Joaquin County Office of Education, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13940, 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.129.0.0/18 No ROA Nonecovered by 204.129.0.0/16 669 99% 68
204.129.64.0/18 No ROA Nonecovered by 204.129.0.0/16 669 99% 68
204.129.128.0/18 No ROA Nonecovered by 204.129.0.0/16 669 99% 68
204.129.192.0/18 No ROA Nonecovered by 204.129.0.0/16 669 99% 68
204.129.132.0/28 No ROA Nonecovered by 204.129.0.0/16 1 0%low visibility 1
205.154.255.48/29 No ROA None 1 0%low visibility 1

AS-SET

AS13940 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none204.129.0.0/18No ROA covers it. Add a ROA for AS13940, maxLength 18.669 of 673
Route object: none204.129.0.0/18No route object for it. A route object for 204.129.0.0/16 with origin AS13940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13940 in the RIR database for the space.669 of 673
ROA: none204.129.64.0/18No ROA covers it. Add a ROA for AS13940, maxLength 18.669 of 673
Route object: none204.129.64.0/18No route object for it. A route object for 204.129.0.0/16 with origin AS13940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13940 in the RIR database for the space.669 of 673
ROA: none204.129.128.0/18No ROA covers it. Add a ROA for AS13940, maxLength 18.669 of 673
Route object: none204.129.128.0/18No route object for it. A route object for 204.129.0.0/16 with origin AS13940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13940 in the RIR database for the space.669 of 673
ROA: none204.129.192.0/18No ROA covers it. Add a ROA for AS13940, maxLength 18.669 of 673
Route object: none204.129.192.0/18No route object for it. A route object for 204.129.0.0/16 with origin AS13940 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13940 in the RIR database for the space.669 of 673
ROA: none204.129.132.0/28No ROA covers it. Add a ROA for AS13940, maxLength 28.1 of 673
Route object: none204.129.132.0/28No route object for it. A route object for 204.129.0.0/16 with origin AS13940 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS13940 in the RIR database for the space.1 of 673
ROA: none205.154.255.48/29No ROA covers it. Add a ROA for AS13940, maxLength 29.1 of 673
Route object: none205.154.255.48/29No route object for it. Add a route object with origin AS13940 in the RIR database for the space.1 of 673

Route objects not announced

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

204.129.0.0/16RADBNo 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.