Data as of Nov 10, 2026
89.109.0.0/18
2 anonymizer addresses · 0.01% · VPN3,745 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
3,745
23% of its addresses · 30 days
Always-on exits
1,342
36% of its exits
Spread
57 of 64
/24s with at least one exit
Providers
125
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
2.5M observations
- VPN · anonymizer
- Residential
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 89.109.50.0/24 | 172 | 253 | |
| 89.109.47.0/24 | 170 | 253 | |
| 89.109.46.0/24 | 167 | 255 | |
| 89.109.44.0/24 | 162 | 255 | |
| 89.109.51.0/24 | 162 | 254 | |
| 89.109.49.0/24 | 159 | 250 | |
| 89.109.45.0/24 | 156 | 251 | |
| 89.109.48.0/24 | 150 | 250 | |
| 89.109.4.0/24 | 4 | 18 | |
| 89.109.53.0/24 | 3 | 22 | |
| 89.109.15.0/24 | 3 | 19 | |
| 89.109.20.0/24 | 3 | 14 | |
| 89.109.42.0/24 | 2 | 20 | |
| 89.109.5.0/24 | 2 | 19 | |
| 89.109.1.0/24 | 2 | 18 | |
| 89.109.16.0/24 | 2 | 17 | |
| 89.109.52.0/24 | 2 | 17 | |
| 89.109.54.0/24 | 2 | 15 | |
| 89.109.23.0/24 | 2 | 15 | |
| 89.109.11.0/24 | 2 | 9 | |
| 89.109.3.0/24 | 1 | 68 | |
| 89.109.57.0/24 | 1 | 66 | |
| 89.109.63.0/24 | 1 | 59 | |
| 89.109.30.0/24 | 1 | 57 |
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
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- JoyProxy
- KindProxy
- KocerRoxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- 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
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 89.109.0.0/18 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 20.01% | 2 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
89.109.0.0/18
From the registry to its use
- Mar 23, 2006Registry recordPJSC RostelecomALLOCATED PA89.109.0.0/18
- Apr 22, 2006– Jun 22, 2016AnnouncedAS25405 PJSC Rostelecom
- May 21, 2014Route objectAS25405 PJSC RostelecomRIPE route object for AS25405 PJSC Rostelecom, maintainer ROSTELECOM-MNT89.109.16.0/22
- Aug 15, 2016– today
- Oct 1, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- todayUsedVPN GateVPN
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Anonymizer addresses | Operator | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|---|
| 89.109.24.0/21 since Apr 2021 | AS12389 | Residential | 525 1 always on | PJSC Rostelecom | |||
| 89.109.44.0/23 since Mar 2024 | AS12389 | Residential | 506 318 always on | PJSC Rostelecom | |||
| 89.109.44.0/24 since Mar 2024 | AS12389 | Residential | 255 162 always on | PJSC Rostelecom | |||
| 89.109.45.0/24 since Mar 2024 | AS12389 | Residential | 251 156 always on | PJSC Rostelecom | |||
| 89.109.46.0/23 since Mar 2024 | AS12389 | Residential | 508 337 always on | PJSC Rostelecom | |||
| 89.109.46.0/24 since Mar 2024 | AS12389 | Residential | 255 167 always on | PJSC Rostelecom | |||
| 89.109.47.0/24 since Mar 2024 | AS12389 | Residential | 253 170 always on | PJSC Rostelecom | |||
| 89.109.48.0/23 since Mar 2024 | AS12389 | Residential | 500 309 always on | PJSC Rostelecom | |||
| 89.109.48.0/24 since Mar 2024 | AS12389 | Residential | 250 150 always on | PJSC Rostelecom | |||
| 89.109.49.0/24 since Mar 2024 | AS12389 | Residential | 250 159 always on | PJSC Rostelecom | |||
| 89.109.50.0/23 since Mar 2024 | AS12389 | Residential | 507 334 always on | PJSC Rostelecom | |||
| 89.109.50.0/24 since Mar 2024 | AS12389 | Residential | 253 172 always on | PJSC Rostelecom | |||
| 89.109.51.0/24 since Mar 2024 | AS12389 | Residential | 10.39%VPN | VPN servicesoperated by VPN Gate | 254 162 always on | PJSC Rostelecom | |
| 89.109.56.0/21 since Apr 2021 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 506 2 always on | PJSC 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 89.109.0.0/18 | 16,384 | RU-RTK-20060323 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Mar 23, 2006 | abuse@ |
| └ 89.109.0.0/23 | 512 | NMTS-UAC-NET5 | Network for vpdn session terminations on UAC`s | ASSIGNED PA | May 2, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.2.0/23 | 512 | BRAS1-DYNAMICPOOL-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Aug 23, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.4.0/24 | 256 | PPPOE-IPPOOL8-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 17, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.5.0/24 | 256 | PPPOE-IPPOOL24-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Apr 16, 2015 | abuse@ via RU-RTK-20060323 |
| └ 89.109.6.0/24 | 256 | DYNAMIC-FLY-POOL3-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Feb 14, 2008 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.0/27 | 32 | ALIDI-VT-NET | Personal network for | ASSIGNED PA | Jun 28, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.40/29 | 8 | NN-ELECTRICAL-NET | Personal network for | ASSIGNED PA | Jul 27, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.48/29 | 8 | GUMMI4-NET | Personal network for | ASSIGNED PA | Nov 22, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.64/29 | 8 | LINDOVSKOE-NN-NET | Personal network for | ASSIGNED PA | Jun 23, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.72/29 | 8 | DERYUGINA-NET | Personal network for | ASSIGNED PA | Oct 12, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.80/29 | 8 | MRK-SERVERS | Network for servers J-service | ASSIGNED PA | Sep 15, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.88/29 | 8 | EVMCOMPLEX-NET | JSC EVM Complex | ASSIGNED PA | Sep 21, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.96/27 | 32 | Klutch-net | Personal network for | ASSIGNED PA | Sep 7, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.144/29 | 8 | Market-net | Personal network for | ASSIGNED PA | Oct 18, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.152/29 | 8 | Japan-Center-net | Personal network for | ASSIGNED PA | Oct 27, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.160/29 | 8 | SweetLife-FoodService-NET | Personal network for | ASSIGNED PA | Dec 30, 2013 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.168/29 | 8 | Chazma-net | Personal network for | ASSIGNED PA | Nov 13, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.176/29 | 8 | Rospotrebnadzor-NET | Personal network for | ASSIGNED PA | Jan 17, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.184/29 | 8 | SarovEngCenter-NN-NET | Personal network for | ASSIGNED PA | Mar 5, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.192/29 | 8 | VVNP-NET | Personal network for | ASSIGNED PA | Jan 24, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.200/29 | 8 | NN-JUDICAL-NET | Personal network for | ASSIGNED PA | Dec 4, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.208/29 | 8 | ISR-Trans-NN-NET | Personal network for | ASSIGNED PA | Dec 31, 2013 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.216/29 | 8 | GUMMI5-NET | Personal network for | ASSIGNED PA | Dec 25, 2006 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.224/29 | 8 | arbitrsud-nn-net | Personal network for | ASSIGNED PA | May 26, 2008 | abuse@ via RU-RTK-20060323 |
| └ 89.109.7.232/29 | 8 | VKT-net | Personal network for | ASSIGNED PA | Jan 19, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.8.0/24 | 256 | PPPOE-IPPOOL-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.9.0/24 | 256 | PPPOE-IPPOOL7-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Dec 11, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.10.0/24 | 256 | PPPOE-IPPOOL22-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Jun 5, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.11.0/24 | 256 | PPPOE-IPPOOL23-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Dec 11, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.12.0/24 | 256 | STATIC-FLY-POOL2-NNOVVT | Network for static PPPoE cliens | ASSIGNED PA | Sep 7, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.13.0/24 | 256 | PPPOE-IPPOOL15-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Jul 31, 2009 | abuse@ via RU-RTK-20060323 |
| └ 89.109.14.0/23 | 512 | PPPOE-IPPOOL17-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Sep 7, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.16.0/22 | 1,024 | BRAS1-DYNAMICPOOL-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Aug 23, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.20.0/24 | 256 | NMTS-SS7DIALUP2-NET | Network for dialup services in NNOV city | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.21.0/24 | 256 | PPPOE-IPPOOL2-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.22.0/24 | 256 | PPPOE-IPPOOL28-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 6, 2016 | abuse@ via RU-RTK-20060323 |
| └ 89.109.23.0/24 | 256 | PPPOE-IPPOOL27-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 6, 2016 | abuse@ via RU-RTK-20060323 |
| └ 89.109.24.0/21 | 2,048 | BRAS1-DYNAMICPOOL-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Sep 6, 2016 | abuse@ via RU-RTK-20060323 |
| └ 89.109.32.0/24 | 256 | PPPOE-IPPOOL29-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 6, 2016 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.0/29 | 8 | ALIDI2-NET | Personal network for | ASSIGNED PA | Feb 5, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.8/29 | 8 | SVIAZBANK2-NET | Personal network for | ASSIGNED PA | Feb 20, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.16/28 | 16 | SBRF-NN-NET4 | Personal network for | ASSIGNED PA | Mar 6, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.32/29 | 8 | SugarFactory-NN-NET | Personal network for | ASSIGNED PA | Jan 20, 2017 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.40/29 | 8 | SBB-GARANTIA-NET | Personal network for | ASSIGNED PA | Mar 16, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.48/29 | 8 | CapvidiaNV-NN-NET | Personal network for | ASSIGNED PA | Sep 4, 2017 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.72/29 | 8 | ETRA-NN-NET | Personal network for | ASSIGNED PA | Jun 29, 2017 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.80/29 | 8 | Metallimpress-NN-NET | Personal network for | ASSIGNED PA | Dec 25, 2015 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.88/29 | 8 | Alekseevs-Bureau-NN-NET | Personal network for Alekseev's Central Hydrofoil Bureau | ASSIGNED PA | Dec 22, 2017 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.96/29 | 8 | DNS-SHOP-NET1 | Personal network for | ASSIGNED PA | Jul 20, 2012 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.104/29 | 8 | NNIIRT-NET | Personal network for | ASSIGNED PA | Dec 2, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.112/29 | 8 | DNS-SHOP-NET2 | Personal network for | ASSIGNED PA | Jul 20, 2012 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.120/29 | 8 | Methodological-Center-NN-NET | Personal network for | ASSIGNED PA | Dec 19, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.128/29 | 8 | KBRET-NET | Personal network for KBRET | ASSIGNED PA | May 17, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.136/29 | 8 | BRAVO-SOFT-NET | Personal network for | ASSIGNED PA | May 21, 2010 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.144/29 | 8 | DNS-SHOP-NET4 | Personal network for | ASSIGNED PA | Jul 23, 2012 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.152/29 | 8 | NTA-NET | Personal network for | ASSIGNED PA | May 29, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.160/28 | 16 | Energobalance-net4 | Personal network for | ASSIGNED PA | May 24, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.176/29 | 8 | BERICAP-NET | Personal network for BERICAP | ASSIGNED PA | Aug 6, 2015 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.184/29 | 8 | DNS-SHOP-NET3 | Personal network for | ASSIGNED PA | Jul 23, 2012 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.192/27 | 32 | NNE-NET2 | Personal network for | ASSIGNED PA | May 28, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.232/29 | 8 | VAGP-NET | Personal network for | ASSIGNED PA | Feb 5, 2008 | abuse@ via RU-RTK-20060323 |
| └ 89.109.33.240/28 | 16 | NGTS-SERVERS-NET | Network internal needs for NGTS servers | ASSIGNED PA | Nov 9, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89. | 1,536 | PPPOE-IPPOOL13-NNOVVT | Network for OJSC Rstelecom Nizhny Novgorod | ASSIGNED PA | Aug 23, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.40.0/23 | 512 | STATIC-FLY-POOL16-NNOVVT | Network for static PPPoE cliens | ASSIGNED PA | Aug 21, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.42.0/24 | 256 | PPPOE-IPPOOL3-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.43.0/24 | 256 | PPPOE-IPPOOL20-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Jun 5, 2014 | abuse@ via RU-RTK-20060323 |
| └ 89. | 2,048 | PPPoE-PG-NAT-POOL4 | Network for PPPoE clients terminations in | ASSIGNED PA | May 13, 2021 | abuse@ via RU-RTK-20060323 |
| └ 89.109.52.0/24 | 256 | PPPOE-IPPOOL4-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.53.0/24 | 256 | PPPOE-IPPOOL6-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 7, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.54.0/23 | 512 | PPPOE-IPPOOL5-NNOVVT | Network for PPPoE clients terminations in | ASSIGNED PA | Sep 3, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.56.0/23 | 512 | BRAS1-DYNAMICPOOL-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Aug 23, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.58.0/23 | 512 | DYNAMIC-FLY-POOL-NNOVVT | Network for OJSC VolgaTelecom | ASSIGNED PA | Aug 23, 2007 | abuse@ via RU-RTK-20060323 |
| └ 89.109.60.0/22 | 1,024 | NMTS-PPPOE-NET | Network for dynamic IP pools for broadband subscribers | ASSIGNED PA | Aug 21, 2007 | abuse@ via RU-RTK-20060323 |
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
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 16,382 | >99% | 15 | |
| VPNanonymizer | 2 | 0.01% | 2 |
Network & registry
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
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2006
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 2
- Last change of origin
- Aug 2016
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 89.109.0.0/18 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 1, 2018 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 89.109.16.0/22 | AS25405 | RIPE | NMTS Autonomous System | ROSTELECOM-MNT | Jun 9, 2026 |
Whois
Registration for this announcement
- Range
- 89.
109. 0. 0/ 18 - Netname
- RU-RTK-20060323
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Mar 23, 2006
- Updated
- Jun 6, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 23, 2006
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE