bgpreport

Network · data from 2026-11-12

AS402664 EHOCGL - Evergreen

Registry name: EHOCGL - Evergreen, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402664, 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.
164.37.225.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2a02:ffc0::/29 Valid RIR databaseRIPE 631 99% 69
2a05:e900::/29 Valid RIR databaseRIPE 631 99% 69
2a0c:7e80::/29 Valid RIR databaseRIPE 631 99% 69
2a11:4940::/29 Valid RIR databaseRIPE 631 99% 69
2a12:bf00::/29 Valid RIR databaseRIPE 631 99% 69

AS-SET

AS402664 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin164.37.225.0/24ROAs covering it name AS138995, not AS402664. If AS402664 should announce it, add a ROA for AS402664.1 of 673
Route object: none164.37.225.0/24Route objects for it name AS138995. Add a route object with origin AS402664 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS402664 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.