bgpreport

Network · data from 2026-11-12

AS49528 MARCIN MALOLEPSZY @ALFANET

Registry name: ALFANET-PL-AS MARCIN MALOLEPSZY @ALFANET, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49528, 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.
31.42.12.59/32 No ROA Nonecovered by 31.42.0.0/20 2 0%low visibility 6
185.19.118.126/32 No ROA Nonecovered by 185.19.116.0/22 2 0%low visibility 6
185.19.119.225/32 No ROA Nonecovered by 185.19.116.0/22 2 0%low visibility 6
31.42.0.0/20 No ROA RIR databaseRIPE 671 100% 68
185.19.116.0/22 No ROA RIR databaseRIPE 671 100% 67
185.55.67.0/24 No ROA RIR databaseRIPE 671 100% 68
195.88.28.0/23 No ROA RIR databaseRIPE 671 100% 68
2a00:40a0::/40 No ROA RIR databaseRIPE 14 2%low visibility 14
2a02:4a40:101::/48 No ROA RIR databaseRIPE 14 2%low visibility 14

AS-SET

AS49528'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 13 are in fix.csv.

  • ROA: none9
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none31.42.12.59/32No ROA covers it. Add a ROA for AS49528, maxLength 32.2 of 673
Route object: none31.42.12.59/32No route object for it. A route object for 31.42.0.0/20 with origin AS49528 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49528 in the RIR database for the space.2 of 673
ROA: none185.19.118.126/32No ROA covers it. Add a ROA for AS49528, maxLength 32.2 of 673
Route object: none185.19.118.126/32No route object for it. A route object for 185.19.116.0/22 with origin AS49528 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49528 in the RIR database for the space.2 of 673
ROA: none185.19.119.225/32No ROA covers it. Add a ROA for AS49528, maxLength 32.2 of 673
Route object: none185.19.119.225/32No route object for it. A route object for 185.19.116.0/22 with origin AS49528 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS49528 in the RIR database for the space.2 of 673
ROA: none31.42.0.0/20No ROA covers it. Add a ROA for AS49528, maxLength 20.671 of 673
ROA: none185.19.116.0/22No ROA covers it. Add a ROA for AS49528, maxLength 22.671 of 673
ROA: none185.55.67.0/24No ROA covers it. Add a ROA for AS49528, maxLength 24.671 of 673
ROA: none195.88.28.0/23No ROA covers it. Add a ROA for AS49528, maxLength 23.671 of 673
ROA: none2a00:40a0::/40No ROA covers it. Add a ROA for AS49528, maxLength 40.14 of 636
ROA: none2a02:4a40:101::/48No ROA covers it. Add a ROA for AS49528, maxLength 48.14 of 636

Route objects not announced

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

2a10:f781:10:27c8::/64RIPENo 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.