Data as of Nov 5, 2026
178.44.0.0/14
1 anonymizer address · <0.01% · VPNPJSC Rostelecom
Residential-proxy exits
Proxy exits
65,310
25% of its addresses · listed by providers
Always-on exits
633
0.97% of its exits
Spread
844 of 1,024
/24s with at least one exit
Providers
118
selling exits here
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 178.45.236.0/24 | 150 | 254 | |
| 178.46.213.0/24 | 5 | 255 | |
| 178.46.211.0/24 | 5 | 255 | |
| 178.44.225.0/24 | 5 | 60 | |
| 178.47.141.0/24 | 5 | 25 | |
| 178.46.158.0/24 | 5 | 24 | |
| 178.47.37.0/24 | 5 | 20 | |
| 178.46.137.0/24 | 5 | 13 | |
| 178.46.214.0/24 | 4 | 256 | |
| 178.46.209.0/24 | 4 | 256 | |
| 178.46.212.0/24 | 4 | 256 | |
| 178.46.208.0/24 | 4 | 255 | |
| 178.44.68.0/24 | 4 | 80 | |
| 178.45.111.0/24 | 4 | 79 | |
| 178.45.155.0/24 | 4 | 74 | |
| 178.46.161.0/24 | 4 | 21 | |
| 178.46.156.0/24 | 4 | 21 | |
| 178.46.152.0/24 | 4 | 21 | |
| 178.46.215.0/24 | 3 | 256 | |
| 178.44.25.0/24 | 3 | 84 | |
| 178.45.209.0/24 | 3 | 81 | |
| 178.45.202.0/24 | 3 | 75 | |
| 178.45.81.0/24 | 3 | 74 | |
| 178.44.108.0/24 | 3 | 73 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- ColaProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- JoyProxy
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- MrScraper
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- 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
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- WealthProxies
- Webshare
- YumiProxy
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 178.44.0.0/14 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 1<0.01% | 1 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
178.44.0.0/14
From the registry to its use
- Oct 31, 2011Registry recordPJSC RostelecomALLOCATED PA178.44.0.0/14
- Jun 8, 2017Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- Sep 10, 2018– today
- Oct 31, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT178.45.248.0/21
- Nov 2, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT178.45.236.0/24
- Nov 14, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT178.45.248.0/23
- 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 |
|---|---|---|---|---|---|---|---|
| 178.44.0.0/19 since Aug 2017 | AS12389 | Residential | 2,159 28 always on | PJSC Rostelecom | |||
| 178.44.32.0/19 since Aug 2017 | AS12389 | Residential | 2,147 19 always on | PJSC Rostelecom | |||
| 178.44.64.0/20 since Aug 2017 | AS12389 | Residential | 1,072 15 always on | PJSC Rostelecom | |||
| 178.44.80.0/20 since Aug 2017 | AS12389 | Residential | 808 4 always on | PJSC Rostelecom | |||
| 178.44.96.0/21 since Aug 2017 | AS12389 | Residential | 545 10 always on | PJSC Rostelecom | |||
| 178.44.104.0/21 since Aug 2017 | AS12389 | Residential | 555 7 always on | PJSC Rostelecom | |||
| 178.44.112.0/20 since Aug 2017 | AS12389 | Residential | 38 1 always on | PJSC Rostelecom | |||
| 178.44.128.0/17 since May 2016 | AS12389 | Residential | 7,599 94 always on | PJSC Rostelecom | |||
| 178.45.0.0/20 since Apr 2016 | AS12389 | Residential | 1,000 16 always on | PJSC Rostelecom | |||
| 178.45.16.0/20 since Apr 2016 | AS12389 | Residential | 1,001 9 always on | PJSC Rostelecom | |||
| 178.45.32.0/19 since Jun 2016 | AS12389 | Residential | 10.01%VPN | VPN servicesoperated by VPN Gate | 2,445 20 always on | PJSC Rostelecom | |
| 178.45.64.0/18 since Jun 2016 | AS12389 | Residential | 4,781 44 always on | PJSC Rostelecom | |||
| 178.45.128.0/21 since May 2016 | AS12389 | Residential | 637 4 always on | PJSC Rostelecom | |||
| 178.45.136.0/21 since May 2016 | AS12389 | Residential | 653 1 always on | PJSC Rostelecom | |||
| 178.45.144.0/21 since Apr 2016 | AS12389 | Residential | 488 8 always on | PJSC Rostelecom | |||
| 178.45.152.0/21 since Apr 2016 | AS12389 | Residential | 526 7 always on | PJSC Rostelecom | |||
| 178.45.160.0/19 since Jun 2016 | AS12389 | Residential | 2,403 23 always on | PJSC Rostelecom | |||
| 178.45.192.0/21 since May 2016 | AS12389 | Residential | 524 7 always on | PJSC Rostelecom | |||
| 178.45.200.0/21 since May 2016 | AS12389 | Residential | 577 14 always on | PJSC Rostelecom | |||
| 178.45.208.0/20 since May 2016 | AS12389 | Residential | 1,240 14 always on | PJSC Rostelecom | |||
| 178.45.224.0/22 since Apr 2016 | AS12389 | Residential | 245 4 always on | PJSC Rostelecom | |||
| 178.45.228.0/22 since Apr 2016 | AS12389 | Residential | 264 5 always on | PJSC Rostelecom | |||
| 178.45.232.0/22 since Apr 2016 | AS12389 | Residential | 240 7 always on | PJSC Rostelecom | |||
| 178.46.0.0/20 since Mar 2017 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.46.16.0/20 since Apr 2017 | AS12389 | Residential | 1,153 | PJSC Rostelecom | |||
| 178.46.32.0/19 since Aug 2017 | AS12389 | Residential | 1,951 | PJSC Rostelecom | |||
| 178.46.64.0/18 since Nov 2017 | AS12389 | Residential | 12,646 | PJSC Rostelecom | |||
| 178.46.64.0/19 since Dec 2017 | AS12389 | Residential | 6,297 | PJSC Rostelecom | |||
| 178.46.64.0/20 since Apr 2019 | AS12389 | Residential | 3,153 | PJSC Rostelecom | |||
| 178.46.80.0/20 since Dec 2017 | AS12389 | Residential | 3,144 | PJSC Rostelecom | |||
| 178.46.80.0/23 since Sep 2024 | AS12389 | Residential | 394 | PJSC Rostelecom | |||
| 178.46.96.0/19 since Dec 2017 | AS12389 | Residential | 6,349 | PJSC Rostelecom | |||
| 178.46.96.0/20 since Dec 2017 | AS12389 | Residential | 3,185 | PJSC Rostelecom | |||
| 178.46.96.0/24 since Sep 2024 | AS12389 | Residential | 205 | PJSC Rostelecom | |||
| 178.46.112.0/20 since Mar 2019 | AS12389 | Residential | 3,164 | PJSC Rostelecom | |||
| 178.46.128.0/20 since Jul 2017 | AS12389 | Residential | 48 11 always on | PJSC Rostelecom | |||
| 178.46.144.0/20 since Apr 2017 | AS12389 | Residential | 176 21 always on | PJSC Rostelecom | |||
| 178.46.160.0/20 since Jul 2017 | AS12389 | Residential | 168 23 always on | PJSC Rostelecom | |||
| 178.46.176.0/20 since Aug 2017 | AS12389 | Residential | 22 4 always on | PJSC Rostelecom | |||
| 178.46.192.0/20 since Aug 2017 | AS12389 | Residential | 1,257 | PJSC Rostelecom | |||
| 178.46.208.0/20 since Mar 2017 | AS12389 | Residential | 2,045 30 always on | PJSC Rostelecom | |||
| 178.46.224.0/19 since Jul 2017 | AS12389 | Residential | 5 1 always on | PJSC Rostelecom | |||
| 178.46.240.0/20 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.47.0.0/20 since Aug 2017 | AS12389 | Residential | 949 | PJSC Rostelecom | |||
| 178.47.16.0/20 since Mar 2017 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.47.32.0/20 since Nov 2017 | AS12389 | Residential | 60 12 always on | PJSC Rostelecom | |||
| 178.47.48.0/20 since Mar 2017 | AS12389 | Residential | 6 1 always on | PJSC Rostelecom | |||
| 178.47.64.0/19 since Aug 2017 | AS12389 | Residential | 6,108 | PJSC Rostelecom | |||
| 178.47.96.0/19 since Aug 2017 | AS12389 | Residential | 1,894 | PJSC Rostelecom | |||
| 178.47.128.0/20 since Aug 2017 | AS12389 | Residential | 127 17 always on | PJSC Rostelecom | |||
| 178.47.144.0/20 since Mar 2017 | AS12389 | Residential | 11 2 always on | PJSC Rostelecom | |||
| 178.47.160.0/19 since Apr 2017 | AS12389 | Residential | 2,123 | PJSC Rostelecom | |||
| 178.47.160.0/20 since Nov 2024 | AS12389 | Residential | 1,032 | PJSC Rostelecom | |||
| 178.47.192.0/20 since Mar 2017 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.47.208.0/20 since Mar 2017 | AS12389 | Residential | 1,250 | PJSC Rostelecom | |||
| 178.47.224.0/21 since Mar 2017 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.47.232.0/21 since Mar 2017 | AS12389 | Residential | PJSC Rostelecom | ||||
| 178.47.240.0/20 since Aug 2017 | AS12389 | Residential | 1,105 | 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 |
|---|---|---|---|---|---|---|
| 178.44.0.0/14 | 262,144 | RU-RTK-20100209 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Oct 31, 2011 | abuse@ |
| └ 178.44.0.0/17 | 32,768 | VOLGATELECOM-KIROV-DYNPOOL-22012010 | Dynamic IP Pools for customers in the | ASSIGNED PA | Mar 11, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.44.128.0/17 | 32,768 | VOLGATELECOM-ORB-DYNPOOL-14012010 | Dynamic IP Pools for xDSL and FTTH subscribers of the | ASSIGNED PA | Mar 11, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.45.0.0/19 | 8,192 | VOLGATELECOM-SARANSK-DYNPOOL-290910 | Dynamic IP Pools for customers in the | ASSIGNED PA | Oct 1, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178. | 24,576 | VOLGATELECOM-SAMARA-TLT-DYNPOOL-122009 | Dynamic pools for clients in the Samara branch | ASSIGNED PA | Oct 19, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.45.128.0/20 | 4,096 | VOLGATELECOM-SARATOV-DYNPOOL-160211 | Dynamic Pools for xDSL and FTTH subscribers | ASSIGNED PA | Feb 17, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.45.144.0/20 | 4,096 | VOLGATELECOM-SARANSK-DYNPOOL-090311 | Dynamic IP Pools for customers in the | ASSIGNED PA | Mar 9, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.45.160.0/19 | 8,192 | VOLGATELECOM-SAMARA-TLT-DYNPOOL-122009 | Dynamic pools for clients in the Samara branch | ASSIGNED PA | Oct 19, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.45.192.0/20 | 4,096 | VOLGA-ORB-DYNPOOL-29122011 | Dynamic IP Pools for xDSL and FTTH subscribers of the | ASSIGNED PA | Dec 29, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.45.208.0/20 | 4,096 | VOLGA-SARATOV-DYNPOOL-130112 | Dynamic Pools for xDSL and FTTH subscribers | ASSIGNED PA | Jan 13, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.45.224.0/21 | 2,048 | VOLGATELECOM-SARANSK-DYNPOOL-240112 | Dynamic IP Pools for customers in the | ASSIGNED PA | Jan 24, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.45.232.0/21 | 2,048 | VOLGA-SARANSK-DYNPOOL-070212 | Dynamic IP Pools for customers in the | ASSIGNED PA | Feb 7, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.45.240.0/21 | 2,048 | VOLGA-RESERVED-25-03-2013 | Reserved for future needs | ASSIGNED PA | Mar 25, 2013 | abuse@ via RU-RTK-20100209 |
| └ 178.45.248.0/23 | 512 | VTK-AS-TECHNET2 | Technological IP address space | ASSIGNED PA | Dec 30, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.45.250.0/23 | 512 | VTK-AS-TECHNET2 | Technological IP address space | ASSIGNED PA | Feb 15, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.45.252.0/24 | 256 | VTK-AS-TECHNET3 | Technological IP address space | ASSIGNED PA | Feb 15, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178. | 768 | VTK-AS-TECHNET4 | Technological IP address space | ASSIGNED PA | Dec 26, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.46.0.0/22 | 1,024 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Jun 22, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.46.4.0/24 | 256 | USI_ | Static distribution IP's for broadband services | ASSIGNED PA | Jun 22, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178. | 2,816 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Jun 22, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.46.16.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Apr 12, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.32.0/19 | 8,192 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 23, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.64.0/18 | 16,384 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Apr 19, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.128.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | May 31, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.144.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Jul 19, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.160.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Aug 4, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.176.0/23 | 512 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Feb 7, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178. | 3,584 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Feb 7, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.46.192.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Oct 5, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.208.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Oct 18, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.46.224.0/19 | 8,192 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Oct 18, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.0.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Oct 18, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.16.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Oct 18, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.32.0/23 | 512 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 23, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178. | 3,584 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Mar 20, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.47.48.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 14, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.64.0/19 | 8,192 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 10, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.96.0/19 | 8,192 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 10, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.128.0/21 | 2,048 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Feb 7, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.47.136.0/22 | 1,024 | Argus_ | Static distribution IP's for broadband services | ASSIGNED PA | Jan 27, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.47.140.0/22 | 1,024 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Mar 21, 2012 | abuse@ via RU-RTK-20100209 |
| └ 178.47.144.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 14, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.160.0/19 | 8,192 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 21, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.192.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 21, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.208.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Dec 23, 2010 | abuse@ via RU-RTK-20100209 |
| └ 178.47.224.0/21 | 2,048 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Mar 2, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.47.232.0/21 | 2,048 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Mar 2, 2011 | abuse@ via RU-RTK-20100209 |
| └ 178.47.240.0/20 | 4,096 | USI_ | Dynamic distribution IP's for broadband services | ASSIGNED PA | Feb 21, 2012 | abuse@ via RU-RTK-20100209 |
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
262,144 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 262,143 | >99% | 58 | |
| VPNanonymizer | 1 | <0.01% | 1 |
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
- Sep 2018
- Current origin since
- Sep 2018 · 8.2 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 178.44.0.0/14 | AS12389 | /20 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Jun 8, 2017 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 178.45.236.0/24 | AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Nov 2, 2018 |
| 178.45.248.0/21 | AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 31, 2018 |
| 178.45.248.0/23 | AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Nov 14, 2018 |
Whois
Registration for this announcement
- Range
- 178.
44. 0. 0/ 14 - Netname
- RU-RTK-20100209
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Oct 31, 2011
- Updated
- May 29, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 9, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE