Data as of Nov 19, 2026

23.234.148.0/22

Anonymizer · Datacenter proxy

Inter Data Link Inc · space held by Digital Landscape, Inc.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Datacenter proxy
Risk
85 / 100 · Critical
IPv4 market

Path

1 · Holder
record created Oct 9, 2013 · reallocated to hypebeastservers Jul 26, 2023
2 · Leased from
not leased
3 · Announced by
AS399091 Inter Data Link Inc
since Sep 2023 · 3.2 yr ago
4 · Use
Proxy providersnamed MyPrivateProxy
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 23.234.148.0/22/24s
MyPrivateProxy
1,024100%
4

Lineage

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

23.234.148.0/22

From the registry to its use

  1. Oct 9, 2013
    Registry record
    Digital Landscape, Inc.
    Direct Allocation
    23.234.128.0/18
  2. May 4, 2022– Jun 8, 2022
    Announced
    AS398712 Ispconnected Corp
    Hosting
  3. May 28, 2022– Aug 2, 2023
    Announced
    AS399150 ispexchangecorp
    Hosting
  4. Jul 22, 2023– Sep 7, 2023
    Announced
    AS398436 hypebeastservers
    Hosting
  5. Jul 26, 2023
    Reallocated
    hypebeastservers
    Reallocated
    23.234.148.0/22
  6. Sep 8, 2023– today
    Announced
    AS399091 Inter Data Link Inc
    Hosting
  7. Aug 24, 2026
    Route object
    AS399091 Inter Data Link Inc
    ARIN route object for AS399091 Inter Data Link Inc, maintainer MNT-DIGIT-215
  8. today
    Used
    MyPrivateProxy
    Proxy seller

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
23.234.128.0/1816,384DL-ARIN06Digital Landscape, Inc. (DIGIT-215) · USDirect AllocationOct 9, 2013abuse@digitallandscape.com
└ 23.234.148.0/221,024HYPEBEASTSERVERShypebeastservers (WS-834) · USReallocatedJul 26, 2023abuse@hypebeastservers.com
└ 23.234.148.0/221,024ATLANTAAtlanta (C10904042) · USReassignedJul 18, 2024abuse@hypebeastservers.com
via HYPEBEASTSERVERS

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
May 2022
Current origin since
Sep 2023 · 3.2 yr
Origin networks
4
Last change of origin
Sep 2023
Recorded history

History

Handoffs
3