Data as of Nov 11, 2026

176.56.48.0/22

10 residential-proxy exits · 30 days

LLC 'Ipls'

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

Residential-proxy exits

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

Exits seen per day

2.9K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
176.56.48.0/212,048RU-KRASTELCOM-20110530LLC "Ipls" (ORG-JR9-RIPE) · RUALLOCATED PAMay 30, 2011no-reply@ipls.ru
└ 176.56.48.0/221,024IPLS-NET5IPLS NetworkASSIGNED PASep 18, 2012no-reply@ipls.ru
via RU-KRASTELCOM-20110530

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 176.56.48.0/21

176.56.48.0/21

Routing history

Pattern
Stable
First seen
Jun 2011
Current origin since
Jun 2011 · 15 yr
Origin networks
1