Data as of Nov 10, 2026

3.64.0.0/10

2 anonymizer addresses · <0.01% · Datacenter proxy

Amazon.com, Inc. · space held by Amazon Technologies Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
>99% of it
IPv4 market

Path

1 · Holder
record created Dec 20, 2017
2 · Leased from
not leased
3 · Announced by
AS16509 Amazon.com, Inc.
since Dec 2024 · 23 mo ago
4 · Use
Hosting
anonymizer space, operator not named

Lineage

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

3.64.0.0/10

From the registry to its use

  1. Dec 20, 2017
    Registry record
    Amazon Technologies Inc.
    Direct Allocation
    3.0.0.0/9
  2. Dec 7, 2024– today
    Announced
    AS16509 Amazon.com, Inc.
    Hosting

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeAnonymizer addressesHolderRPKI
3.64.0.0/12
since Oct 2020
AS16509Hosting1<0.01%Datacenter proxyAmazon Technologies Inc.
via A100 ROW GmbH
3.80.0.0/12
since Sep 2018
AS14618HostingAmazon Technologies Inc.
via Amazon Data Services Northern Virginia
3.96.0.0/15
since Mar 2020
AS16509HostingAmazon Technologies Inc.
via Amazon Data Services Canada
3.98.0.0/15
since Aug 2020
AS16509HostingAmazon Technologies Inc.
via Amazon Data Services Canada
3.101.0.0/16
since Jan 2020
AS16509HostingAmazon Technologies Inc.
via Amazon.com, Inc.
3.102.0.0/15
since Feb 2025
AS16509HostingAmazon Technologies Inc.
via Amazon Data Services New Zealand
3.104.0.0/14
since Oct 2018
AS16509HostingAmazon Technologies Inc.
via Amazon Corporate Services Pty Ltd
3.108.0.0/14
since Apr 2021
AS16509HostingAmazon Technologies Inc.
via Amazon Data Services India
3.112.0.0/14
since Aug 2018
AS16509HostingAmazon Technologies Inc.
via Amazon Data Services Japan
3.120.0.0/14
since Jul 2018
AS16509HostingAmazon Technologies Inc.
via A100 ROW GmbH
3.124.0.0/14
since Jan 2019
AS16509Hosting1<0.01%Datacenter proxyAmazon Technologies Inc.
via A100 ROW GmbH

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
3.0.0.0/98,388,608AT-88-ZAmazon Technologies Inc. (AT-88-Z) · USDirect AllocationDec 20, 2017trustandsafety@support.aws.com
└ 3.64.0.0/121,048,576AMAZON-FRAA100 ROW GmbH (RG-123) · DEReallocatedOct 22, 2020trustandsafety@support.aws.com
└ 3.64.1.216/298AWS-DRUVAunknown———
└ 3.64.95.16/298AWS-FRESHWORKSunknown———
└ 3.64.95.128/25128AWS-LARKunknown———
└ 3.64.226.128/298AWS-ORCA-SECURITYunknown———
└ 3.64.226.160/2816AWS-SAP-SEunknown———
└ 3.65.246.128/2732AWS-CLOUDERAunknown———
└ 3.67.7.128/25128AWS-TENABLEunknown———
└ 3.67.81.0/2732AWS-VIBER-MEDIAunknown———
└ 3.67.81.128/25128AWS-ELECTRONICARTSunknown———
└ 3.67.228.128/2664AWS-PROMETHEUS-GROUPunknown———
└ 3.68.188.168/304AWS-AWNunknown———
└ 3.68.251.128/2732AWS-AWNunknown———
└ 3.68.251.184/298AWS-AWNunknown———
└ 3.69.198.248/304AWS-AWNunknown———
└ 3.70.48.0/23512AWS-ELECTRONICARTSunknown———
└ 3.70.50.0/23512AWS-ELECTRONICARTSunknown———
└ 3.70.68.128/25128AWS-ELECTRONICARTSunknown———
└ 3.71.134.128/2732AWS-DTA-33unknown———
└ 3.76.129.0/2732AWS-LOOKOunknown———
└ 3.76.129.32/2816AWS-LOOKOunknown———
└ 3.77.207.0/25128AWS-CS-2828unknown———
└ 3.77.207.192/298AWS-AWNunknown———
└ 3.80.0.0/121,048,576AMAZON-IADAmazon Data Services Northern Virginia (ADSN-1) · USReallocatedAug 22, 2018trustandsafety@support.aws.com
└ 3.80.13.160/2732AWS-SCHELLMANunknown———
└ 3.80.20.0/25128AWS-TWILIO-INCunknown———
└ 3.91.171.0/298AWS-IDGUARDunknown———
└ 3.91.171.8/298AWS-AKAMAIunknown———
└ 3.91.171.32/298AWS-NETFLIX-INCunknown———
└ 3.91.171.40/298AWS-NETFLIX-INCunknown———
└ 3.91.171.48/298AWS-NETFLIX-INCunknown———
└ 3.91.171.56/298AWS-NETFLIX-INCunknown———
└ 3.91.171.64/2816AWS-FRESHWORKSunknown———
└ 3.91.171.120/298AWS-TENABLEunknown———
└ 3.93.93.0/24256AWS-FIREEYEunknown———
└ 3.93.157.0/24256AWS-HUBSPOTunknown———
└ 3.93.158.128/25128AWS-PLIVOunknown———
└ 3.95.40.0/24256AWS-COUPAunknown———
└ 3.95.98.0/23512AWS-VEEVAunknown———
└ 3.96.0.0/15131,072AMAZON-YULAmazon Data Services Canada (ADSC-5) · CAReallocatedApr 1, 2020trustandsafety@support.aws.com
└ 3.96.143.96/2732AWS-F5-SILVERLINEunknown———
└ 3.96.247.44/304AWS-AWNunknown———
└ 3.97.17.192/2816AWS-AWNunknown———
└ 3.97.17.224/298AWS-AWNunknown———
└ 3.97.99.32/2732AWS-CLOUDMARKunknown———
└ 3.97.207.0/24256AWS-FIREEYEunknown———
└ 3.97.208.0/24256AWS-FIREEYEunknown———
└ 3.98.0.0/15131,072AMAZON-YULAmazon Data Services Canada (ADSC-5) · CAReallocatedAug 6, 2020trustandsafety@support.aws.com
└ 3.98.24.112/2816AWS-AWNunknown———
└ 3.98.24.248/298AWS-ATLASSIANunknown———
└ 3.98.92.0/25128AWS-TENABLEunknown———
└ 3.98.171.0/2664AWS-PROMETHEUS-GROUPunknown———
└ 3.99.123.196/304AWS-AWNunknown———
└ 3.101.0.0/1665,536AMAZON-SFOAmazon.com, Inc. (AMAZO-48) · USReallocatedJan 30, 2020trustandsafety@support.aws.com
└ 3.101.32.0/25128AWS-LARKunknown———
└ 3.101.32.128/25128AWS-ZOOMunknown———
└ 3.101.70.0/25128AWS-CISCO-WEBEXunknown———
└ 3.101.84.0/24256AWS-NGA911unknown———
└ 3.101.156.80/2816AWS-DRUVAunknown———
└ 3.101.175.128/2732AWS-VIBER-MEDIAunknown———
└ 3.101.196.208/2816AWS-UT-33unknown———
└ 3.101.196.224/2816AWS-UT-33unknown———
└ 3.101.196.240/2816AWS-UT-33unknown———
└ 3.101.201.0/25128AWS-FREEWHEELunknown———
└ 3.102.0.0/15131,072AMAZON-AKLAmazon Data Services New Zealand (ADSNZ) · NZReallocatedSep 16, 2024trustandsafety@support.aws.com
└ 3.104.0.0/14262,144AMAZO-SYDAmazon Corporate Services Pty Ltd (ACSPL-2) · AUReallocatedNov 1, 2018trustandsafety@support.aws.com
└ 3.104.34.0/298AWS-GLANCEunknown———
└ 3.104.34.32/2732AWS-OKTAunknown———
└ 3.104.208.0/23512AWS-PALOALTOunknown———
└ 3.105.5.96/2732AWS-SPORTSBETunknown———
└ 3.106.118.128/25128AWS-TENABLEunknown———
└ 3.108.0.0/14262,144AMAZON-BOMAmazon Data Services India (ADSI-6) · INReallocatedApr 7, 2021trustandsafety@support.aws.com
└ 3.108.37.0/24256AWS-TENABLEunknown———
└ 3.110.59.128/2664AWS-TRENDMICROunknown———
└ 3.110.59.192/2664AWS-TRENDMICROunknown———
└ 3.110.71.192/2664AWS-TRENDMICROunknown———
└ 3.112.0.0/14262,144AMAZON-NRTAmazon Data Services Japan (AMAZO-49) · JPReallocatedJul 11, 2018trustandsafety@support.aws.com
└ 3.112.23.16/2816AWS-HDEunknown———
└ 3.112.23.32/2732AWS-HDEunknown———
└ 3.112.23.64/2664AWS-DERBYSOFTunknown———
└ 3.112.23.128/2732AWS-SONY-IEunknown———
└ 3.112.23.160/304AWS-AVATUREunknown———
└ 3.112.23.168/298AWS-SECUREWORKSunknown———
└ 3.112.85.0/2664AWS-VEEVAunknown———
└ 3.112.85.80/298AWS-VIBER-MEDIAunknown———
└ 3.112.85.128/25128AWS-KDDIunknown———
└ 3.112.99.0/24256AWS-FIREEYEunknown———
└ 3.112.100.0/25128AWS-FIREEYEunknown———
└ 3.112.100.128/25128AWS-FIREEYEunknown———
└ 3.113.218.160/2816AWS-SKYSCANNER-LTDunknown———
└ 3.120.0.0/14262,144AMAZO-ZFRAA100 ROW GmbH (RG-123) · DEReallocatedJun 27, 2018trustandsafety@support.aws.com
└ 3.120.121.128/2664AWS-PLIVOunknown———
└ 3.120.121.192/2664AWS-ZUORAunknown———
└ 3.120.181.16/2816AWS-SAP-SEunknown———
└ 3.120.181.48/2816AWS-IHSMARKITunknown———
└ 3.120.181.64/2732AWS-TIBCOunknown———
└ 3.120.181.160/298AWS-CVENTunknown———
└ 3.120.181.168/298AWS-AKAMAIunknown———
└ 3.120.181.192/2816AWS-FRESHWORKSunknown———
└ 3.120.181.208/2816AWS-MODIXunknown———
└ 3.121.120.0/221,024AWS-RINGRing.com (C07238944) · USReassignedOct 30, 2018trustandsafety@support.aws.com
via AMAZO-ZFRA
└ 3.122.63.0/25128AWS-FIREEYEunknown———
└ 3.122.63.128/25128AWS-FIREEYEunknown———
└ 3.122.132.192/2664AWS-OKTAunknown———
└ 3.123.5.0/24256AWS-FIREEYEunknown———
└ 3.123.7.0/24256AWS-VEEVAunknown———
└ 3.123.44.192/2732AWS-COUPAunknown———
└ 3.123.44.224/2816AWS-SKYSCANNER-LTDunknown———
└ 3.123.44.240/298AWS-FRESHWORKSunknown———
└ 3.123.44.248/298AWS-ONTRADEunknown———
└ 3.124.0.0/14262,144AMAZO-ZFRAA100 ROW GmbH (RG-123) · DEReallocatedDec 13, 2018trustandsafety@support.aws.com
└ 3.124.123.128/25128AWS-TENABLEunknown———
└ 3.126.60.0/2732AWS-COUPAunknown———
└ 3.127.194.0/25128AWS-LARKunknown———

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,194,304 addresses
TypeAddressesShareRanges
Hosting4,194,302>99%379
Datacenter proxyanonymizer2<0.01%2

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2024
Current origin since
Dec 2024 · 1.9 yr
Origin networks
1