bgpreport

Network · data from 2026-11-12

AS63435 MONTEREY-AS-01 - County of Monterey

Registry name: MONTEREY-AS-01 - County of Monterey, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63435, 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.7.82/31 No ROA None 1 0%low visibility 1
205.154.248.0/24 No ROA Other IRR onlyRADB 668 99% 68
50.145.72.0/24 Valid None 664 99% 67
192.92.176.0/24 Valid RIR databaseARIN, RADB 673 100% 68
199.58.31.0/24 Valid RIR databaseARIN 673 100% 67
199.58.30.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

AS63435 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 10 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none137.164.7.82/31No ROA covers it. Add a ROA for AS63435, maxLength 31.1 of 673
Route object: none137.164.7.82/31No route object for it. Add a route object with origin AS63435 in the RIR database for the space.1 of 673
ROA: none205.154.248.0/24No ROA covers it. Add a ROA for AS63435, maxLength 24.668 of 673
Route object: RIR205.154.248.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: none50.145.72.0/24No route object for it. Add a route object with origin AS63435 in the RIR database for the space.664 of 673

Route objects not announced

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

199.58.28.0/22ARINNo ROA
199.58.28.0/23ARINValid
199.58.28.0/24ARINValid
199.58.29.0/24ARINValid
199.58.30.0/23ARINValid

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.