Network · data from 2026-11-12

AS18854 RadWeb, LLC

Registry name: RADWEB-NA-01 - RadWeb, LLC, US · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object

4IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS18854, seen from no peer

Announced routes

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


141.195.117.0/24	Valid	RIR databaseARIN	672 100%	67
131.143.94.0/24	Valid	RIR databaseARIN	670 100%	67
141.195.116.0/24	Valid	RIR databaseARIN	670 100%	68
141.195.118.0/23	Valid	RIR databaseARIN	670 100%	68
199.249.9.0/24	Valid	RIR databaseARIN	670 100%	68
199.249.10.0/24	Valid	RIR databaseARIN	670 100%	68
199.249.11.0/24	Valid	RIR databaseARIN	670 100%	68
23.131.216.0/24	Valid	RIR databaseARIN	666 99%	68
199.249.8.0/24	Valid	RIR databaseARIN	666 99%	68
2606:aec0:4000::/36	Valid	RIR databaseARIN	636 100%	67
2606:aec0:1000::/36	Valid	RIR databaseARIN	635 100%	70
2606:aec0:3000::/36	Valid	RIR databaseARIN	635 100%	67
2606:aec0:2000::/36	Valid	RIR databaseARIN	634 100%	69

AS-SET

AS18854's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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