bgpreport

Network · data from 2026-11-12

AS54116 STROM - Strom Holdings LLC

Registry name: STROM - Strom Holdings LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54116, 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.
199.115.201.0/24 No ROA None 670 100% 67
199.115.202.0/24 No ROA None 670 100% 67
2602:feb3::/48 No ROA Nonecovered by 2602:feb3::/36 635 100% 68
2602:feb3::/64 No ROA Nonecovered by 2602:feb3::/36 15 2%low visibility 14
23.145.192.0/24 No ROA Other IRR onlyRADB 670 100% 67

AS-SET

AS54116 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none199.115.201.0/24No ROA covers it. Add a ROA for AS54116, maxLength 24.670 of 673
Route object: none199.115.201.0/24No route object for it. Add a route object with origin AS54116 in the RIR database for the space.670 of 673
ROA: none199.115.202.0/24No ROA covers it. Add a ROA for AS54116, maxLength 24.670 of 673
Route object: none199.115.202.0/24No route object for it. Add a route object with origin AS54116 in the RIR database for the space.670 of 673
ROA: none2602:feb3::/48No ROA covers it. Add a ROA for AS54116, maxLength 48.635 of 636
Route object: none2602:feb3::/48No route object for it. A route object for 2602:feb3::/36 with origin AS54116 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54116 in the RIR database for the space.635 of 636
ROA: none2602:feb3::/64No ROA covers it. Add a ROA for AS54116, maxLength 64.15 of 636
Route object: none2602:feb3::/64No route object for it. A route object for 2602:feb3::/36 with origin AS54116 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS54116 in the RIR database for the space.15 of 636
ROA: none23.145.192.0/24No ROA covers it. Add a ROA for AS54116, maxLength 24.670 of 673
Route object: RIR23.145.192.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

2602:feb3::/36RADBNo 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.