AS29194
MTS PJSC — mtu.ru
Summary
| Country |
 Russian Federation
|
| Organization | MTS PJSC |
| Domain | mtu.ru |
| Number of IPv4 | 49,152 |
| Number of IPv6 | 0 |
| AS Type | ISP |
| Registry | RIPE NCC |
| Allocated | June 25, 2003 (about 22 years ago) |
| Updated | September 04, 2018 (about 6 years ago) |
IP Ranges
AS29194 announces 48 IPv4 ranges and 0 IPv6 range.
That's a total of 49,152 IPv4 address and 0 IPv6 address.
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 77.66.184.0/23 |
Ip Address Space for Kazan And Novosibirsk
|
512 | RIPE NCC | ASSIGNED PA |
| 77.66.186.0/23 |
Ip Address Space for Kazan And Novosibirsk
|
512 | RIPE NCC | ASSIGNED PA |
| 77.66.188.0/23 |
Ip Address Space for Kazan And Novosibirsk
|
512 | RIPE NCC | ASSIGNED PA |
| 83.151.0.0/20 |
MTS PJSC
|
4,096 | RIPE NCC | ASSIGNED PI |
| 83.151.0.0/23 |
MTS PJSC
|
512 | RIPE NCC | ASSIGNED PI |
| 83.151.2.0/23 |
MTS PJSC
|
512 | RIPE NCC | ASSIGNED PI |
| 83.151.11.0/24 |
MTS PJSC
|
256 | RIPE NCC | ASSIGNED PI |
| 83.151.12.0/22 |
MTS PJSC
|
1,024 | RIPE NCC | ASSIGNED PI |
| 89.251.144.0/21 |
MTS PJSC
|
2,048 | RIPE NCC | ALLOCATED PA |
| 89.251.151.0/24 |
Tatarstan, Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 89.251.152.0/21 |
Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 89.251.152.0/22 |
Tatarstan, Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 89.251.156.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 89.251.156.0/23 |
MTS PJSC
|
512 | RIPE NCC | ALLOCATED PA |
| 176.52.0.0/19 |
Kazan, Tatarstan, Russia
|
8,192 | RIPE NCC | ASSIGNED PA |
| 176.52.8.0/22 |
Kazan, Tatarstan, Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.52.12.0/22 |
Kazan, Tatarstan, Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.52.16.0/21 |
Kazan, Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 176.52.24.0/21 |
Kazan, Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 176.52.32.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.34.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.40.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.42.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.52.0/22 |
Kazan, Tatarstan, Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.52.56.0/22 |
Kazan, Tatarstan, Russia
|
1,024 | RIPE NCC | ASSIGNED PA |
| 176.52.64.0/24 |
Kazan, Tatarstan, Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 176.52.76.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.78.0/23 |
Kazan, Tatarstan, Russia
|
512 | RIPE NCC | ASSIGNED PA |
| 176.52.96.0/21 |
MTS PJSC
|
2,048 | RIPE NCC | ALLOCATED PA |
| 176.52.104.0/21 |
MTS PJSC
|
2,048 | RIPE NCC | ALLOCATED PA |
| 176.52.112.0/23 |
MTS PJSC
|
512 | RIPE NCC | ALLOCATED PA |
| 176.52.114.0/23 |
MTS PJSC
|
512 | RIPE NCC | ALLOCATED PA |
| 176.52.120.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.122.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.123.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.124.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.125.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.126.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 176.52.127.0/24 |
MTS PJSC
|
256 | RIPE NCC | ALLOCATED PA |
| 217.66.16.0/21 |
Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 217.66.24.0/24 |
Tatarstan, Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.66.24.0/21 |
Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 217.173.16.0/21 |
Kazan, Tatarstan, Russia
|
2,048 | RIPE NCC | ASSIGNED PA |
| 217.173.21.0/24 |
Kazan, Tatarstan, Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.173.23.0/24 |
Kazan, Tatarstan, Russia
|
256 | RIPE NCC | ASSIGNED PA |
| 217.173.28.0/22 |
MTS PJSC
|
1,024 | RIPE NCC | ALLOCATED PA |
| 217.173.29.0/24 |
MTS PJSC
|
256 | RIPE NCC | ASSIGNED PA |
| 217.173.30.0/24 |
Nizhnekamskneftekhim Company
|
256 | RIPE NCC | ASSIGNED PA |
Peers
AS29194 does not have any direct peering agreements. Instead, its global connectivity is achieved through transit providers. While this setup ensures comprehensive reach, future peering could reduce latency and optimize route efficiency.
Upstreams
AS29194 connects to the global Internet via at least 1 upstream provider. In this setup, AS29194 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS29194 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.