Data as of Nov 16, 2026

202.53.168.0/24

5 residential-proxy exits · 30 days

Agni Systems Limited

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

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
33
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

329 observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_BASIC
  • AETHYN_ELITE
  • AnyIP
  • BestProxy
  • BottingTools
  • Byteful
  • CatProxies
  • DataImpulse
  • EVOPROXY
  • FastProxy
  • FloppyData
  • IPFly
  • IPRoyal
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NextProxy
  • NiuProxy
  • PROXYCOVE
  • Proxies.fo
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • Shifter
  • Smartproxy
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.53.160.0/20
since Jun 2006
AS23923Residential70
1 always on
Agni Systems Limited

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
202.53.160.0/204,096AGNISYSAgni Systems Limited (ORG-ASL2-AP) · BDALLOCATED PORTABLE—zaman@agni.com
└ 202.53.168.0/24256AGNISYSCustomer Allocation for Navana ZoneALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS

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
Jul 2006
Current origin since
Jul 2006 · 20 yr
Origin networks
1