bgpreport

Network · data from 2026-11-12

AS21922 WorldSpice Technologies

Registry name: WEBNET - WorldSpice Technologies, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21922, 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.
204.197.128.0/20 Valid None 673 100% 67
216.37.64.0/20 Valid None 673 100% 67
216.37.64.0/24 Valid None 673 100% 67
216.37.65.0/24 Valid None 673 100% 67
216.37.66.0/24 Valid None 673 100% 67
216.37.69.0/24 Valid None 673 100% 67
216.37.72.0/24 Valid None 673 100% 67
216.37.74.0/24 Valid None 673 100% 67
216.37.76.0/24 Valid None 673 100% 67
216.37.80.0/20 Valid None 673 100% 67
216.37.85.0/24 Valid None 673 100% 67
2604:c040::/32 Valid None 636 100% 67

AS-SET

AS21922'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 12 are in fix.csv.

  • Route object: none12
ChangePrefix or setDetailFull-table peers
Route object: none204.197.128.0/20No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.64.0/20No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.64.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.65.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.66.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.69.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.72.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.74.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.76.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.80.0/20No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none216.37.85.0/24No route object for it. Add a route object with origin AS21922 in the RIR database for the space.673 of 673
Route object: none2604:c040::/32No route object for it. Add a route object with origin AS21922 in the RIR database for the space.636 of 636

Route objects not announced

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