Data as of Nov 14, 2026

45.250.24.0/24

No anonymizer space · no proxy exits in 30 days

Clouvider Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contactRIR
45.250.24.0/221,024RIPENCCunknown———ARIN
└ 45.250.24.0/221,024UK-CLOUVIDER-20160516Clouvider Limited (ORG-CL248-RIPE) · GBALLOCATED PAMay 29, 2018abuse@clouvider.netRIPE NCC
└ 45.250.24.0/24256CLOUVIDER-NYC2New York NetworkLIR-PARTITIONED PAJun 19, 2022abuse@clouvider.net
via RIPENCC
RIPE NCC
└ 45.250.24.128/2664CLOUVIDER-HB-CLIENT-9107Customer allocation HB Client 9107ASSIGNED PAOct 31, 2024abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.226/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAJan 18, 2024abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.227/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.228/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.229/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.230/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.231/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.232/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.233/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.234/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.235/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAAug 12, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.236/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAMay 10, 2023abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.237/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PASep 21, 2023abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.238/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PASep 21, 2023abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.242/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PASep 20, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.243/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PASep 20, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.244/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PASep 20, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC
└ 45.250.24.245/321CLOUVIDER-HB-CLIENT-272Customer allocation HB Client 272ASSIGNED PASep 20, 2022abuse@clouvider.net
via CLOUVIDER-NYC2
RIPE NCC

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2017
Current origin since
Aug 2022 · 4.3 yr
Origin networks
2
Last change of origin
Mar 2018
Recorded history

History

Handoffs
2