bgpreport

Network · data from 2026-11-12

AS42655 BESTHOSTING-AS ON-LINE Ltd

Registry name: BESTHOSTING-AS ON-LINE Ltd, UA · not in PeeringDB

21IPv4 routes 19.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
17No 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 AS42655, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42655, 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.41.216.0/21 No ROA RIR databaseRIPE 671 100% 68
31.41.216.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.217.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.218.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.219.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.220.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.221.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.222.0/24 No ROA RIR databaseRIPE 671 100% 68
31.41.223.0/24 No ROA RIR databaseRIPE 671 100% 68
194.28.172.0/22 No ROA RIR databaseRIPE 671 100% 68
194.28.172.0/24 No ROA RIR databaseRIPE 671 100% 68
194.28.173.0/24 No ROA RIR databaseRIPE 671 100% 68
194.28.174.0/24 No ROA RIR databaseRIPE 671 100% 68
194.28.175.0/24 No ROA RIR databaseRIPE 671 100% 68
195.248.234.0/23 No ROA RIR databaseRIPE 671 100% 68
195.248.234.0/24 No ROA RIR databaseRIPE 671 100% 68
195.248.235.0/24 No ROA RIR databaseRIPE 671 100% 68
91.199.45.0/24 Valid RIR databaseRIPE 673 100% 66
91.235.128.0/24 Valid RIR databaseRIPE 673 100% 66
185.237.204.0/23 Valid RIR databaseRIPE 673 100% 66
195.54.163.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS42655 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 20 are in fix.csv.

  • ROA: none17
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none31.41.216.0/21No ROA covers it. Add a ROA for AS42655, maxLength 21.671 of 673
ROA: none31.41.216.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.217.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.218.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.219.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.220.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.221.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.222.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none31.41.223.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none194.28.172.0/22No ROA covers it. Add a ROA for AS42655, maxLength 22.671 of 673
ROA: none194.28.172.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none194.28.173.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none194.28.174.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none194.28.175.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none195.248.234.0/23No ROA covers it. Add a ROA for AS42655, maxLength 23.671 of 673
ROA: none195.248.234.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673
ROA: none195.248.235.0/24No ROA covers it. Add a ROA for AS42655, maxLength 24.671 of 673

Route objects not announced

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

2001:67c:2224::/48RIPENo ROA
2a03:1240:1::/48RIPEValid
2a06:c6c0:1::/48RIPEValid

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.