92.37.128.0/18
AS34584 · PJSC Rostelecom
Summary
- BGP Prefix
- 92.37.128.0/18
- Country
- 🇷🇺 Russia
- Domain
- rt.ru
- Registry
- RIPE_NCC
- ID
- RU-RTK-20080118
- Allocation
- Part of 92.37.128.0/17
WHOIS
- Network
- 92.37.128.0/17
- Name
- PJSC Rostelecom
- Net name
- RU-RTK-20080118
- Organization type
- allocated pa
- Registry
- RIPE_NCC
- Country
- RU
- Abuse contact
- PJSC Rostelecom Technical Team
- Abuse email
- abuse@rt.ru
Overlapping Ranges
| Range | Source | Holder | Country |
|---|---|---|---|
| 92.37.128.0/17 | BGP route | AS34584 PJSC Rostelecom | — |
| 92.37.128.0/17 | WHOIS (RIPE_NCC) | PJSC Rostelecom | RU |
| 92.37.128.0/17 | RIPE_NCC assigned | — | RU |
| 92.37.128.0/18 | BGP route | AS34584 PJSC Rostelecom | — |
| 92.37.128.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.144.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.152.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.160.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.168.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.176.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.176.0/21 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.184.0/21 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.136.0/22 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.136.0/22 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.156.0/22 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.184.0/22 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.130.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.134.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.140.0/23 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.140.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.142.0/23 | BGP route | AS12389 PJSC Rostelecom | — |
| 92.37.142.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.144.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.146.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.150.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.152.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.154.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.160.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.164.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.170.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.188.0/23 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.128.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.129.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.132.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.133.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.149.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.162.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.163.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.169.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.172.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.174.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.191.0/24 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.148.0/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.148.128/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.166.128/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.173.0/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.173.128/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.175.0/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.175.128/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.190.0/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.190.128/25 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.166.0/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.166.64/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.167.0/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.167.64/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.167.128/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.167.192/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.168.0/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.168.64/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.168.128/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |
| 92.37.168.192/26 | WHOIS (RIPE_NCC) | KHT-XDSL | RU |