bgpreport

Network · data from 2026-11-12

AS12417 DHH-AS Plus Hosting Grupa d.o.o.

Registry name: DHH-AS Plus Hosting Grupa d.o.o., HR · not in PeeringDB

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

Announced routes

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

46.174.136.0/24 Invalid: origin Other origin only 2 0%low visibility 2
46.174.137.0/24 Invalid: origin Other origin only 2 0%low visibility 2
91.234.46.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.160.0/20 Valid RIR databaseRIPE 671 100% 66
178.218.160.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.161.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.162.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.163.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.164.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.165.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.166.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.167.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.168.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.170.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.171.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.172.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.173.0/24 Valid RIR databaseRIPE 671 100% 66
185.220.24.0/22 Valid RIR databaseRIPE 671 100% 66
185.220.24.0/24 Valid RIR databaseRIPE 671 100% 66
185.220.25.0/24 Valid RIR databaseRIPE 671 100% 66
185.220.26.0/24 Valid RIR databaseRIPE 671 100% 66
185.220.27.0/24 Valid RIR databaseRIPE 671 100% 66
212.44.127.0/24 Valid RIR databaseRIPE 671 100% 66
178.218.174.0/24 Valid RIR databaseRIPE 668 99% 66
2a0b:ee41::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS12417 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: origin2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin46.174.136.0/24ROAs covering it name AS35779, not AS12417. If AS12417 should announce it, add a ROA for AS12417.2 of 673
Route object: none46.174.136.0/24Route objects for it name AS35779. Add a route object with origin AS12417 in the RIR database for the space.2 of 673
ROA: origin46.174.137.0/24ROAs covering it name AS35779, not AS12417. If AS12417 should announce it, add a ROA for AS12417.2 of 673
Route object: none46.174.137.0/24Route objects for it name AS35779. Add a route object with origin AS12417 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS12417 is announced.

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.