Data as of Nov 12, 2026

5.202.178.0/23

6 residential-proxy exits · 30 days

Pishgaman Toseeh Ertebatat Company (Private Joint Stock)

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

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

491 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.202.178.0/2405
5.202.179.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • FlashProxy
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • Infatica
  • KindProxy
  • Kookey
  • MangoProxy
  • NextProxy
  • NodeProxy
  • Novada
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • TalorData
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
5.202.176.0/20
since Apr 2026
AS49100Residential35Pishgaman Toseeh Ertebatat Company (Private Joint Stock)
5.202.0.0/16
since Oct 2016
AS49100Residential3,176
16 always on
Pishgaman Toseeh Ertebatat Company (Private Joint Stock)

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
5.202.0.0/1665,536IR-PTE-TEHRAN-20120829Pishgaman Toseeh Ertebatat Company (Private Joint Stock) (ORG-PTEC8-RIPE) · IRALLOCATED PAAug 29, 2012abuse@pishgaman.net
└ 5.202.176.0 - 5.202.180.391,064PTEunknownASSIGNED PAMay 7, 2017abuse@pishgaman.net
via IR-PTE-TEHRAN-20120829

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
Jun 2014
Current origin since
Jul 2020 · 6.4 yr
Origin networks
2
Last change of origin
Dec 2015
Recorded history

History

Handoffs
2