Data as of Nov 18, 2026

166.88.120.0/24

No anonymizer space · no proxy exits in 30 days

Amazon.com, Inc. · space held by Ace Data Centers II, L.L.C.

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

Path

1 · Holder
record created Oct 26, 2012
2 · Leased from
3 · Announced by
AS16509 Amazon.com, Inc.
since Sep 2024 · 2.2 yr ago
4 · Use
Hosting

Lineage

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

166.88.120.0/24

From the registry to its use

  1. Oct 26, 2012
    Registry record
    Ace Data Centers II, L.L.C.
    Direct Allocation
    166.88.0.0/16
  2. Jun 13, 2019– Jun 24, 2019
    Announced
    AS174 Cogent Communications, LLC
    Internet provider
  3. Aug 1, 2021– Aug 12, 2021
    Announced
    AS18779 EGIHosting
    Hosting
  4. Aug 28, 2024
    Assigned
    Share2f
    Reassigned
    166.88.120.0/24
  5. Aug 28, 2024
    Route object
    AS14618 Amazon.com, Inc.
    ARIN route object for AS14618 Amazon.com, Inc., maintainer MNT-ADCIL
  6. Aug 28, 2024
    Route object
    AS16509 Amazon.com, Inc.
    ARIN route object for AS16509 Amazon.com, Inc., maintainer MNT-ADCIL
  7. Sep 2, 2024– today
    Announced
    AS16509 Amazon.com, Inc.
    Hosting
  8. Sep 6, 2024
    Route object
    AS16509 Amazon.com, Inc.
    RADB route object for AS16509 Amazon.com, Inc., maintainer MAINT-AS16509
  9. today
    Leased from
    Ace Data Centers
    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.88.0.0/1665,536ADCILAce Data Centers II, L.L.C. (ADCIL) · USDirect AllocationOct 26, 2012ipabuse@acedatacenter.com
└ 166.88.120.0/24256SHARE2F-NETWORKShare2f (C10941425) · MYReassignedAug 28, 2024ipabuse@acedatacenter.com
via ADCIL

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
Jun 2019
Current origin since
Sep 2024 · 2.2 yr
Origin networks
3
Last change of origin
Sep 2024
Recorded history

History

Handoffs
2