bgpreport

Network · data from 2026-11-12

AS33585 NEWPORTBEACH-ASN01 - City of Newport Beach

Registry name: NEWPORTBEACH-ASN01 - City of Newport Beach, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33585, 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.12.174/31 No ROA None 1 0%low visibility 1
205.155.143.96/27 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS33585 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none137.164.12.174/31No ROA covers it. Add a ROA for AS33585, maxLength 31.1 of 673
Route object: none137.164.12.174/31No route object for it. Add a route object with origin AS33585 in the RIR database for the space.1 of 673
ROA: none205.155.143.96/27No ROA covers it. Add a ROA for AS33585, maxLength 27.1 of 673
Route object: RIR205.155.143.96/27Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

216.237.19.0/24RADBNo 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.