bgpreport

Network · data from 2026-11-12

AS402309 AS-AURO - AuroraNetworks LLC

Registry name: AS-AURO - AuroraNetworks LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS402309, 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.

82.110.128.0/24 Valid Nonecovered by 82.110.128.0/22 670 100% 67
45.141.170.0/24 Valid Nonecovered by 45.141.170.0/23 669 99% 67
45.141.171.0/24 Valid Nonecovered by 45.141.170.0/23 669 99% 67
151.247.166.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
82.110.128.0/22 Valid RIR databaseRADB, RIPE 670 100% 67
45.141.170.0/23 Valid RIR databaseRADB, RIPE 7 1%low visibility 4

AS-SET

AS402309 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 6 are in fix.csv.

  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none82.110.128.0/24No route object for it. A route object for 82.110.128.0/22 with origin AS402309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402309 in the RIR database for the space.670 of 673
Route object: none45.141.170.0/24No route object for it. A route object for 45.141.170.0/23 with origin AS402309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402309 in the RIR database for the space.669 of 673
Route object: none45.141.171.0/24No route object for it. A route object for 45.141.170.0/23 with origin AS402309 covers it (filters allowing more-specifics accept it). Add a route object with origin AS402309 in the RIR database for the space.669 of 673

Route objects not announced

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

102.129.233.0/24AFRINIC, RADBValid
185.199.213.0/24RADB, RIPEValid
192.78.219.0/24ARIN, RADBValid

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.