Data as of Nov 16, 2026

104.243.213.0/24

Anonymizer · Datacenter proxy3 residential-proxy exits · 30 days

M247 Europe SRL · space held by CloudIP LLC

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

33 observations
IPv4 market

Path

1 · Holder
record created Sep 28, 2016
2 · Leased from
its owner, directly
3 · Announced by
AS9009 M247 Europe SRL
since Jan 2026 · 10 mo ago
4 · Use
Proxy providersnamed Wired ISP
Datacenter proxy

Operators, sellers and brokers

Proxy providers

NameParentIn 104.243.213.0/24/24s
Wired ISP
256100%
1
Leased from

Owners leasing their own space

NameIn 104.243.213.0/24/24s
CloudIP LLC
256100%
1

Lineage

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

104.243.213.0/24

From the registry to its use

  1. Sep 28, 2016
    Registry record
    CloudIP LLC
    Direct Allocation
    104.243.208.0/21
  2. Nov 16, 2019– Dec 1, 2025
    Announced
    AS9009 M247 Europe SRL
    Hosting
  3. Nov 25, 2019
    Route object
    AS9009 M247 Europe SRL
    RADB route object for AS9009 M247 Europe SRL, maintainer MAINT-AS9009
  4. Dec 24, 2025
    Route object
    AS9009 M247 Europe SRL
    ARIN route object for AS9009 M247 Europe SRL, maintainer MNT-CL-970
  5. Jan 31, 2026
    Assigned
    Premio Digital-Belize
    Reassigned
    104.243.213.0/24
  6. Jan 31, 2026– today
    Announced
    AS9009 M247 Europe SRL
    Hosting
  7. today
    Used
    Wired ISP
    Proxy operator

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.243.208.0/212,048CLOUD-CONNECTCloudIP LLC (CL-970) · USDirect AllocationSep 28, 2016admin@gpuhosting.ai
└ 104.243.213.0/24256BELIZE-CITYPremio Digital-Belize (C11495063) · BZReassignedJan 31, 2026admin@gpuhosting.ai
via CLOUD-CONNECT

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
Stable
First seen
Nov 2019
Current origin since
Jan 2026 · 9 mo
Origin networks
1