bgpreport

Network · data from 2026-11-12

AS30679 CPPNET - California State Polytechnic University - Pomona

Registry name: CPPNET - California State Polytechnic University - Pomona, US · not in PeeringDB

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

Announced routes

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

137.164.34.70/31 No ROA None 1 0%low visibility 1
137.164.34.176/31 No ROA None 1 0%low visibility 1
2607:f380:1::118:98f2:2b00/123 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a42:2460/123 No ROA None 1 0%low visibility 1
134.71.206.0/24 Valid Nonecovered by 134.71.0.0/16 672 100% 67
2620:df:8000::/48 Valid Other IRR onlyRADB 633 100% 69
134.71.0.0/16 Valid RIR databaseARIN, RADB 669 99% 68

AS-SET

AS30679 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none137.164.34.70/31No ROA covers it. Add a ROA for AS30679, maxLength 31.1 of 673
Route object: none137.164.34.70/31No route object for it. Add a route object with origin AS30679 in the RIR database for the space.1 of 673
ROA: none137.164.34.176/31No ROA covers it. Add a ROA for AS30679, maxLength 31.1 of 673
Route object: none137.164.34.176/31No route object for it. Add a route object with origin AS30679 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:98f2:2b00/123No ROA covers it. Add a ROA for AS30679, maxLength 123.1 of 636
Route object: none2607:f380:1::118:98f2:2b00/123No route object for it. Add a route object with origin AS30679 in the RIR database for the space.1 of 636
ROA: none2607:f380:1::118:9a42:2460/123No ROA covers it. Add a ROA for AS30679, maxLength 123.1 of 636
Route object: none2607:f380:1::118:9a42:2460/123No route object for it. Add a route object with origin AS30679 in the RIR database for the space.1 of 636
Route object: none134.71.206.0/24No route object for it. A route object for 134.71.0.0/16 with origin AS30679 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30679 in the RIR database for the space.672 of 673
Route object: RIR2620:df:8000::/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 AS30679 whose prefix no peer sees AS30679 announce. Many are kept on purpose (backup routes, space announced only in some places).

2620:df:8000::/44ARINValid

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.