Data as of Nov 17, 2026

104.234.166.0/24

No anonymizer space · no proxy exits in 30 days

Secured Servers LLC · space held by Velcom

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

Path

1 · Holder
record created Oct 27, 2014 · reallocated to Internet Utilities NA LLC Jan 7, 2025
2 · Leased from
3 · Announced by
AS19437 Secured Servers LLC
since Jun 2022 · 4.4 yr ago
4 · Use
Hosting

Lineage

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

104.234.166.0/24

From the registry to its use

  1. Oct 27, 2014
    Registry record
    Velcom
    Direct Allocation
    104.234.0.0/16
  2. Feb 21, 2022– Jun 20, 2022
    Announced
    AS1239 Cogent Communications, LLC
  3. Jun 9, 2022– today
    Announced
    AS19437 Secured Servers LLC
    Hosting
  4. Sep 10, 2022
    Route object
    IPXO
    RADB route object for AS19437 Secured Servers LLC, maintainer MAINT-AS834
  5. Jan 7, 2025
    Reallocated
    Internet Utilities NA LLC
    Reallocated
    104.234.160.0/21
  6. Jan 7, 2025
    Assigned
    Internet Utilities NA LLC
    Reassigned
    104.234.166.0/24
  7. Jan 7, 2025
    Route object
    IPXO
    ARIN route object for AS1239 Cogent Communications, LLC, maintainer MNT-DCL-577
  8. Jan 7, 2025
    Route object
    IPXO
    ARIN route object for AS19437 Secured Servers LLC, maintainer MNT-DCL-577
  9. 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
104.234.0.0/1665,536VELCOM-16Velcom (ONTAR-40) · CADirect AllocationOct 27, 2014abuse@velcom.com
└ 104.234.160.0/212,048IL-845IPXO LLC (IL-845) · USReallocatedJan 28, 2022abuse@ipxo.com
└ 104.234.160.0/212,048NETUTILSInternet Utilities NA LLC (DCL-577) · USReallocatedJan 7, 2025report@abuseradar.com
└ 104.234.166.0/24256AMG-BROADBAND-TELECOM-LLCunknownReassignedJan 7, 2025report@abuseradar.com
via IL-845

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
Feb 2022
Current origin since
Jun 2022 · 4.4 yr
Origin networks
2
Last change of origin
Jun 2022
Recorded history

History

Handoffs
1