AS60490
MTS PJSC — mtu.ru
Summary
Country |
![]() |
Organization | MTS PJSC |
Domain | mtu.ru |
Number of IPv4 | 19,200 |
Number of IPv6 | 1.5595× 1026 |
AS Type | Hosting |
Registry | RIPE NCC |
Allocated | July 11, 2013 (about 11 years ago) |
Updated | July 15, 2021 (about 3 years ago) |
IP Ranges
AS60490 announces 57 IPv4 ranges and 2 IPv6 ranges.
That's a total of 19,200 IPv4 addresses and 1.5595× 1026 IPv6 addresses.
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
77.105.177.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.178.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.179.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.180.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.182.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.185.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.186.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.187.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.190.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
77.105.191.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
89.22.168.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
89.22.169.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
89.22.180.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PI |
89.22.184.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PI |
89.22.185.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
89.22.186.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
89.22.187.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
91.185.81.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.84.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.85.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.86.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.88.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.90.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.91.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.93.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.94.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
91.185.95.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
176.109.67.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.70.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.72.0/21 |
![]() |
2,048 | RIPE NCC | ALLOCATED PA |
176.109.80.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.82.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.83.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.84.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.85.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.86.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.87.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.88.0/23 |
![]() |
512 | RIPE NCC | ALLOCATED PA |
176.109.90.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.92.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.94.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
176.109.95.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
178.236.18.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
178.236.19.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
178.236.22.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
178.236.23.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
185.47.36.0/22 |
![]() |
1,024 | RIPE NCC | ASSIGNED PA |
188.93.49.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
193.8.208.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
193.8.209.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
193.8.210.0/24 |
![]() |
256 | RIPE NCC | ALLOCATED PA |
194.113.236.0/23 |
![]() |
512 | RIPE NCC | ALLOCATED PA |
194.150.88.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
194.150.89.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
194.150.90.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
194.150.91.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PI |
212.6.56.0/24 |
![]() |
256 | RIPE NCC | ASSIGNED PA |
Prefix | Organization | Size | Registry | Status |
---|---|---|---|---|
2a02:28:7::/48 |
![]() |
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-LIR |
2a02:2a:1000::/41 |
![]() |
1.5474× 1026 | RIPE NCC | ALLOCATED-BY-RIR |
Peers
AS60490 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
AS60490 connects to the global Internet via at least 3 upstream providers. In this setup, AS60490 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS60490 serves as a transit provider the following ASes, delivering the BGP routes needed for global connectivity. This downstream relationship underscores AS60490's role in extending Internet access beyond its own infrastructure.