Data as of Nov 13, 2026

31.171.136.0/24

42 residential-proxy exits · 30 days

INTRED S.p.A.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
42
16% of its addresses · 30 days
Always-on exits
3
7.1% of its exits
Providers
61
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

16K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonPrime
  • MagneticProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYON
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxying
  • Proxyma
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.171.136.0/22
since May 2011
AS31115Residential47
4 always on
INTRED S.p.A.
31.171.136.0/21
since May 2011
AS31115Residential104
10 always on
INTRED S.p.A.

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
31.171.136.0/212,048IT-INTRED-20110331INTRED S.p.A. (ORG-IS25-RIPE) · ITALLOCATED PAMar 31, 2011abuse@intred.it
└ 31.171.136.0/24256INTRED-xDSL-L-NAT-RESIDENTIAL-NET-B01Infrastructure IP addresses for residential customer, NAT, public subnetASSIGNED PAAug 27, 2019abuse@intred.it
via IT-INTRED-20110331

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

Summary

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.6 yr
Origin networks
1