Data as of Nov 12, 2026

193.41.131.0/24

256 residential-proxy exits · 30 days

Mobile Telecom-Service LLP

Announcement
this exact prefix
RPKI valid
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
256
100% of its addresses · 30 days
Always-on exits
2
0.78% of its exits
Providers
69
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

40K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GeekProxy
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPCola
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NovaProxy
  • Novada
  • Oxylabs
  • PacketStream
  • PrivateProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VibeProxies
  • VitalExclusive
  • Webshare
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
193.41.130.0/23
since Oct 2025
AS48503Mobile512
3 always on
Mobile Telecom-Service LLP

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
193.41.130.0/23512KZ-TELE2-20001113Mobile Telecom-Service LLP (ORG-MTL59-RIPE) · KZALLOCATED PAFeb 17, 2020abuse@tele2.kz
└ 193.41.131.0/24256pool-net-karTele2 KazakhstanASSIGNED PADec 30, 2025abuse@tele2.kz
via KZ-TELE2-20001113

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
May 2005
Current origin since
Jun 2020 · 6.4 yr
Origin networks
2
Last change of origin
Jun 2020
Recorded history

History

Handoffs
1