Data as of Nov 21, 2026

217.11.186.0/23

3 residential-proxy exits · 30 days

LLC Babilon-T

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
24
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

843 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.11.186.0/2402
217.11.187.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • GonzoProxy
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.11.186.0/24
since Feb 2019
AS24722Residential2LLC Babilon-T
217.11.187.0/24
since May 2011
AS24722Residential1LLC Babilon-T

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
217.11.176.0/204,096TJ-BABILON-20041129LLC Babilon-T (ORG-BA76-RIPE) · TJALLOCATED PANov 29, 2004abuse@babilon-t.tj
└ 217.11.186.0/2816AREA186CLIENT1site-TajikGazASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.16/2816AREA186CLIENT2Wi-Fi SarbandASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.32/2732AREA186CLIENT3unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.64/2816AREA186CLIENT4Wi-Fi KolhozabadASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.80/2816AREA186CLIENT5Wi-Fi KhojamastonASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.96/2816AREA186CLIENT6ATC-KorvonASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.112/2816AREA186CLIENT7site-Poliklinika10ASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.128/2732AREA186CLIENT8unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.160/2816AREA186CLIENT9Wi-Fi RogunASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.176/2816AREA186CLIENT10site-GuldastaASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.192/2732AREA186CLIENT11unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.224/298AREA186CLIENT12RahshASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.232/298AREA186CLIENT13OrienASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.240/298AREA186CLIENT14ProgressASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.186.248/298AREA186CLIENT15digestASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.0/2816AREA187CLIENT1site-MuseumASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.16/2816AREA187CLIENT2ATC-KhujandASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.32/2732AREA187CLIENT3unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.64/2816AREA187CLIENT4site-MatlubotASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.80/2816AREA187CLIENT5site-AutoRinokASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.96/2732AREA187CLIENT6unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.128/2732AREA187CLIENT7unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.160/2732AREA187CLIENT8unknownASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.192/2816AREA187CLIENT9site-KhlebzavodASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.208/298AREA187CLIENT10RissavhozASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.216/298AREA187CLIENT11KhovarASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.224/298AREA187CLIENT12CaftarASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.232/298AREA187CLIENT13HanakASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.240/298AREA187CLIENT14WM-TajikistanASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129
└ 217.11.187.248/298AREA187CLIENT15shelkkombinatASSIGNED PASep 26, 2007abuse@babilon-t.tj
via TJ-BABILON-20041129

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
Oct 2007
Current origin since
Oct 2007 · 19 yr
Origin networks
1