Data as of Nov 13, 2026

202.53.161.0/24

1 residential-proxy exit · 30 days

Agni Systems Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

45 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Byteful
  • DataImpulse
  • GloryCloud
  • Infatica
  • Kookey
  • Novada
  • ProxyRack
  • ProxyWing
  • RapidProxy
  • RolaProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.53.160.0/23
since May 2005
AS23923Residential2Agni Systems Limited
202.53.160.0/20
since Jun 2006
AS23923Residential73
3 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.161.0/24256AGNISYSAssined for Server & Hosting ServiceALLOCATED 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
May 2009
Current origin since
May 2009 · 17 yr
Origin networks
1