bgpreport

Network · data from 2026-11-12

AS61251 HOST4BIZ-AS Host4Biz sp. z o.o.

Registry name: HOST4BIZ-AS Host4Biz sp. z o.o., PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61251, 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.
77.73.36.0/22 No ROA RIR databaseRIPE 673 100% 66
91.195.12.0/23 No ROA RIR databaseRIPE 673 100% 66
91.232.127.0/24 No ROA RIR databaseRIPE 673 100% 66
185.151.244.0/22 No ROA RIR databaseRIPE 673 100% 66
2a07:7c80::/29 No ROA RIR databaseRIPE 633 100% 69

AS-SET

AS61251 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: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none77.73.36.0/22No ROA covers it. Add a ROA for AS61251, maxLength 22.673 of 673
ROA: none91.195.12.0/23No ROA covers it. Add a ROA for AS61251, maxLength 23.673 of 673
ROA: none91.232.127.0/24No ROA covers it. Add a ROA for AS61251, maxLength 24.673 of 673
ROA: none185.151.244.0/22No ROA covers it. Add a ROA for AS61251, maxLength 22.673 of 673
ROA: none2a07:7c80::/29No ROA covers it. Add a ROA for AS61251, maxLength 29.633 of 636

Route objects not announced

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

185.151.244.0/23RIPENo ROA
185.151.245.0/24RIPENo ROA
185.151.246.0/23RIPENo 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.