Data as of Nov 17, 2026

217.11.183.0/24

3 residential-proxy exits · 30 days

LLC Babilon-T

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.4K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • FastProxy
  • FlashProxy
  • Geonode
  • IPFly
  • InfiniteProxies
  • KocerRoxy
  • Kookey
  • LemonBright
  • Novada
  • Oxylabs
  • PROXYWING_BASIC
  • Proxiware
  • ProxyRack
  • PuraRoute
  • Q2IP
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.183.0/24256BABILONNET183unknownASSIGNED PAFeb 28, 2009abuse@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
Mar 2009
Current origin since
Sep 2020 · 6.2 yr
Origin networks
1