Data as of Nov 11, 2026

116.68.193.0/24

10 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
10
3.9% of its addresses · 30 days
Always-on exits
2
20% of its exits
Providers
38
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EVOPROXY
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • Infatica
  • KocerRoxy
  • Kookey
  • LemonBright
  • NSocks
  • NiuProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
116.68.192.0/20
since Jun 2007
AS23923Residential141
15 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
116.68.192.0/204,096AGNISYSAgni Systems Limited (ORG-ASL2-AP) · BDALLOCATED PORTABLE—zaman@agni.com
└ 116.68.193.0/24256AGNISYSCustomer Allocation for Call CentreALLOCATED 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
Oct 2009
Current origin since
Sep 2017 · 9.2 yr
Origin networks
1