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

85.222.64.0/19

24 residential-proxy exits · 30 days

P4 Sp. z o.o.

Announcement
this exact prefix
RPKI valid
Announced by
AS9141
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
24
0.29% of its addresses · 30 days
Always-on exits
1
4.2% of its exits
Spread
18 of 32
/24s with at least one exit
Providers
62
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.222.82.0/2411
85.222.73.0/2403
85.222.80.0/2402
85.222.89.0/2402
85.222.67.0/2402
85.222.81.0/2402
85.222.86.0/2401
85.222.79.0/2401
85.222.68.0/2401
85.222.71.0/2401
85.222.87.0/2401
85.222.83.0/2401
85.222.88.0/2401
85.222.72.0/2401
85.222.91.0/2401
85.222.92.0/2401
85.222.94.0/2401
85.222.95.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
85.222.0.0/1732,768PL-UPC-20050214P4 Sp. z o.o. (ORG-UTKS1-RIPE) · PLALLOCATED PAFeb 14, 2005abuse@play.pl
└ 85.222.64.0/221,024PLAYPLAYASSIGNED PAOct 18, 2007abuse@play.pl
via PL-UPC-20050214
└ 85.222.68.0/221,024PLAYPLAYASSIGNED PANov 5, 2007abuse@play.pl
via PL-UPC-20050214
└ 85.222.72.0/221,024PLAYPLAYASSIGNED PANov 5, 2007abuse@play.pl
via PL-UPC-20050214
└ 85.222.76.0/221,024PLAYPLAYASSIGNED PANov 6, 2007abuse@play.pl
via PL-UPC-20050214
└ 85.222.80.0/221,024PLAYPLAYASSIGNED PADec 14, 2007abuse@play.pl
via PL-UPC-20050214
└ 85.222.84.0/24256PLAYPLAYASSIGNED PAFeb 13, 2008abuse@play.pl
via PL-UPC-20050214
└ 85.222.85.0/24256PLAYPLAYASSIGNED PAFeb 13, 2008abuse@play.pl
via PL-UPC-20050214
└ 85.222.86.0/24256PLAYPLAYASSIGNED PAJul 14, 2008abuse@play.pl
via PL-UPC-20050214
└ 85.222.87.0/24256PLAYPLAYASSIGNED PAJul 14, 2008abuse@play.pl
via PL-UPC-20050214
└ 85.222.88.0/221,024PLAYPLAYASSIGNED PAFeb 13, 2008abuse@play.pl
via PL-UPC-20050214
└ 85.222.92.0/221,024PLAYPLAYASSIGNED PAMar 3, 2008abuse@play.pl
via PL-UPC-20050214

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2025
Current origin since
Jan 2025 · 1.8 yr
Origin networks
1