Data as of Nov 3, 2026
2.60.0.0/14
3 anonymizer addresses · <0.01% · VPNPJSC Rostelecom
Residential-proxy exits
Proxy exits
47,111
18% of its addresses · listed by providers
Always-on exits
594
1.3% of its exits
Spread
945 of 1,024
/24s with at least one exit
Providers
113
selling exits here
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.63.201.0/24 | 198 | 256 | |
| 2.63.200.0/24 | 189 | 256 | |
| 2.63.182.0/24 | 25 | 256 | |
| 2.63.183.0/24 | 21 | 256 | |
| 2.63.176.0/24 | 20 | 256 | |
| 2.63.180.0/24 | 16 | 256 | |
| 2.63.212.0/24 | 15 | 21 | |
| 2.63.181.0/24 | 14 | 256 | |
| 2.63.255.0/24 | 11 | 23 | |
| 2.60.143.0/24 | 8 | 14 | |
| 2.63.188.0/24 | 7 | 16 | |
| 2.60.117.0/24 | 7 | 12 | |
| 2.60.116.0/24 | 7 | 8 | |
| 2.63.234.0/24 | 5 | 11 | |
| 2.60.119.0/24 | 3 | 6 | |
| 2.60.112.0/24 | 3 | 4 | |
| 2.60.120.0/24 | 3 | 4 | |
| 2.63.202.0/24 | 2 | 199 | |
| 2.63.139.0/24 | 2 | 90 | |
| 2.63.235.0/24 | 2 | 19 | |
| 2.60.115.0/24 | 2 | 6 | |
| 2.63.242.0/24 | 2 | 3 | |
| 2.60.113.0/24 | 2 | 3 | |
| 2.63.232.0/24 | 1 | 255 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- 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
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- 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
- Webshare
- YumiProxy
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 2.60.0.0/14 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba (volunteer relays) | 3<0.01% | 3 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
2.60.0.0/14
From the registry to its use
- Oct 8, 2010Registry recordPJSC RostelecomALLOCATED PA2.60.0.0/14
- Jan 1, 2011– Jun 15, 2016AnnouncedAS41440 PJSC Rostelecom
- Jun 22, 2016– Jun 27, 2016
- Aug 15, 2016– Nov 2, 2026
- Sep 20, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- Apr 3, 2025Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT2.63.198.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 |
|---|---|---|---|---|---|---|---|
| 2.60.0.0/16 since Dec 2015 | AS12389 | Residential | 11,202 45 always on | PJSC Rostelecom | |||
| 2.60.0.0/18 since Jul 2020 | AS12389 | Residential | 3,125 1 always on | PJSC Rostelecom | |||
| 2.60.64.0/19 since Jul 2020 | AS12389 | Residential | 1,575 1 always on | PJSC Rostelecom | |||
| 2.60.96.0/20 since Jul 2020 | AS12389 | Residential | 851 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.112.0/20 since Mar 2024 | AS12389 | Residential | 56 30 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.128.0/19 since Jul 2020 | AS12389 | Residential | 1,583 9 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.143.0/24 since Mar 2024 | AS12389 | Residential | 14 8 always on | PJSC Rostelecom | |||
| 2.60.160.0/19 since Jul 2020 | AS12389 | Residential | 1,576 | PJSC Rostelecom | |||
| 2.60.192.0/19 since Jul 2020 | AS12389 | Residential | 1,564 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.224.0/20 since Jul 2020 | AS12389 | Residential | 854 2 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.60.240.0/20 since Mar 2025 | AS12389 | Residential | 18 2 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 2.61.0.0/16 since Dec 2014 | AS12389 | Residential | 3<0.01%VPN | VPN servicesoperated by VPN Gate | 15,831 1 always on | PJSC Rostelecom | |
| 2.62.0.0/16 since Feb 2018 | AS12389 | Residential | 9,836 2 always on | PJSC Rostelecom | |||
| 2.62.0.0/17 since Feb 2016 | AS12389 | Residential | 3,910 | PJSC Rostelecom | |||
| 2.63.0.0/17 since Mar 2016 | AS12389 | Residential | 6,041 4 always on | PJSC Rostelecom | |||
| 2.63.0.0/18 since Mar 2016 | AS12389 | Residential | 3,236 3 always on | PJSC Rostelecom | |||
| 2.63.64.0/18 since Mar 2016 | AS12389 | Residential | 2,805 1 always on | PJSC Rostelecom | |||
| 2.63.134.0/24 since Mar 2025 | AS12389 | Residential | PJSC Rostelecom | ||||
| 2.63.135.0/24 since Mar 2025 | AS12389 | Residential | PJSC Rostelecom | ||||
| 2.63.136.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom | |||
| 2.63.144.0/20 since Jul 2022 | AS201776 | Residential | 23 3 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.158.0/24 since Oct 10, 2026 | AS201776 | Residential | 2 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.159.0/24 since Oct 10, 2026 | AS201776 | Residential | 2 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.160.0/24 since Mar 2025 | AS12389 | Residential | PJSC Rostelecom | ||||
| 2.63.161.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom | |||
| 2.63.162.0/24 since Mar 2025 | AS12389 | Residential | 1 | PJSC Rostelecom | |||
| 2.63.163.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom | |||
| 2.63.170.0/24 since Mar 2024 | AS57580 | Business | 1 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.174.0/24 since Mar 2024 | AS12389 | Residential | 1 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.176.0/20 since Dec 2021 | AS201776 | Residential | 1,591 107 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.176.0/24 since May 2026 | AS201776 | Residential | 256 20 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.180.0/22 since May 2026 | AS201776 | Residential | 1,024 76 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.184.0/24 since May 2026 | AS201776 | Residential | 256 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.192.0/24 since Mar 2022 | AS48421 | Residential | PJSC Rostelecom via JSC Rostelecom . Rostov | ||||
| 2.63.200.0/23 since Jul 2024 | AS12389 | Residential | 512 387 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.200.0/24 since Jul 2024 | AS12389 | Residential | 256 189 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.201.0/24 since Jul 2024 | AS12389 | Residential | 256 198 always on | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.204.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom via JSC Rostelecom . Rostov | ||||
| 2.63.205.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom via JSC Rostelecom . Rostov | ||||
| 2.63.213.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom | |||
| 2.63.214.0/24 since Mar 2025 | AS12389 | Residential | 3 | PJSC Rostelecom | |||
| 2.63.220.0/24 since Mar 2025 | AS12389 | Residential | 1 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.221.0/24 since Mar 2025 | AS12389 | Residential | 3 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.222.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.223.0/24 since Mar 2025 | AS12389 | Residential | 1 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.224.0/20 since Jul 2022 | AS201776 | Residential | 551 9 always on | PJSC Rostelecom | |||
| 2.63.225.0/24 since Oct 2025 | AS201776 | Residential | PJSC Rostelecom | ||||
| 2.63.231.0/24 since May 2026 | AS201776 | Residential | 256 | PJSC Rostelecom | |||
| 2.63.232.0/24 since May 2026 | AS201776 | Residential | 255 1 always on | PJSC Rostelecom | |||
| 2.63.240.0/24 since Mar 2025 | AS12389 | Residential | PJSC Rostelecom via JSC Rostelecom . Rostov | ||||
| 2.63.241.0/24 since Apr 2026 | AS12389 | Residential | 2 | PJSC Rostelecom via JSC Rostelecom . Rostov | |||
| 2.63.242.0/24 since Mar 2025 | AS12389 | Residential | 3 2 always on | PJSC Rostelecom | |||
| 2.63.243.0/24 since Mar 2025 | AS12389 | Residential | 2 | PJSC Rostelecom | |||
| 2.63.244.0/24 since May 2025 | AS12389 | Residential | PJSC Rostelecom | ||||
| 2.63.253.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom via JSC Rostelecom . Rostov | ||||
| 2.63.254.0/24 since Apr 2024 | AS12389 | Residential | 2 | PJSC Rostelecom via JSC Rostelecom . Rostov |
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 |
|---|---|---|---|---|---|---|
| 2.60.0.0/14 | 262,144 | RU-RTK-20101008 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Oct 8, 2010 | [email protected] |
| └ 2.60.0.0/16 | 65,536 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 2, 2010 | [email protected] via RU-RTK-20101008 |
| └ 2.60.0.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 29, 2010 | [email protected] via RU-SIBNET |
| └ 2.60.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 29, 2010 | [email protected] via RU-SIBNET |
| └ 2.60.64.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 29, 2010 | [email protected] via RU-SIBNET |
| └ 2.60.96.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | May 30, 2023 | [email protected] via RU-SIBNET |
| └ 2.60.112.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.113.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.114.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.115.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | May 30, 2023 | [email protected] via WEBSTREAM |
| └ 2.60.116.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.117.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.118.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.119.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.120.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.121.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.122.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.123.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.124.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.125.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.126.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.127.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.128.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via RU-SIBNET |
| └ 2.60.143.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.160.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.60.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via RU-SIBNET |
| └ 2.60.240.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.241.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.242.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.243.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.244.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.245.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.246.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.247.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.248.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.249.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.250.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.251.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.252.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.253.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.254.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.60.255.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.61.0.0/16 | 65,536 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 2, 2010 | [email protected] via RU-RTK-20101008 |
| └ 2.61.0.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.64.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.96.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.112.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.120.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.128.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | [email protected] via RU-SIBNET |
| └ 2.61.160.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.61.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.62.0.0/16 | 65,536 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Mar 29, 2011 | [email protected] via RU-RTK-20101008 |
| └ 2.62.0.0 - 2.62.47.255 | 12,288 | WEBSTREAM | OJSC "Rostelecom" | ASSIGNED PA | Jul 5, 2012 | [email protected] via RU-SIBNET |
| └ 2.62.48.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.62.64.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via RU-SIBNET |
| └ 2.62.112.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.113.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.114.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.115.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.116.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.117.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.118.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.119.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.120.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.121.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.122.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.123.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.124.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.125.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.126.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.127.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via WEBSTREAM |
| └ 2.62.128.0/17 | 32,768 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 2, 2010 | [email protected] via RU-SIBNET |
| └ 2.62.128.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | [email protected] via RU-SIBNET |
| └ 2.62.160.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.62.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.63.0.0/17 | 32,768 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 2, 2010 | [email protected] via RU-RTK-20101008 |
| └ 2.63.0.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | [email protected] via RU-SIBNET |
| └ 2.63.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.63.64.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 14, 2011 | [email protected] via RU-SIBNET |
| └ 2.63.128.0/17 | 32,768 | Rostelecom_net | JSC Rostelecom . Rostov | SUB-ALLOCATED PA | Oct 7, 2021 | [email protected] via RU-RTK-20101008 |
| └ 2.63.132.0 - 2.63.132.6 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.132.7 - 2.63.132.13 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.132.14/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.132.16 - 2.63.132.22 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.132.23 - 2.63.132.29 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.132.30/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.133.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 27, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.134.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.135.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.136.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.137.224 - 2.63.137.230 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.137.231 - 2.63.137.237 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.137.238/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.137.240 - 2.63.137.246 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.137.247 - 2.63.137.253 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.137.254/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.0 - 2.63.138.6 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.7 - 2.63.138.13 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.14/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.16 - 2.63.138.22 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.23 - 2.63.138.29 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.30/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.32 - 2.63.138.38 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.39 - 2.63.138.45 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.46/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.48 - 2.63.138.54 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.55 - 2.63.138.61 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.62/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.64 - 2.63.138.70 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.71 - 2.63.138.77 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.78/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.80 - 2.63.138.86 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.87 - 2.63.138.93 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.94/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.96 - 2.63.138.102 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.103 - 2.63.138.109 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.110/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.112 - 2.63.138.118 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.119 - 2.63.138.125 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.126/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.128 - 2.63.138.134 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.135 - 2.63.138.141 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.142/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.144 - 2.63.138.150 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.151 - 2.63.138.157 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.158/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.160 - 2.63.138.166 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.167 - 2.63.138.173 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.174/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.176 - 2.63.138.182 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.183 - 2.63.138.189 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.190/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.192 - 2.63.138.198 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.199 - 2.63.138.205 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.206/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.208 - 2.63.138.214 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.215 - 2.63.138.221 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.222/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.224 - 2.63.138.230 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.231 - 2.63.138.237 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.238/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.240 - 2.63.138.246 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.247 - 2.63.138.253 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.138.254/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.0 - 2.63.139.6 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.7 - 2.63.139.13 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.14/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.16 - 2.63.139.22 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.23 - 2.63.139.29 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.30/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.32 - 2.63.139.38 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.39 - 2.63.139.45 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.46/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.48 - 2.63.139.54 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.55 - 2.63.139.61 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.62/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.64 - 2.63.139.70 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.71 - 2.63.139.77 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.78/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.80 - 2.63.139.86 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.87 - 2.63.139.93 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.94/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.96 - 2.63.139.102 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.103 - 2.63.139.109 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.110/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.112 - 2.63.139.118 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.119 - 2.63.139.125 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.126/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.128 - 2.63.139.134 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.135 - 2.63.139.141 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.142/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.144 - 2.63.139.150 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.151 - 2.63.139.157 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.158/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.160 - 2.63.139.166 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.167 - 2.63.139.173 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.174/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.176 - 2.63.139.182 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.183 - 2.63.139.189 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.190/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 21, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.192 - 2.63.139.198 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.199 - 2.63.139.205 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.206/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.208 - 2.63.139.214 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.215 - 2.63.139.221 | 7 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.139.222/31 | 2 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Feb 26, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.140.0/22 | 1,024 | Rezerv | unknown | ASSIGNED PA | Dec 5, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.144.0/20 | 4,096 | Miranda_Media_net | unknown | ASSIGNED PA | Oct 7, 2021 | [email protected] via Rostelecom_net |
| └ 2.63.160.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.161.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.162.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.163.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.168.0/26 | 64 | Rostelecom_net | unknown | ASSIGNED PA | Mar 2, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.169.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.170.0/24 | 256 | Rostelecom-client | unknown | ASSIGNED PA | Mar 16, 2022 | [email protected] via Rostelecom_net |
| └ 2.63.176.0/20 | 4,096 | Miranda_Media_net | unknown | ASSIGNED PA | Dec 22, 2021 | [email protected] via Rostelecom_net |
| └ 2.63.204.0/24 | 256 | MNCAP_Assigned | unknown | ASSIGNED PA | Nov 14, 2023 | [email protected] via Rostelecom_net |
| └ 2.63.211.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | May 23, 2024 | [email protected] via Rostelecom_net |
| └ 2.63.213.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 25, 2025 | [email protected] via Rostelecom_net |
| └ 2.63.214.0/24 | 256 | Rostelecom_net | unknown | SUB-ALLOCATED PA | Aug 25, 2025 | [email protected] via Rostelecom_net |
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 | 261,869 | >99% | 75 | |
| Business | 272 | 0.10% | 2 | |
| VPNanonymizer | 3 | <0.01% | 3 |
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
- Jan 2011
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 2
- Last change of origin
- Jun 2016
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.60.0.0/14 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | JSC Rostelecom regional branch "Siberia" | ROSTELECOM-MNT | Sep 20, 2018 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 2.63.198.0/23 | AS12389 | RIPE | ROSTELECOM-MNT | Apr 3, 2025 |
Whois
Registration for this announcement
- Range
- 2.60.0.0/14
- Netname
- RU-RTK-20101008
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Oct 8, 2010
- Updated
- Jun 4, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 8, 2010
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE