Data as of Nov 11, 2026

185.3.52.0/22

19 residential-proxy exits · 30 days

JT (Jersey) Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
69% of it

Residential-proxy exits

Proxy exits
19
1.9% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
48
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

16K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.3.53.0/24110
185.3.52.0/2415
185.3.54.0/2403
185.3.55.0/2401

Proxy providers listing exits

  • 2Captcha
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • GSocks
  • GoProxies
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

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
185.3.52.0/221,024JE-JERSEYTELECOM-20120919JT (Jersey) Limited (ORG-JT7-RIPE) · JEALLOCATED PASep 19, 2012ripe@jtglobal.com
└ 185.3.52.0/24256JT-Rapid-BusunknownSUB-ALLOCATED PAApr 23, 2020ripe@jtglobal.com
via JE-JERSEYTELECOM-20120919
└ 185.3.52.254/321Castle-Quay-Medical-PracticeunknownASSIGNED PAApr 23, 2020ripe@jtglobal.com
via JT-Rapid-Bus
└ 185.3.53.0/24256JT-Rapid-ResJersey Telecom Rapid ServiceASSIGNED PAJun 27, 2014ripe@jtglobal.com
via JE-JERSEYTELECOM-20120919
└ 185.3.54.0/24256Jersey_Host_AddressingunknownLIR-PARTITIONED PAMay 8, 2024ripe@jtglobal.com
via JE-JERSEYTELECOM-20120919
└ 185.3.54.0/2664MNE-BrianFosterMNE-Brian FosterASSIGNED PAJan 20, 2016ripe@jtglobal.com
via Jersey_Host_Addressing
└ 185.3.54.128/2664FONNAT_AddressFON NAT AddressesLIR-PARTITIONED PAApr 16, 2024ripe@jtglobal.com
via Jersey_Host_Addressing
└ 185.3.54.136/298WT_RAPID_PoolunknownASSIGNED PAApr 16, 2024ripe@jtglobal.com
via FONNAT_Address
└ 185.3.54.144/298JT_RAPID_PRO_PoolunknownASSIGNED PAApr 16, 2024ripe@jtglobal.com
via FONNAT_Address
└ 185.3.54.152/298Local_BNG_Test_PoolunknownASSIGNED PAApr 16, 2024ripe@jtglobal.com
via FONNAT_Address
└ 185.3.54.160/298Test_Radiator_Spare_PoolunknownASSIGNED PAApr 16, 2024ripe@jtglobal.com
via FONNAT_Address
└ 185.3.55.0/24256JTIBS_HostsunknownLIR-PARTITIONED PAApr 17, 2024ripe@jtglobal.com
via JE-JERSEYTELECOM-20120919
└ 185.3.55.0/2664ElianFiduciaryElian Fiduciary Shared ServicesASSIGNED PADec 31, 2015ripe@jtglobal.com
via JTIBS_Hosts
└ 185.3.55.128/25128RegusManagementRegus Management UKASSIGNED PADec 31, 2015ripe@jtglobal.com
via JTIBS_Hosts

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

1,024 addresses
TypeAddressesShareRanges
Residential70369%5
Business32131%10

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2012
Current origin since
Dec 2012 · 14 yr
Origin networks
1