bgpreport

Network · data from 2026-11-12

AS18966 Aurora Solutions

Registry name: AURORA-SOLUTIONS - Aurora Solutions, LLC, US · PeeringDB

2IPv4 routes 50.0% RPKI valid · 50.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No 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 AS18966, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18966, 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.22.166.0/24 Invalid: origin Other origin only 1 0%low visibility 1
134.195.69.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS18966's PeeringDB record names no 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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin82.22.166.0/24ROAs covering it name AS52419, not AS18966. If AS18966 should announce it, add a ROA for AS18966.1 of 673
Route object: none82.22.166.0/24Route objects for it name AS52419. Add a route object with origin AS18966 in the RIR database for the space.1 of 673

Route objects not announced

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

23.166.96.0/24ARINValid

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.