Network · data from 2026-11-12

AS20875 HPTNET-AS JP HT d.d. Mostar

Registry name: HPTNET-AS JP HT d.d. Mostar, BA · not in PeeringDB

34IPv4 routes 97.1% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS20875, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20875, 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.


185.98.0.0/22	No ROA	RIR databaseRIPE	671 100%	68
5.133.128.0/19	Valid	RIR databaseRIPE	671 100%	68
37.8.128.0/20	Valid	RIR databaseRIPE	671 100%	68
46.35.128.0/19	Valid	RIR databaseRIPE	671 100%	68
62.113.0.0/19	Valid	RIR databaseRIPE	671 100%	68
85.94.128.0/19	Valid	RIR databaseRIPE	671 100%	68
92.240.32.0/21	Valid	RIR databaseRIPE	671 100%	68
92.240.40.0/22	Valid	RIR databaseRIPE	671 100%	68
92.240.44.0/22	Valid	RIR databaseRIPE	671 100%	68
92.240.48.0/20	Valid	RIR databaseRIPE	671 100%	68
95.156.128.0/21	Valid	RIR databaseRIPE	671 100%	68
95.156.136.0/21	Valid	RIR databaseRIPE	671 100%	68
95.156.144.0/20	Valid	RIR databaseRIPE	671 100%	68
95.156.160.0/20	Valid	RIR databaseRIPE	671 100%	68
95.156.176.0/21	Valid	RIR databaseRIPE	671 100%	68
95.156.184.0/21	Valid	RIR databaseRIPE	671 100%	68
159.20.16.0/22	Valid	RIR databaseRIPE	671 100%	68
159.20.20.0/22	Valid	RIR databaseRIPE	671 100%	68
185.17.44.0/22	Valid	RIR databaseRIPE	671 100%	68
185.24.160.0/22	Valid	RIR databaseRIPE	671 100%	68
185.38.144.0/22	Valid	RIR databaseRIPE	671 100%	68
212.39.96.0/19	Valid	RIR databaseRIPE	671 100%	68
212.39.99.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.100.0/22	Valid	RIR databaseRIPE	671 100%	68
212.39.104.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.110.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.111.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.117.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.118.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.119.0/24	Valid	RIR databaseRIPE	671 100%	68
212.39.122.0/24	Valid	RIR databaseRIPE	671 100%	68
212.125.144.0/20	Valid	RIR databaseRIPE	671 100%	68
212.125.144.0/21	Valid	RIR databaseRIPE	671 100%	68
212.125.152.0/21	Valid	RIR databaseRIPE	668 99%	68

AS-SET

AS20875 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 4 are in fix.csv.

ROA: none1
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.98.0.0/22	No ROA covers it. Add a ROA for AS20875, maxLength 22.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.98.0.0/22

No ROA covers it. Add a ROA for AS20875, maxLength 22.

671 of 673

Route objects not announced

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


37.19.24.0/21	RIPE	Valid
95.156.128.0/20	RIPE	Valid
212.47.45.0/24	RIPE	Valid

37.19.24.0/21

RIPE

Valid

95.156.128.0/20

RIPE

Valid

212.47.45.0/24

RIPE

Valid

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.