Data as of Nov 20, 2026

104.145.219.0/24

No anonymizer space · no proxy exits in 30 days

Nazim Host · space held by VirtuDataCenter, Inc.

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

Path

1 · Holder
VirtuDataCenter, Inc.
record created Sep 10, 2014 · reallocated to Internet Utilities NA LLC Oct 13, 2025
2 · Leased from
3 · Announced by
AS153383 Nazim Host
since Mar 2026 · 8 mo ago
4 · Use
Hosting

Lineage

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

104.145.219.0/24

From the registry to its use

  1. Sep 10, 2014
    Registry record
    VirtuDataCenter, Inc.
    Direct Allocation
    104.145.208.0 - 104.145.219.255
  2. Feb 8, 2020– Feb 19, 2020
    Announced
    AS36747 VirtuDataCenter, Inc.
  3. Oct 13, 2025
    Reallocated
    Internet Utilities NA LLC
    Reallocated
    104.145.216.0/22
  4. Mar 8, 2026– today
    Announced
    AS153383 Nazim Host
    Hosting
  5. Mar 12, 2026
    Assigned
    Internet Utilities NA LLC
    Reassigned
    104.145.219.0/24
  6. Mar 12, 2026
    Route object
    IPXO
    RADB route object for AS153383 Nazim Host, maintainer MAINT-AS834
  7. Mar 12, 2026
    Route object
    IPXO
    ARIN route object for AS153383 Nazim Host, maintainer MNT-DCL-577
  8. 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.145.208.0 - 104.145.219.2553,072VIRTUDATACENTERVirtuDataCenter, Inc. (VIRTU-74) · USDirect AllocationSep 10, 2014—
└ 104.145.216.0/221,024SWC-22IPXO LLC (IL-845) · USReallocatedOct 13, 2025abuse@ipxo.com
└ 104.145.216.0/221,024NETUTILSInternet Utilities NA LLC (DCL-577) · USReallocatedOct 13, 2025report@abuseradar.com
└ 104.145.219.0/24256NET-104-145-219-0-24unknownReassignedMar 12, 2026report@abuseradar.com
via SWC-22

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
Reactivated
First seen
Feb 2020
Current origin since
Mar 2026 · 8 mo
Origin networks
2
Last change of origin
Mar 2026
Recorded history

History

Handoffs
1