LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

64.64.121.0/24

No anonymizer space · no proxy exits in 30 days

Datacamp Limited · space held by LogicWeb Inc.

Announcement
this exact prefix
RPKI valid
Announced by
AS212238
Type
Hosting
Risk
50 / 100 · Medium
Recently moved
Recent change
New origin May 2026
from AS206092 F.N.S. Holdings Limited
IPv4 market

Path

Announced by AS212238 since May 2026 · 5 mo ago
1 · Holder
LogicWeb Inc.
record created Apr 6, 2010
2 · Leased from
LogicWeb
3 · Announced by
AS212238 Datacamp Limited
since May 2026 · 5 mo ago
4 · Use
Hosting

Lineage

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

64.64.121.0/24

From the registry to its use

  1. Apr 6, 2010
    Registry record
    LogicWeb Inc.
    Direct Allocation
    64.64.96.0/19
  2. Dec 1, 2013– Oct 1, 2015
    Announced
    AS12025 Iron Mountain Data Center
    Hosting
  3. Jan 1, 2016– Apr 11, 2017
    Announced
    AS36351 IBM Cloud
    Hosting
  4. Jul 21, 2017
    Route object
    AS206092 F.N.S. Holdings Limited
    ARIN route object for AS206092 F.N.S. Holdings Limited, maintainer MNT-LOGIC-25
  5. Apr 7, 2018– Jan 26, 2020
    Announced
    AS36351 IBM Cloud
    Hosting
  6. Jan 27, 2020– May 18, 2026
    Announced
    AS206092 F.N.S. Holdings Limited
    Hosting
  7. May 31, 2026– today
    Announced
    AS212238 Datacamp Limited
    Hosting
  8. Jun 9, 2026
    Route object
    AS212238 Datacamp Limited
    ARIN route object for AS212238 Datacamp Limited, maintainer MNT-LOGIC-25
  9. today
    Leased from
    LogicWeb
    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
64.64.96.0/198,192LOGICWEBLogicWeb Inc. (LOGIC-25) · USDirect AllocationApr 6, 2010abuse@logicweb.com
└ 64.64.121.0/281664-64-121-0-28-VPN-CONSUMER-BDunknown———
└ 64.64.121.16/281664-64-121-16-28-VPN-CONSUMER-BTunknown———
└ 64.64.121.32/281664-64-121-32-28-VPN-CONSUMER-BNunknown———
└ 64.64.121.48/281664-64-121-48-28-VPN-CONSUMER-CNunknown———
└ 64.64.121.64/281664-64-121-64-28-VPN-CONSUMER-KHunknown———
└ 64.64.121.80/281664-64-121-80-28-VPN-CONSUMER-IDunknown———
└ 64.64.121.96/281664-64-121-96-28-VPN-CONSUMER-THunknown———
└ 64.64.121.112/281664-64-121-112-28-VPN-CONSUMER-MOunknown———
└ 64.64.121.128/281664-64-121-128-28-VPN-CONSUMER-MYunknown———
└ 64.64.121.144/281664-64-121-144-28-VPN-CONSUMER-MNunknown———
└ 64.64.121.160/281664-64-121-160-28-VPN-CONSUMER-MMunknown———
└ 64.64.121.176/281664-64-121-176-28-VPN-CONSUMER-NPunknown———
└ 64.64.121.192/281664-64-121-192-28-VPN-CONSUMER-VNunknown———
└ 64.64.121.208/281664-64-121-208-28-VPN-CONSUMER-TWunknown———
└ 64.64.121.224/29864-64-121-224-29-VPN-CONSUMER-LAunknown———
└ 64.64.121.232/29864-64-121-232-29-VPN-CONSUMER-KZunknown———
└ 64.64.121.240/29864-64-121-240-29-VPN-CONSUMER-LKunknown———
└ 64.64.121.248/29864-64-121-248-29-VPN-CONSUMER-PKunknown———

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Dec 2013
Current origin since
May 2026 · 5 mo
Origin networks
4
Last change of origin
May 2026
Recorded history

History

Handoffs
3