AS204167 hyve Hyve Ltd

🇬🇧

Org handle: ORG-HL224-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

19total

15 IPv44 IPv6

IPv4 Addresses

Allocated (RIR)2,048

Announced (BGP)7,168

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)8.4×10²⁴

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2015-08-07

Announced Prefixes

(BGP)19

Prefix	RPKI	IRR	Last Seen
5.57.56.0/23	No ROA	RIPE	-
5.57.58.0/23	No ROA	RIPE	-
5.57.60.0/23	No ROA	-	-
5.57.62.0/23	No ROA	-	-
45.154.133.0/24	No ROA	RIPE	-
178.170.128.0/23	Valid	RIPE	-
185.35.248.0/23	No ROA	RIPE	-
185.35.250.0/23	No ROA	RIPE	-
185.76.44.0/24	No ROA	RIPE	-
185.161.26.0/23	No ROA	RIPE	-

1-10 of 19

1 / 2

(RIR)5

Prefix	Country	RIR	Status
45.154.133.0/24	🇮🇪 IE	RIPE	assigned
185.35.248.0/23	🇬🇧 GB	RIPE	assigned
185.35.250.0/23	🇬🇧 GB	RIPE	assigned
185.76.44.0/24	🇬🇧 GB	RIPE	assigned
185.225.162.0/23	🇬🇧 GB	RIPENCC	allocated

(seen in AS paths)

Networks AS204167 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

External Links

What is an ASN?Autonomous systems, ASN ranges and how they are assigned
RPKI and route origin validationWhat the RPKI badges on the prefix list mean
ASPA explainedWhy AS204167 should publish an ASPA object
IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/204167" | jq