Data as of Nov 21, 2026

212.165.52.0/24

8 residential-proxy exits · 30 days

INTRED S.p.A.

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
38
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

694 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • IPPeak
  • IPRoyal
  • Infatica
  • KindProxy
  • LOKIPROXY
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.165.32.0/19
since Aug 2016
AS41497Residential138
2 always on
INTRED S.p.A.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.165.32.0/198,192IT-INTRED-20020501INTRED S.p.A. (ORG-IS25-RIPE) · ITALLOCATED PAMay 2, 2002abuse@intred.it
└ 212.165.52.0/23512QCOM_IT-NETWORKIP Pubblici per Backup CVASSIGNED PAJan 15, 2015abuse@intred.it
via IT-INTRED-20020501

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

Covering aggregate above, the prefix's own history below

212.165.48.0/21

Routing history

Pattern
Stable
First seen
May 2017
Current origin since
May 2024 · 2.5 yr
Origin networks
1