bgpreport

Network · data from 2026-11-12

AS402618 TRICO-COOP-AZ - Trico

Registry name: TRICO-COOP-AZ - Trico, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402618, 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.
68.169.64.0/21 No ROA Nonecovered by 68.169.64.0/20 672 100% 67
68.169.72.0/21 No ROA Nonecovered by 68.169.64.0/20 672 100% 67
2607:1540::/36 No ROA Nonecovered by 2607:1540::/32 631 99% 68
68.169.64.0/20 No ROA RIR databaseARIN 672 100% 67
2607:1540::/32 No ROA RIR databaseARIN 633 100% 68

AS-SET

AS402618 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 8 are in fix.csv.

  • ROA: none5
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none68.169.64.0/21No ROA covers it. Add a ROA for AS402618, maxLength 21.672 of 673
Route object: none68.169.64.0/21No route object for it. A route object for 68.169.64.0/20 with origin AS402618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402618 in the RIR database for the space.672 of 673
ROA: none68.169.72.0/21No ROA covers it. Add a ROA for AS402618, maxLength 21.672 of 673
Route object: none68.169.72.0/21No route object for it. A route object for 68.169.64.0/20 with origin AS402618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402618 in the RIR database for the space.672 of 673
ROA: none2607:1540::/36No ROA covers it. Add a ROA for AS402618, maxLength 36.631 of 636
Route object: none2607:1540::/36No route object for it. A route object for 2607:1540::/32 with origin AS402618 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402618 in the RIR database for the space.631 of 636
ROA: none68.169.64.0/20No ROA covers it. Add a ROA for AS402618, maxLength 20.672 of 673
ROA: none2607:1540::/32No ROA covers it. Add a ROA for AS402618, maxLength 32.633 of 636

Route objects not announced

Every route object with origin AS402618 is announced.

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.