bgpreport

Network · data from 2026-11-12

AS33690 AUREON-33690 - Aureon Network Services

Registry name: AUREON-33690 - Aureon Network Services, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33690, 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.
2001:5f8:8300::/40 No ROA None 635 100% 69
208.69.144.0/24 No ROA Nonecovered by 208.69.144.0/22 3 0%low visibility 4
208.69.145.0/24 No ROA Nonecovered by 208.69.144.0/22 3 0%low visibility 4
208.69.146.0/24 No ROA Nonecovered by 208.69.144.0/22 3 0%low visibility 4
208.69.147.0/24 No ROA Nonecovered by 208.69.144.0/22 3 0%low visibility 4
70.35.0.0/24 No ROA Other IRR onlyRADB 671 100% 68
206.72.27.0/24 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

AS33690 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 15 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2001:5f8:8300::/40No ROA covers it. Add a ROA for AS33690, maxLength 40.635 of 636
Route object: none2001:5f8:8300::/40No route object for it. Add a route object with origin AS33690 in the RIR database for the space.635 of 636
ROA: none208.69.144.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.3 of 673
Route object: none208.69.144.0/24No route object for it. A route object for 208.69.144.0/22 with origin AS33690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33690 in the RIR database for the space.3 of 673
ROA: none208.69.145.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.3 of 673
Route object: none208.69.145.0/24No route object for it. A route object for 208.69.144.0/22 with origin AS33690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33690 in the RIR database for the space.3 of 673
ROA: none208.69.146.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.3 of 673
Route object: none208.69.146.0/24No route object for it. A route object for 208.69.144.0/22 with origin AS33690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33690 in the RIR database for the space.3 of 673
ROA: none208.69.147.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.3 of 673
Route object: none208.69.147.0/24No route object for it. A route object for 208.69.144.0/22 with origin AS33690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33690 in the RIR database for the space.3 of 673
ROA: none70.35.0.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.671 of 673
Route object: RIR70.35.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.72.27.0/24No ROA covers it. Add a ROA for AS33690, maxLength 24.671 of 673
Route object: RIR206.72.27.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

208.69.144.0/22RADBNo ROA

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.