LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

45.250.25.0/24

No anonymizer space · no proxy exits in 30 days

Clouvider Limited

Announcement
this exact prefix
RPKI valid
Announced by
AS62240
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.25.0/24256US-CLOUVIDER-ASHUS - Ashburn, VA NetworkSUB-ALLOCATED PAJul 30, 2021abuse@clouvider.net
via RIPENCC
RIPE NCC
└ 45.250.25.6/312CLOUVIDER-HB-CLIENT-2369Customer allocation HB Client 2369ASSIGNED PAOct 22, 2021abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.8/298CLOUVIDER-HB-CLIENT-2384Customer allocation HB Client 2384ASSIGNED PADec 3, 2021abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.32/298CLOUVIDER-HB-CLIENT-16168Customer allocation HB Client 16168ASSIGNED PAOct 28, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.42/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAOct 22, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.43/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAOct 22, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.44/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAOct 22, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.45/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAOct 22, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.46/321CLOUVIDER-HB-CLIENT-2404Customer allocation HB Client 2404ASSIGNED PAOct 22, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.48/298PACKETHUB-20211124-ASHPackethub S.A. (ORG-PS433-RIPE)ASSIGNED PANov 25, 2021abuse@packethub.techRIPE NCC
└ 45.250.25.56/298CLOUVIDER-HB-CLIENT-9774Customer allocation HB Client 9774ASSIGNED PADec 5, 2024abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.64/2732PACKETHUB-20211124-ASHPackethub S.A. (ORG-PS433-RIPE)ASSIGNED PANov 25, 2021abuse@packethub.techRIPE NCC
└ 45.250.25.96/298CLOUVIDER-HB-CLIENT-3944Customer allocation HB Client 3944ASSIGNED PANov 30, 2021abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.104/298CLOUVIDER-HB-CLIENT-16168Customer allocation HB Client 16168ASSIGNED PANov 4, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.112/2816CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 18, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.131/321CLOUVIDER-HB-CLIENT-15982Customer allocation HB Client 15982ASSIGNED PAOct 15, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.132/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 18, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.134/321CLOUVIDER-HB-CLIENT-3944Customer allocation HB Client 3944ASSIGNED PANov 30, 2021abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.135/321CLOUVIDER-HB-CLIENT-5228Customer allocation HB Client 5228ASSIGNED PAJan 6, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.136/321CLOUVIDER-HB-CLIENT-16037Customer allocation HB Client 16037ASSIGNED PAOct 19, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.138/321CLOUVIDER-HB-CLIENT-14065Customer allocation HB Client 14065ASSIGNED PAJun 4, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.139/321CLOUVIDER-HB-CLIENT-16158Customer allocation HB Client 16158ASSIGNED PAOct 27, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.140/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMay 3, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.141/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMay 5, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.142/321CLOUVIDER-HB-CLIENT-15700Customer allocation HB Client 15700ASSIGNED PASep 29, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.143/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMay 3, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.144/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAAug 5, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.145/321CLOUVIDER-HB-CLIENT-11310Customer allocation HB Client 11310ASSIGNED PAMay 8, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.146/321CLOUVIDER-HB-CLIENT-10736Customer allocation HB Client 10736ASSIGNED PAMar 3, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.148/321CLOUVIDER-HB-CLIENT-13643Customer allocation HB Client 13643ASSIGNED PASep 28, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.150/321CLOUVIDER-HB-CLIENT-10315Customer allocation HB Client 10315ASSIGNED PAJun 17, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.152/321CLOUVIDER-HB-CLIENT-2384Customer allocation HB Client 2384ASSIGNED PADec 3, 2021abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.153/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAAug 6, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.155/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMay 3, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.156/321CLOUVIDER-HB-CLIENT-14137Customer allocation HB Client 14137ASSIGNED PAApr 29, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.157/321CLOUVIDER-HB-CLIENT-15624Customer allocation HB Client 15624ASSIGNED PAOct 20, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.158/321CLOUVIDER-HB-CLIENT-14025Customer allocation HB Client 14025ASSIGNED PAApr 15, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.159/321CLOUVIDER-HB-CLIENT-16158Customer allocation HB Client 16158ASSIGNED PAOct 27, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.160/321CLOUVIDER-HB-CLIENT-16168Customer allocation HB Client 16168ASSIGNED PAOct 28, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.161/321CLOUVIDER-HB-CLIENT-16442Customer allocation HB Client 16442ASSIGNED PANov 10, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.162/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAApr 18, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.163/321CLOUVIDER-HB-CLIENT-14088Customer allocation HB Client 14088ASSIGNED PAApr 22, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.164/321CLOUVIDER-HB-CLIENT-14065Customer allocation HB Client 14065ASSIGNED PAApr 24, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.166/321CLOUVIDER-HB-CLIENT-9055Customer allocation HB Client 9055ASSIGNED PAOct 9, 2024abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.167/321CLOUVIDER-HB-CLIENT-16496Customer allocation HB Client 16496ASSIGNED PANov 13, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.168/321CLOUVIDER-HB-CLIENT-11310Customer allocation HB Client 11310ASSIGNED PAJul 2, 2025abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.169/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAApr 18, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.171/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAAug 6, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.172/321CLOUVIDER-HB-CLIENT-16511Customer allocation HB Client 16511ASSIGNED PANov 13, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.173/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAJul 12, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.174/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 18, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.175/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAJul 12, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.176/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAJul 12, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.177/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAJul 12, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.178/321CLOUVIDER-HB-CLIENT-9774Customer allocation HB Client 9774ASSIGNED PADec 5, 2024abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.179/321CLOUVIDER-HB-CLIENT-4368Customer allocation HB Client 4368ASSIGNED PAMar 25, 2022abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.180/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAApr 18, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.181/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAJul 12, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.182/321CLOUVIDER-HB-CLIENT-14065Customer allocation HB Client 14065ASSIGNED PAJul 17, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.183/321CLOUVIDER-HB-CLIENT-14065Customer allocation HB Client 14065ASSIGNED PAJul 18, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.184/321CLOUVIDER-HB-CLIENT-14065Customer allocation HB Client 14065ASSIGNED PAJul 17, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.185/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAAug 6, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.186/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAAug 6, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.187/321CLOUVIDER-HB-CLIENT-11252Customer allocation HB Client 11252ASSIGNED PAAug 6, 2026abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.200/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 15, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.201/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 15, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.209/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 15, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.231/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAFeb 15, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
RIPE NCC
└ 45.250.25.232/321CLOUVIDER-HB-CLIENT-3860Customer allocation HB Client 3860ASSIGNED PAMay 5, 2023abuse@clouvider.net
via US-CLOUVIDER-ASH
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2017
Current origin since
Jun 2021 · 5.4 yr
Origin networks
2
Last change of origin
Feb 2020
Recorded history

History

Handoffs
4