bgpreport

Network · data from 2026-11-12

AS32045 1UWEB

Registry name: AS-DYNASCALE-LAS - 1U Web, INC., US · PeeringDB

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

Announced routes

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

173.255.0.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.1.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.2.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.3.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.4.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.5.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.6.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.7.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.8.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.9.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.10.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.11.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.12.0/24 No ROA Other IRR onlyRADB 673 100% 67
173.255.13.0/24 No ROA Other IRR onlyRADB 673 100% 67
72.26.113.0/24 No ROA Other IRR onlyRADB 672 100% 67
2606:6e00:6000::/35 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS32045'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 34 are in fix.csv.

  • ROA: none16
  • Route object: RIR16
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none173.255.0.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.0.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.1.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.1.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.2.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.2.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.3.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.3.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.4.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.5.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.5.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.6.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.6.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.7.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.7.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.8.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.8.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.9.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.9.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.10.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.10.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.11.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.11.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.12.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.12.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none173.255.13.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.673 of 673
Route object: RIR173.255.13.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none72.26.113.0/24No ROA covers it. Add a ROA for AS32045, maxLength 24.672 of 673
Route object: RIR72.26.113.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2606:6e00:6000::/35No ROA covers it. Add a ROA for AS32045, maxLength 35.634 of 636
Route object: RIR2606:6e00:6000::/35Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

173.255.0.0/20RADBNo ROA
173.255.14.0/24RADBNo 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.