bgpreport

Network · data from 2026-11-12

AS41849 NETSTORMING-WHL-AS NETSTORMING S.R.L.

Registry name: NETSTORMING-WHL-AS NETSTORMING S.R.L., IT · not in PeeringDB

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

Announced routes

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

91.102.128.0/22 Valid Nonecovered by 91.102.128.0/21 673 100% 67
91.102.134.0/24 Valid Nonecovered by 91.102.134.0/23 673 100% 67
91.102.135.0/24 Valid Nonecovered by 91.102.134.0/23 673 100% 67
5.252.44.0/23 Valid None 671 100% 67
5.252.44.0/22 Valid Other origin only 670 100% 67
91.102.134.0/23 Valid RIR databaseRIPE 673 100% 67
91.102.128.0/21 Valid RIR databaseRIPE 670 100% 67
2a01:7140::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS41849 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.

  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none91.102.128.0/22No route object for it. A route object for 91.102.128.0/21 with origin AS41849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41849 in the RIR database for the space.673 of 673
Route object: none91.102.134.0/24No route object for it. A route object for 91.102.134.0/23 with origin AS41849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41849 in the RIR database for the space.673 of 673
Route object: none91.102.135.0/24No route object for it. A route object for 91.102.134.0/23 with origin AS41849 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41849 in the RIR database for the space.673 of 673
Route object: none5.252.44.0/23No route object for it. Add a route object with origin AS41849 in the RIR database for the space.671 of 673
Route object: none5.252.44.0/22Route objects for it name AS35762. Add a route object with origin AS41849 in the RIR database for the space.670 of 673

Route objects not announced

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

91.102.130.0/24RIPEValid
91.102.131.0/24RIPEInvalid: maxLength
91.102.132.0/23RIPEInvalid: maxLength

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.