bgpreport

Network · data from 2026-11-12

AS6492 PCCD - Palomar Community College District

Registry name: PCCD - Palomar Community College District, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6492, 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.
205.155.239.32/27 No ROA None 1 0%low visibility 1
205.155.239.64/27 No ROA None 1 0%low visibility 1
2620:c0::/49 No ROA Nonecovered by 2620:c0::/48 1 0%low visibility 1
2620:c0:0:7000::/64 No ROA Nonecovered by 2620:c0::/48 1 0%low visibility 1
2620:c0:0:8000::/49 No ROA Nonecovered by 2620:c0::/48 1 0%low visibility 1
2620:c0:0:f000::/64 No ROA Nonecovered by 2620:c0::/48 1 0%low visibility 1
192.30.115.0/24 No ROA Other IRR onlyRADB 669 99% 68
205.153.156.0/24 No ROA Other IRR onlyRADB 669 99% 68
205.153.157.0/24 No ROA Other IRR onlyRADB 669 99% 68
205.153.158.0/24 No ROA Other IRR onlyRADB 669 99% 68
205.153.159.0/24 No ROA Other IRR onlyRADB 669 99% 68
2620:c0::/48 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS6492 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 25 are in fix.csv.

  • ROA: none12
  • Route object: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none205.155.239.32/27No ROA covers it. Add a ROA for AS6492, maxLength 27.1 of 673
Route object: none205.155.239.32/27No route object for it. Add a route object with origin AS6492 in the RIR database for the space.1 of 673
ROA: none205.155.239.64/27No ROA covers it. Add a ROA for AS6492, maxLength 27.1 of 673
Route object: none205.155.239.64/27No route object for it. Add a route object with origin AS6492 in the RIR database for the space.1 of 673
ROA: none2620:c0::/49No ROA covers it. Add a ROA for AS6492, maxLength 49.1 of 636
Route object: none2620:c0::/49No route object for it. A route object for 2620:c0::/48 with origin AS6492 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS6492 in the RIR database for the space.1 of 636
ROA: none2620:c0:0:7000::/64No ROA covers it. Add a ROA for AS6492, maxLength 64.1 of 636
Route object: none2620:c0:0:7000::/64No route object for it. A route object for 2620:c0::/48 with origin AS6492 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS6492 in the RIR database for the space.1 of 636
ROA: none2620:c0:0:8000::/49No ROA covers it. Add a ROA for AS6492, maxLength 49.1 of 636
Route object: none2620:c0:0:8000::/49No route object for it. A route object for 2620:c0::/48 with origin AS6492 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS6492 in the RIR database for the space.1 of 636
ROA: none2620:c0:0:f000::/64No ROA covers it. Add a ROA for AS6492, maxLength 64.1 of 636
Route object: none2620:c0:0:f000::/64No route object for it. A route object for 2620:c0::/48 with origin AS6492 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS6492 in the RIR database for the space.1 of 636
ROA: none192.30.115.0/24No ROA covers it. Add a ROA for AS6492, maxLength 24.669 of 673
Route object: RIR192.30.115.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none205.153.156.0/24No ROA covers it. Add a ROA for AS6492, maxLength 24.669 of 673
Route object: RIR205.153.156.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none205.153.157.0/24No ROA covers it. Add a ROA for AS6492, maxLength 24.669 of 673
Route object: RIR205.153.157.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none205.153.158.0/24No ROA covers it. Add a ROA for AS6492, maxLength 24.669 of 673
Route object: RIR205.153.158.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none205.153.159.0/24No ROA covers it. Add a ROA for AS6492, maxLength 24.669 of 673
Route object: RIR205.153.159.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2620:c0::/48No ROA covers it. Add a ROA for AS6492, maxLength 48.633 of 636
Route object: RIR2620:c0::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

205.153.156.0/22RADBNo 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.