bgpreport

Network · data from 2026-11-12

AS29878 CHMP-ASN - Community Hospital of the Monterey Peninsula

Registry name: CHMP-ASN - Community Hospital of the Monterey Peninsula, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29878, 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.40.64/29 No ROA None 1 0%low visibility 1
2607:f380:1::118:9a42:8400/121 No ROA None 1 0%low visibility 1
204.179.192.0/19 No ROA Other IRR onlyRADB 669 99% 68
204.179.219.0/24 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS29878 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 47 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
ROA: none137.164.40.64/29No ROA covers it. Add a ROA for AS29878, maxLength 29.1 of 673
Route object: none137.164.40.64/29No route object for it. Add a route object with origin AS29878 in the RIR database for the space.1 of 673
ROA: none2607:f380:1::118:9a42:8400/121No ROA covers it. Add a ROA for AS29878, maxLength 121.1 of 636
Route object: none2607:f380:1::118:9a42:8400/121No route object for it. Add a route object with origin AS29878 in the RIR database for the space.1 of 636
ROA: none204.179.192.0/19No ROA covers it. Add a ROA for AS29878, maxLength 19.669 of 673
Route object: RIR204.179.192.0/19Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none204.179.219.0/24No ROA covers it. Add a ROA for AS29878, maxLength 24.669 of 673
Route object: RIR204.179.219.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

204.179.192.0/23RADBNo ROA
204.179.192.0/24RADBNo ROA
204.179.193.0/24RADBNo ROA
204.179.194.0/23RADBNo ROA
204.179.194.0/24RADBNo ROA
204.179.195.0/24RADBNo ROA
204.179.196.0/23RADBNo ROA
204.179.196.0/24RADBNo ROA
204.179.197.0/24RADBNo ROA
204.179.198.0/23RADBNo ROA
204.179.198.0/24RADBNo ROA
204.179.199.0/24RADBNo ROA
204.179.200.0/24RADBNo ROA
204.179.201.0/24RADBNo ROA
204.179.202.0/24RADBNo ROA
204.179.203.0/24RADBNo ROA
204.179.204.0/24RADBNo ROA
204.179.205.0/24RADBNo ROA
204.179.206.0/24RADBNo ROA
204.179.207.0/24RADBNo ROA
204.179.208.0/24RADBNo ROA
204.179.209.0/24RADBNo ROA
204.179.210.0/24RADBNo ROA
204.179.211.0/24RADBNo ROA
204.179.212.0/24RADBNo ROA
204.179.213.0/24RADBNo ROA
204.179.214.0/24RADBNo ROA
204.179.215.0/24RADBNo ROA
204.179.216.0/24RADBNo ROA
204.179.217.0/24RADBNo ROA
204.179.218.0/23RADBNo ROA
204.179.218.0/24RADBNo ROA
204.179.220.0/23RADBNo ROA
204.179.220.0/24RADBNo ROA
204.179.221.0/24RADBNo ROA
204.179.222.0/23RADBNo ROA
204.179.222.0/24RADBNo ROA
204.179.223.0/24RADBNo ROA
2602:ff54::/36RADBNo 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.