bgpreport

Network · data from 2026-11-12

AS51290 HosTeam

Registry name: HOSTEAM-AS BARTOSZ WASZAK trading as HOSTEAM S.C. TOMASZ GROSZEWSKI BARTOSZ WASZAK LUKASZ GROSZEWSKI, PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51290, 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.133.0.0/21 No ROA RIR databaseRIPE 673 100% 66
91.206.26.0/23 No ROA RIR databaseRIPE 673 100% 66
91.206.26.0/24 No ROA RIR databaseRIPE 673 100% 67
91.206.27.0/24 No ROA RIR databaseRIPE 673 100% 67
91.207.168.0/23 No ROA RIR databaseRIPE 673 100% 66
91.224.220.0/23 No ROA RIR databaseRIPE 673 100% 66
91.224.220.0/24 No ROA RIR databaseRIPE 673 100% 67
91.224.221.0/24 No ROA RIR databaseRIPE 673 100% 67
178.217.184.0/21 No ROA RIR databaseRIPE 673 100% 66
2001:67c:2044::/48 No ROA RIR databaseRIPE 635 100% 69
2001:67c:d94::/48 No ROA RIR databaseRIPE 634 100% 67
91.216.191.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS51290: RIPE::AS-HOSTEAM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS51290 isn't in the set, or no route object for AS51290 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS51290 in itNot covered
RIPE::AS-HOSTEAM RIPE 282244 Yes 0

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: none12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none31.133.0.0/21No ROA covers it. Add a ROA for AS51290, maxLength 21.673 of 673
ROA: none91.206.26.0/23No ROA covers it. Add a ROA for AS51290, maxLength 23.673 of 673
ROA: none91.206.26.0/24No ROA covers it. Add a ROA for AS51290, maxLength 24.673 of 673
ROA: none91.206.27.0/24No ROA covers it. Add a ROA for AS51290, maxLength 24.673 of 673
ROA: none91.207.168.0/23No ROA covers it. Add a ROA for AS51290, maxLength 23.673 of 673
ROA: none91.224.220.0/23No ROA covers it. Add a ROA for AS51290, maxLength 23.673 of 673
ROA: none91.224.220.0/24No ROA covers it. Add a ROA for AS51290, maxLength 24.673 of 673
ROA: none91.224.221.0/24No ROA covers it. Add a ROA for AS51290, maxLength 24.673 of 673
ROA: none178.217.184.0/21No ROA covers it. Add a ROA for AS51290, maxLength 21.673 of 673
ROA: none2001:67c:2044::/48No ROA covers it. Add a ROA for AS51290, maxLength 48.635 of 636
ROA: none2001:67c:d94::/48No ROA covers it. Add a ROA for AS51290, maxLength 48.634 of 636
ROA: none91.216.191.0/24No ROA covers it. Add a ROA for AS51290, maxLength 24.2 of 673

Route objects not announced

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

91.223.142.0/24RIPENo 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.