Data as of Nov 12, 2026

166.0.130.0/24

No anonymizer space · no proxy exits in 30 days

BreezeHost · space held by Ace Data Centers, Inc.

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

Path

1 · Holder
record created Jul 10, 2012 · reallocated to Internet Utilities NA LLC Jan 27, 2025
2 · Leased from
3 · Announced by
AS400810 BreezeHost
since Dec 2022 · 3.9 yr ago
4 · Use
Hosting

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

166.0.130.0/24

From the registry to its use

  1. Jul 10, 2012
    Registry record
    Ace Data Centers, Inc.
    Direct Allocation
    166.0.0.0/15
  2. Jun 14, 2021– Nov 11, 2022
    Announced
    AS62240 Clouvider Limited
    Hosting
  3. Nov 12, 2022– Nov 23, 2022
    Announced
    AS46573 Vault Host
    Hosting
  4. Nov 12, 2022– Dec 17, 2022
    Announced
    AS35913 DediPath
  5. Dec 18, 2022– today
    Announced
    AS400810 BreezeHost
    Hosting
  6. Dec 22, 2022
    Route object
    IPXO
    RADB route object for AS400810 BreezeHost, maintainer MAINT-AS834
  7. Jan 27, 2025
    Reallocated
    Internet Utilities NA LLC
    Reallocated
    166.0.130.0/24
  8. Jan 27, 2025
    Route object
    IPXO
    ARIN route object for AS400810 BreezeHost, maintainer MNT-DCL-577
  9. today
    Leased from
    Ace Data Centers
    IP broker
  10. today
    Leased from
    IPXO
    IP broker

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 contact
166.0.0.0/15131,072ACE-NETWORK-10Ace Data Centers, Inc. (ADC-96) · USDirect AllocationJul 10, 2012ipabuse@acedatacenter.com
└ 166.0.130.0/24256IPXOIPXO LLC (IL-845) · USReallocatedJan 27, 2025abuse@ipxo.com
└ 166.0.130.0/24256NETUTILSInternet Utilities NA LLC (DCL-577) · USReallocatedJan 27, 2025report@abuseradar.com
└ 166.0.130.0/24256BREEZEHOSTBreezeHost (C11081733) · USReassignedJan 27, 2025report@abuseradar.com
via IPXO

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
Rotating
First seen
Jun 2021
Current origin since
Dec 2022 · 3.9 yr
Origin networks
4
Last change of origin
Dec 2022
Recorded history

History

Handoffs
3