Data as of Nov 10, 2026

122.167.188.0/22

56 residential-proxy exits · 30 days

Bharti Airtel Ltd., Telemedia Services

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

Residential-proxy exits

Proxy exits
56
5.5% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
44
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
122.167.191.0/24035
122.167.190.0/24021

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • IPFly
  • IPPeak
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

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
122.160.0.0/121,048,576BHARTI-INBharti Airtel Limited (ORG-BAL1-AP) · INALLOCATED PORTABLE—ip.misuse@airtel.com
└ 122.160.0.0 - 122.168.255.255589,824BHARTI-INBHARTI Airtel LTD.ALLOCATED NON-PORTABLE—ip.misuse@airtel.com
└ 122.166.0.0/15131,072ABTS-KK-DSL-9102-blrABTS (Karnataka)ALLOCATED NON-PORTABLE—ip.misuse@airtel.com
via BHARTI-IN
└ 122.167.0.0/1665,536ABTS-KK-DSL-9102-blrABTS (Karnataka)ALLOCATED NON-PORTABLE—ip.misuse@airtel.com
└ 122.167.128.0/1816,384ABTS-KK-DSL-9102-blrABTS (Karnataka)ALLOCATED NON-PORTABLE—ip.misuse@airtel.com
via ABTS-KK-DSL-9102-blr

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2007
Current origin since
Jan 2022 · 4.8 yr
Origin networks
3
Last change of origin
Jun 2008
Recorded history

History

Handoffs
2