bgpreport

Network · data from 2026-11-12

AS219502 STORMCLOUD-AS Storm Industries LLC

Registry name: STORMCLOUD-AS Storm Industries LLC, US · not in PeeringDB

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

Announced routes

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

94.154.43.0/24 Invalid: origin None 85 13% 39
209.163.105.0/24 Invalid: origin None 80 12% 38
45.204.146.0/24 Invalid: origin RIR databaseAFRINIC 95 14% 43
176.65.139.141/32 Invalid: maxLength Nonecovered by 176.65.139.0/24 1 0%low visibility 1
176.65.139.0/24 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

AS219502 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 8 are in fix.csv.

  • ROA: origin3
  • ROA: maxLength1
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin94.154.43.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS219502 should announce it, add a ROA for AS219502.85 of 673
Route object: none94.154.43.0/24No route object for it. Add a route object with origin AS219502 in the RIR database for the space.85 of 673
ROA: origin209.163.105.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS219502 should announce it, add a ROA for AS219502.80 of 673
Route object: none209.163.105.0/24No route object for it. Add a route object with origin AS219502 in the RIR database for the space.80 of 673
ROA: origin45.204.146.0/24ROAs covering it name AS17561, not AS219502. If AS219502 should announce it, add a ROA for AS219502.95 of 673
ROA: maxLength176.65.139.141/32ROA 176.65.139.0/24 AS219502 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 176.65.139.141/32.1 of 673
Route object: none176.65.139.141/32No route object for it. A route object for 176.65.139.0/24 with origin AS219502 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS219502 in the RIR database for the space.1 of 673

Route objects not announced

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

89.251.29.0/24RIPEValid

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.