Data as of Nov 16, 2026

202.53.168.0/21

54 residential-proxy exits · 30 days

Agni Systems Limited

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
54
2.6% of its addresses · 30 days
Always-on exits
1
1.9% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
80
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

6.9K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CoreProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXYCOVE
  • PROXYSALE
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
202.53.168.0/24
since Jul 2006
AS23923Residential5Agni Systems Limited
via Customer Allocation for Navana Zone
202.53.169.0/24
since May 2018
AS23923Residential7Agni Systems Limited
via Customer Allocation for Banani Zone
202.53.170.0/24
since May 2007
AS23923Residential8Agni Systems Limited
via Customer Allocation for BusinessCUST
202.53.171.0/24
since May 2005
AS23923Residential7
1 always on
Agni Systems Limited
via Customer Allocation for Embassy
202.53.172.0/24
since May 2005
AS23923Residential9Agni Systems Limited
via Customer Allocation for Uttara Zone
202.53.173.0/24
since Jan 2017
AS23923Residential5Agni Systems Limited
via Customer Allocation for VPN Client
202.53.174.0/24
since Feb 2020
AS23923Residential8Agni Systems Limited
via Customer Allocation for PPPOE Dialup pool
202.53.175.0/24
since May 2005
AS23923Residential4Agni Systems Limited
via Customer Allocation DVB & Streaming

Registrations in this block

The registry's network records over this block, widest first, each 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
└ 202.53.169.0/24256AGNISYSCustomer Allocation for Banani ZoneALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS
└ 202.53.170.0/24256AGNISYSCustomer Allocation for BusinessCUSTALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS
└ 202.53.171.0/24256AGNISYSCustomer Allocation for EmbassyALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS
└ 202.53.172.0/24256AGNISYSCustomer Allocation for Uttara ZoneALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS
└ 202.53.173.0/24256AGNISYSCustomer Allocation for VPN ClientALLOCATED NON-PORTABLE—zaman@agni.com
└ 202.53.174.0/24256AGNISYSCustomer Allocation for PPPOE Dialup poolALLOCATED NON-PORTABLE—zaman@agni.com
via AGNISYS
└ 202.53.175.0/24256AGNISYSCustomer Allocation DVB & StreamingALLOCATED 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

Who has announced 202.53.160.0/20

202.53.160.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Jun 2006 · 20 yr
Origin networks
2
Last change of origin
Jun 2006
Recorded history

History

Handoffs
1