LAYER3 INTEL
Get started
Sign in
Data as of Nov 8, 2026

188.128.0.0/17

1,072 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
59% of it

Residential-proxy exits

Proxy exits
1,072
3.3% of its addresses · 30 days
Always-on exits
438
41% of its exits
Spread
65 of 128
/24s with at least one exit
Providers
116
selling exits here
Oct 9, 2026 – Nov 7, 2026

Exits seen per day

615K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
188.128.41.0/24231256
188.128.68.0/24190256
188.128.60.0/2437
188.128.33.0/2426
188.128.89.0/2422
188.128.32.0/2422
188.128.37.0/2422
188.128.23.0/2422
188.128.118.0/2414
188.128.84.0/2413
188.128.24.0/2411
188.128.100.0/2411
188.128.76.0/240256
188.128.77.0/240146
188.128.38.0/24012
188.128.46.0/2407
188.128.25.0/2406
188.128.63.0/2405
188.128.12.0/2405
188.128.86.0/2405
188.128.97.0/2404
188.128.35.0/2404
188.128.81.0/2404
188.128.10.0/2404

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYWING_BASIC
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
188.128.67.0/24AS12389Residential1PJSC Rostelecom
188.128.104.0/24
since Dec 2025
AS12389ResidentialPJSC Rostelecom

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.128.0.0/1732,768RU-RTK-20090311PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 11, 2009abuse@rt.ru
└ 188.128.0.0/2732ROSTELECOMNET_NETJSC Rostelecom P2P client connections 1 1ASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.0.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.224/2816ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.240/304AVANTELunknownASSIGNED PAJun 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.244/304ZapsibelectrosetstroyTicket 09-06672ASSIGNED PAJun 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.1.248/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.0/304ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.4/304Istack_ruTicket 09-12216ASSIGNED PAMay 22, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.8/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.16/2816ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.160/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 1, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.168/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 1, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.176/304CB_RF_OrenburgTicket 09-09065, PFASSIGNED PAJul 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.180/304GranTicket 09-09537-, CFASSIGNED PAJul 1, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.184/304TVC_PlanetaTicket 09-09566ASSIGNED PAJul 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.188/304LinkTelecomTicket 09-09566ASSIGNED PAJul 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.2.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.32/2816ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.48/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.56/304ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.60/304ftp_vi_rostov_ruTicket 09-13184ASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.3.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.96/2816ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAAug 13, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.112/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAAug 13, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.120/304Yugoria_ChelabinskTicket 09-10358, RISS 7264, UrFASSIGNED PAAug 13, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.124/304ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAAug 13, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.4.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.64/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 15, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.72/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 15, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.80/304ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 15, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.84/304Angstremt_ZelenogradTicket 09-09654ASSIGNED PAJul 15, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.88/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJul 15, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.5.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.192/304Dalniy_Vostok_Ocean_LineTicket 09-13356-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.196/304SeteLite-TelecomTicket 09-13798-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.200/304Pochta_RF_LipeckTicket 09-13296-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.204/304InformaTicket 09-19536-2ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.208/304Parma-MenegmentTicket 09-13206-2ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.212/304KiberClubTicket 09-13537-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.216/304Nerungri_MetallicTicket 09-13946-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.220/304ShturmanTicket 09-13452-1ASSIGNED PASep 18, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.6.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.0/304ZvenigorodstroyTicket 09-13348ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.4/304Sanatiriy_VoronovoTicket 09-13117ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.8/304GOU_DPO_RIROTicket 09-13183ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.12/304LipeckcombankTicket 09-13305ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.16/304Bar_LimonTicket 09-13472ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.20/304ChapliginTicket 09-13300ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.24/304MegaAlians_RyzanTicket 09-13425ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.28/304RyzanTransNefteProduktTicket 09-13428ASSIGNED PAAug 25, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.32/298ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.40/304Mini_MedTicket 09-14688, RISS 8073, CFASSIGNED PAJun 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.44 - 188.128.7.5916ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.60/304ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.160/304APK_DubininoTicket 09-19416-1ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.164/304YarKomplektStroyTicket 09-18788-2ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.168/304FGOU_VPO_SGAFKSTTicket 09-17778ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.172/304FGOU_VPO_SGAFKSTTicket 09-17758-1ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.176/304EnergoServisCompanyTicket 09-19622-1ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.184/304TapirTicket 09-19946-1ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.188/304TapirTicket 09-19932-1ASSIGNED PAAug 14, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.7.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.0/304ZhulyabinaTicket 10-02107-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.4/304Orenburgskaya_oblastnaya_FilarmoniyaTicket 09-16588-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.12/304IP_StepanidinaTicket 09-18379-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.16/304OYL-TELEKOMTicket 09-23018-2ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.20/304MONTENEGRO_INZhINERINGTicket 09-19170-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.24/304Strakhovaya_kompaniya_PariTicket 09-39012-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.28/304SpetstekhmontazhTicket 10-08720-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.32/304Avangard-MediaTicket 10-05547-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.36/304VIP-TekhnologiiTicket 09-19900-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.40/304Mezhdunarodnyy_promyshlennyy_bankTicket 10-15352-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.44/304BoskoVolgaTicket 09-20788-2ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.48/304Top-MediaTicket 09-22067-2ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.52/304Park_NikolaevaTicket 09-29377-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.56/304Epam_Sistemz_SamaraTicket 10-17100-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.60/304IP_StepanidinaTicket 09-21797-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.64/304MarGUTicket 09-23461-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.68/304KB_SinergiyaTicket 09-23217-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.72/304LaytKomTicket 09-28298-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.76/304EldoradoTicket 09-27685-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.80/304Kompaniya_TekhnotransTicket 09-23565-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.84/304VolgomostTicket 10-15819-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.88/304VolgospetsmontazhTicket 09-23174-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.92/304NK-TelekomTicket 09-25203-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.96/304Novosti_RegionovTicket 10-01368-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.100/304Ministerstvo_obrazovaniya_UdmurtiyaTicket 09-21809-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.104/304IP_PrishchepaTicket 10-13108-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.108/304Sosna_-_2000Ticket 10-01900-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.112/304Saratovskaya_mekhovaya_bazaTicket 10-13091-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.116/304VGTRK_Respubliki_MordoviyaTicket 10-20896-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.120/304Lotos_PenzaTicket 09-23883-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.124/304Dzhi_Ay_Di_InvestTicket 10-04421-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.128/304Aeroport_goroda_PenzyTicket 10-03075-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.132/304Ministerstvo_kultury_URTicket 09-24647-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.136/304GiprozemTicket 09-39421-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.140/304AKVATicket 09-41967-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.144/304MTS-PermTicket 10-23057-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.148/304Gelleri_Servis_v_SaratoveTicket 10-20165-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.152/304Telesem_SaratovTicket 09-41952-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.156/304SG_UralSibTicket 10-24945-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.160/304Sanatoriy_MozhayskiyTicket 09-21679-2ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.164/304Media_StarTicket 09-26967-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.168/304BiokorTicket 09-28833-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.172/304Pervyy_Protsessingovyy_BankTicket 09-30765-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.176/304OTKRYTIETicket 10-18456-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.180/304Mishel-TransTicket 09-23932-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.184/304TeplostarTicket 09-28008-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.188/304SPPKTicket 09-27822-2ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.192/304Tsentralnyy_rynokTicket 09-41970-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.196/304Ozdorovitelnyy_lagerTicket 09-41711-2ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.200/304Povolzhskiy_turisticheskiy_kholdingTicket 09-27896-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.204/304SodaTicket 09-27260-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.208/304Samarskiy_bulochno-konditerskiy_kombinatTicket 09-28575-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.212/304Samarskiy_bulochno-konditerskiy_kombinatTicket 10-05103-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.216/304TNT_PermTicket 10-05679-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.220/304AlternativaTicket 09-43097-1ASSIGNED PAFeb 5, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.224/304Permskiy_krayTicket 10-18687-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.228/304IK_GazinvestTicket 09-29784-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.232/304TortugaTicket 10-21405-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.236/304Finansovo-Promyshlennaya_Kompaniya_SVTicket 09-26167-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.240/304GUVD_po_Permskomu_krayuTicket 10-18229-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.244/304Imperiya-AvtoTicket 09-33831-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.248/304KristallTicket 09-29769-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.8.252/304SGESTicket 09-29767-1ASSIGNED PASep 9, 2010abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.32/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.64/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.192/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.9.224/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.0/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.32/304SOUS_SerovTicket 09-18814-1ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.36/304AZS_CentralTicket 09-19877-3ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.40/304ImpulsTicket 09-20595-1ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.44/304GP_NAC_RN_im_ShpilmanaTicket 09-18640-1ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.48/304TurgidTicket 09-23048-1ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.52/304MNP_GeodataTicket 09-21006-3ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.56/304VTB24_TyumenTicket 09-15805-3ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.60/304VTB24_TyumenTicket 09-15807-3ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.64/304Uralskiy_Transportniy_BankTicket 09-21184-3ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.68/304IntekTicket 09-23543-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.72/304Gorodskaya_poliklinikaTicket 09-22513-2ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.76/304IntercomTicket 09-23033-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.80/304IntercomTicket 09-23033-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.84/304Elita-TurTicket 09-23965-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.88/304Uralskaya_marka-ChalabinskTicket 09-24547-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.92/304Kurganskiy_Kabelniy_ZavodTicket 09-24245-1ASSIGNED PASep 23, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.96/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.128/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.160/2732ROSTELECOMNETJSC Rostelecom P2P client connectionsASSIGNED PAJun 19, 2009abuse@rt.ru
via RU-RTK-20090311
└ 188.128.10.192/304Stalepromishlennaya_CompanyTicket 09-24074-2ASSIGNED PASep 28, 2009abuse@rt.ru
via RU-RTK-20090311
← Previous1–200 of 1,596 · page 1 of 8Next →

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

32,768 addresses
TypeAddressesShareRanges
Residential19,18459%126
Business13,57641%1,534
Mobile80.02%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Origin network

AS12389

RU
Name
PJSC Rostelecom
Type
Internet provider
Registered
Jul 1, 2005
Domain
rt.ru
Website
www.company.rt.ru/en/
Industry
Internet Service Provider (ISP)
Spamhaus ASN-DROP
not listed