bgpreport

Network · data from 2026-11-12

AS402411 AL-3144-402411-01 - Aeryte

Registry name: AL-3144-402411-01 - Aeryte, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
1IPv6 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 AS402411, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS402411, 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.
192.6.116.0/23 Invalid: origin Other origin only 4 1%low visibility 3
198.134.174.0/24 Valid RIR databaseARIN 673 100% 67
2602:f3a9::/40 Valid RIR databaseARIN 635 100% 67

AS-SET

AS402411 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: origin192.6.116.0/23ROAs covering it name AS834, not AS402411. If AS402411 should announce it, add a ROA for AS402411.4 of 673
Route object: none192.6.116.0/23Route objects for it name AS834. Add a route object with origin AS402411 in the RIR database for the space.4 of 673

Route objects not announced

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