Data as of Nov 19, 2026

79.170.191.0/24

9 residential-proxy exits · 30 days

LLC Babilon-T

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Providers
50
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxying
  • Proxyma
  • Q2IP
  • RapidProxy
  • RolaProxy
  • SIMPLYNODE
  • Shifter
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.170.184.0/21
since Dec 2021
AS24722Residential35
1 always on
LLC 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
79.170.184.0/212,048TJ-BABILON-20071002LLC Babilon-T (ORG-BA76-RIPE) · TJALLOCATED PAOct 2, 2007abuse@babilon-t.tj
└ 79.170.191.0/2664BABILON138Babilon-TASSIGNED PAOct 24, 2008abuse@babilon-t.tj
via TJ-BABILON-20071002
└ 79.170.191.64/2664BABILONKHATLONBabilon-TASSIGNED PAOct 24, 2008abuse@babilon-t.tj
via TJ-BABILON-20071002
└ 79.170.191.128/2664BABILONNIKOLAYBabilon-TASSIGNED PAOct 24, 2008abuse@babilon-t.tj
via TJ-BABILON-20071002
└ 79.170.191.192/2664BABILONMARIYABabilon-TASSIGNED PAOct 24, 2008abuse@babilon-t.tj
via TJ-BABILON-20071002

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
Jun 2009
Current origin since
Jun 2009 · 17 yr
Origin networks
1