bgpreport

Network · data from 2026-11-12

AS41930 InitZero

Registry name: INITZERO-AS InitZero Lukasz Wasikowski, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41930, 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.204.88.0/22 No ROA RIR databaseRIPE 673 100% 66
193.221.122.0/24 No ROA RIR databaseRIPE 673 100% 66
194.36.165.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: none3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none91.204.88.0/22No ROA covers it. Add a ROA for AS41930, maxLength 22.673 of 673
ROA: none193.221.122.0/24No ROA covers it. Add a ROA for AS41930, maxLength 24.673 of 673
ROA: none194.36.165.0/24No ROA covers it. Add a ROA for AS41930, maxLength 24.673 of 673

Route objects not announced

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

91.204.88.0/24RIPENo ROA
91.204.89.0/24RIPENo ROA
91.204.90.0/24RIPENo ROA
91.204.91.0/24RIPENo ROA
2001:67c:1738::/48RIPENo 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.