HOS-176601

Data as of 2026-10-25

BGP inherited

This organisation

Netblocks	22
IPv6	22 prefixes (largest 2a01:4f8:10a:1782::/64)
Record ID	257215928
Registry	RIPE
Customers	see who runs inside this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (22)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2a01:4f8:a0:221b::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:a0:315b::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:a0:8113::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:10a:1782::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:10b:1d94::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:13a:69d::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:150:3090::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:151:60c7::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:160:118b::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:162:6230::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:172:f06::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:172:165f::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:173:21c3::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:173:2a64::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:200:5469::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:202:310::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:212:2b16::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:212:3059::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:222:1248::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:262:4816::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f8:272:4d21::/64	HOS-176601	RIPE	ASSIGNED	● low
2a01:4f9:3080:25ac::/64	HOS-176601	RIPE	ASSIGNED	● low

18 weekly snapshots · JSON

22 -1 netblocks since 2026-07-05

2026-07-05 peak 23 2026-10-25

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (22 of 22)

No discrepancies found among checked blocks.

DUMY-RIPE DUMY-RIPE HOS-GUN