Network · data from 2026-11-12

AS203953 Hiper Hiper A/S

Registry name: Hiper Hiper A/S, DK · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS203953, seen from no peer

Announced routes

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


2.110.64.0/18	Valid	RIR databaseRIPE	673 100%	67
2.110.128.0/17	Valid	RIR databaseRIPE	673 100%	67
80.210.64.0/20	Valid	RIR databaseRIPE	673 100%	67
89.150.128.0/18	Valid	RIR databaseRIPE	673 100%	67
90.184.0.0/15	Valid	RIR databaseRIPE	673 100%	67
185.15.72.0/22	Valid	RIR databaseRIPE	673 100%	67
185.50.192.0/22	Valid	RIR databaseRIPE	673 100%	67
185.118.248.0/22	Valid	RIR databaseRIPE	673 100%	67
185.181.220.0/22	Valid	RIR databaseRIPE	673 100%	67
195.192.232.0/22	Valid	RIR databaseRIPE	673 100%	67
212.237.128.0/20	Valid	RIR databaseRIPE	673 100%	67
213.32.240.0/21	Valid	RIR databaseRIPE	673 100%	67
217.61.216.0/21	Valid	RIR databaseRIPE	673 100%	67
2a05:f6c0::/29	Valid	RIR databaseRIPE	634 100%	68

AS-SET

AS203953 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS203953 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.