Data as of Nov 16, 2026

188.43.0.0/16

1 anonymizer address · <0.01% · VPN874 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
874
1.3% of its addresses · 30 days
Always-on exits
159
18% of its exits
Spread
127 of 256
/24s with at least one exit
Providers
136
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

512K observations
  • VPN · anonymizer
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LOKIPROXY
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSTPROXY_LITE
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIES.RIP
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SIMPLYNODE
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
record created Apr 27, 2009
2 · Leased from
not leased
3 · Announced by
AS20485 Joint Stock Company TransTeleCom
since May 2009 · 17.5 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 188.43.0.0/16/24s
VPN GateUniversity of Tsukuba
1<0.01%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

188.43.0.0/16

From the registry to its use

  1. Apr 27, 2009
    Registry record
    Joint Stock Company TransTeleCom
    ALLOCATED PA
    188.43.0.0/16
  2. Apr 28, 2009
    Route object
    AS20485 Joint Stock Company TransTeleCom
    RIPE route object for AS20485 Joint Stock Company TransTeleCom, maintainer TRANSTELECOM-MNT
  3. May 15, 2009– today
    Announced
    AS20485 Joint Stock Company TransTeleCom
    Internet provider
  4. today
    Used
    VPN Gate
    VPN

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
188.43.0.0/1665,536RU-TRANSTELECOM-20090427Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAApr 27, 2009abuse@ttk.ru
└ 188.43.0.0/24256TTK_local_peering(999999) TTKASSIGNED PADec 23, 2010abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.1.0/24256TTK_local_peering2(999999) TTKASSIGNED PADec 30, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.2.0/24256TTK-PtP-NET22(MS004978) TTKASSIGNED PASep 26, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.3.0/24256TTK-PtP-NET21Transtelecom point-to-point interfacesASSIGNED PASep 30, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.4.0/24256TTK-PtP-NET23(MS004978) TTK for Point-to-PointASSIGNED PANov 3, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.5.0/24256TTK-PtP-NET24TTK for Point-to-PointASSIGNED PAJun 17, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.6.0/24256TTK-PtP-NET25TTK for Point-to-PointASSIGNED PAJun 17, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.7.0/24256TTK-PtP-NET26TTK for Point-to-PointASSIGNED PAJun 17, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.8.0/24256TTK-PtP-NET27TTK for Point-to-PointASSIGNED PAAug 22, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.9.0/24256TTK-PtP-NET28(999999) TTK Point-to-PointASSIGNED PANov 14, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.10.0/24256TTK-PtP-NET29(999999) TTK Point-to-PointASSIGNED PADec 10, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.11.0/24256TTK-PtP-NET11(MS004978) TTKASSIGNED PAMar 28, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.12.0/24256TTK-PtP-NET12(999999) TTKASSIGNED PAJun 20, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.13.0/24256p2p-TTK-NET/31 for serial , RussiaASSIGNED PAAug 27, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.14.0/24256p2p-TTK-NET30(999999) p2p /30 networkASSIGNED PAAug 23, 2016abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.15.0/24256TTK-PtP-NET15(MS004978) TTKASSIGNED PAJan 14, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.16.0/221,024TTK-PtP-NET17TTKASSIGNED PAOct 26, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.20.0/24256TTK-PtP-NET16(MS004978) TTKASSIGNED PASep 17, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.21.0 - 188.43.31.2552,816TTK-PtPTTKSUB-ALLOCATED PAFeb 26, 2020abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.31.8/298Atomenergoproekt-net1SP112589, FSUE "Atomenergoproekt"ASSIGNED PAFeb 26, 2020abuse@ttk.ru
via TTK-PtP
└ 188.43.31.32/298Atomenergoproekt-net2SP112589, FSUE "Atomenergoproekt"ASSIGNED PAFeb 26, 2020abuse@ttk.ru
via TTK-PtP
└ 188.43.32.0/221,024TTK-PtPTTKASSIGNED PAMar 31, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.36.0/221,024INSATCOM-V-NET(SR000346) Insatkom-VASSIGNED PAJun 1, 2010abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.40.0/24256TTK-PTP-NETunknownASSIGNED PAJun 24, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.41.0/24256TTK-PtP-NETTTKASSIGNED PAMar 31, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.42.0/24256TTK-NETMoscow, Russia, TestASSIGNED PAAug 27, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.43.0/24256TTK-PtPTTKASSIGNED PAMar 24, 2016abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.44.0/23512PKI-NET3(RS000329) Fiber optic backbone operator Limited liability company "Provider commercial information"ASSIGNED PADec 13, 2010abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.46.0/23512SVYAZ-TELECOM-NET(CN000564) svyaztelecomASSIGNED PADec 15, 2010abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.50.0/24256UKTALY-TYNDA-NET(KH000298 ) UktaliASSIGNED PAFeb 9, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.51.0/24256TVSERVICEN-NET2(YA000129) TVServisASSIGNED PAFeb 14, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.52.0/24256GVCRZD-EBG-NET2(059FR-23) RZDASSIGNED PAJun 8, 2023abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.53.0/24256SAMIIT-NET(MS004926) samgupsASSIGNED PAFeb 14, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.55.0/24256TTK-PtP-28(999999) TTK Point-to-PointASSIGNED PAJan 19, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.56.0/24256KONTAKT-KTV-NET(NN001942) Contact-KASSIGNED PAMar 3, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.57.0/24256KONTAKT-KTV-NET3(NN001942) Contact-KASSIGNED PAMar 3, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.58.0/24256TTK-PtP-28unknownASSIGNED PAMar 4, 2025abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.59.0/24256TTK-PtP-28unknownLIR-PARTITIONED PAOct 12, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.59.16 - 188.43.59.3015Polyus-NET(176-26) PolyusASSIGNED PAOct 12, 2026abuse@ttk.ru
via TTK-PtP-28
└ 188.43.61.0/24256GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAJul 15, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.62.0/24256TTK-MOSCOW-OFFICE-WIFI-NETMoscow, RussiaASSIGNED PAAug 27, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.64.0/23512GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAJun 15, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.66.0/23512GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAJan 16, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.68.0/23512GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAFeb 18, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.70.0/24256VRNTKM-NET(MS000229) YugoVostokTTKASSIGNED PAOct 7, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.72.0/212,048AKAMAI-SERVERS(999999) TTK-Akamai-ServersASSIGNED PAOct 4, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.86.0/24256CITYLINK-NET(KH000314) Sity LinkASSIGNED PAOct 6, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.87.0/24256GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAAug 17, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.88.0/24256KPOST-NET(MS002204) TTK-DVASSIGNED PAAug 12, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.89.48/2816VK-TTK-NET(999999) VK-ServersASSIGNED PASep 22, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.90.0/23512ZHTK-NET1(MS007581) ZHTK p-t-pASSIGNED PAAug 29, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.92.0/24256PKI-NET4(RS000329) Fiber optic backbone operator Limited liability company "Provider commercial information"ASSIGNED PAOct 28, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.93.0/24256TTK-PTPunknownASSIGNED PAJul 13, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.94.0/24256BITELEKOM(CN000577) bitelecomASSIGNED PAAug 24, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.95.0/24256TELECON-NET(KH000314) City LinkASSIGNED PAMar 23, 2011abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.96.0/24256TTK-PTPTTK PTP networkASSIGNED PAJun 29, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.97.0/24256ZHTK-NET5(MS007581) ZHTKASSIGNED PANov 23, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.98.0/24256ZHTK-NET6(MS007581) ZHTK p-t-pASSIGNED PADec 29, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.99.0/24256TTK-PtPTTKASSIGNED PAMay 14, 2009abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.100.0/24256ZHTK-NET8(MS007581) ZHTK p-t-pASSIGNED PAJun 29, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.101.0/2732FABRICA_DANNYH_NET(MS007800) FabricaDannykhASSIGNED PADec 25, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.101.64/2816Maintainer-NET(MS006340) Cnii RTKASSIGNED PAJan 9, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.101.80/2816LIFESTREAM_CDN(999999) TTK-LifestreamASSIGNED PASep 18, 2018abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.101.128/2816MSK-OCRV-NET(CN000732) OcrvASSIGNED PAApr 4, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.101.144/2816RTC-NET(MS007484) RusTransComASSIGNED PANov 7, 2018abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.102.0/23512DJV1DJVASSIGNED PAAug 18, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.104.0/212,048SETTC-TMB-RTL-NET(MS003940) YugoVostokTTKASSIGNED PADec 18, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.112.0/23512tvservicen-NET(YA000129) TVServisASSIGNED PAOct 29, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.114.0/23512SS15341-RIPE(KH000263) IP SlivkinaASSIGNED PADec 2, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.117.96/2732VK-TTK-NET(999999) VK-ServersASSIGNED PASep 22, 2026abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.119.0/24256ZHTK-NET9(MS007581) ZHTK p-t-pASSIGNED PAJun 30, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.124.0/24256NIKA-EKO-NET(NN002042) Nika-EKOASSIGNED PAAug 5, 2014abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.125.0/24256DJV2DJVASSIGNED PAAug 18, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.126.0/24256GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAAug 26, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.127.0/24256GOOGLE-TTK-NET(999999) Google-ServersASSIGNED PAOct 5, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.128.0/221,024PPPoE-vrn-ttk-NET(MS005986) YugoVostokTTKASSIGNED PAOct 15, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.132.0/24256NLAB(999999) TTKASSIGNED PAApr 17, 2016abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.133.0/24256FILTER-Test(999999) TTKASSIGNED PAJun 7, 2016abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.134.0/23512ZHTK-NET10(MS007581) ZHTK p-t-pASSIGNED PAJun 30, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.136.0/24256KPOST-NET2(MS003584) TTK-DVASSIGNED PASep 12, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.184.0/212,048TTK-PtPTTKASSIGNED PAMar 13, 2024abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.192.0/212,048TTK-PtPTTKASSIGNED PANov 25, 2022abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.200.0 - 188.43.211.2553,072TTK-PtPTTKASSIGNED PASep 24, 2019abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.212.0/221,024TTK-PtPTTKASSIGNED PAJul 3, 2024abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.216.0/212,048AKAMAI-FB-TTK-NET(999999) Akamai, FBASSIGNED PAOct 5, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.224.0 - 188.43.247.2556,144TTK-PtPTTKASSIGNED PAJul 13, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.248.0 - 188.43.253.2551,536TTK-PtPTTKASSIGNED PAJul 13, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427
└ 188.43.254.0/23512TTK-PtPTTK for Test PurposesASSIGNED PAJul 13, 2017abuse@ttk.ru
via RU-TRANSTELECOM-20090427

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

65,536 addresses
TypeAddressesShareRanges
Residential65,360>99%10
Business1750.27%10
VPNanonymizer1<0.01%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2009
Current origin since
May 2009 · 18 yr
Origin networks
1