Autonomous System details
AS16285
Joint Stock Company Transtelecom — ttk.ru
Summary
| Country |
 Russian Federation
|
| Organization | Joint Stock Company Transtelecom |
| Domain | ttk.ru |
| Number of IPv4 | 46,080 |
| Number of IPv6 | 9.6560× 1029 |
| AS Type | ISP |
| Registry | RIPE NCC |
| Allocated | July 29, 2002 (about 23 years ago) |
| Updated | January 13, 2025 (about 3 months ago) |
IP Ranges
AS16285 announces 53 IPv4 ranges and 9 IPv6 ranges.
That's a total of 46,080 IPv4 addresses and 9.6560× 1029 IPv6 addresses.
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 37.209.224.0/24 |
Block Backbone of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 37.209.225.0/24 |
Block Backbone of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 37.209.226.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 37.209.228.0/24 |
Block Backbone of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 37.209.229.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 37.209.230.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 37.209.232.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 37.209.236.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 80.78.96.0/19 |
Cjsc Ural-transtelecom
|
8,192 | RIPE NCC | ASSIGNED PA |
| 80.78.105.0/24 |
Dialup Pool of Cjsc Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 80.78.124.0/23 |
Cjsc Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 80.78.126.0/24 |
Cjsc Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 83.222.64.0/22 |
Cjsc Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.222.68.0/22 |
Cjsc Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.222.72.0/23 |
Cjsc Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 83.222.74.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 83.222.76.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 83.222.78.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 83.222.79.0/24 |
Cjsc Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 83.222.80.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 83.222.81.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 83.222.82.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 83.222.84.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.222.88.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 83.222.92.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 83.222.94.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 185.7.40.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.68.128.0/21 |
Block Access of Ural-transtelecom
|
2,048 | RIPE NCC | ASSIGNED PA |
| 188.68.136.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 188.68.138.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 188.68.139.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 188.68.140.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.68.144.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.68.148.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.68.152.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 188.68.156.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 212.75.128.0/20 |
Block Access of Ural-transtelecom
|
4,096 | RIPE NCC | ASSIGNED PA |
| 212.75.144.0/21 |
Block Backbone of Ural-transtelecom
|
2,048 | RIPE NCC | ASSIGNED PA |
| 212.75.153.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 212.75.154.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 212.75.155.0/24 |
Block Access of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 212.75.156.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 213.141.224.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 213.141.228.0/22 |
Cjsc Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 213.141.232.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 213.141.234.0/24 |
LLC Ats-inform
|
256 | RIPE NCC | ASSIGNED PA |
| 213.141.235.0/24 |
Block Backbone of Ural-transtelecom
|
256 | RIPE NCC | ASSIGNED PA |
| 213.141.236.0/22 |
Block Backbone of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 213.141.238.0/24 |
LLC Onegin Plaza
|
256 | RIPE NCC | ASSIGNED PA |
| 213.141.244.0/23 |
Block Access of Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 213.141.246.0/23 |
Cjsc Ural-transtelecom
|
512 | RIPE NCC | ASSIGNED PA |
| 213.141.248.0/22 |
Block Access of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| 213.141.252.0/22 |
Block Backbone of Ural-transtelecom
|
1,024 | RIPE NCC | ASSIGNED PA |
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 2a03:6080::/29 |
Cjsc Ural-transtelecom
|
6.3383× 1029 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6080::/32 |
Cjsc Ural-transtelecom
|
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6080:4::/46 |
Block Access of Ural-transtelecom
|
4.8357× 1024 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6082::/32 |
Cjsc Ural-transtelecom
|
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6083::/36 |
Cjsc Ural-transtelecom
|
4.9518× 1027 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6083:8000::/36 |
Cjsc Ural-transtelecom
|
4.9518× 1027 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6083:c000::/36 |
Cjsc Ural-transtelecom
|
4.9518× 1027 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6084::/32 |
Cjsc Ural-transtelecom
|
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
| 2a03:6086::/32 |
Cjsc Ural-transtelecom
|
7.9228× 1028 | RIPE NCC | AGGREGATED-BY-LIR |
Peers
AS16285 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
AS16285 connects to the global Internet via at least 2 upstream providers. In this setup, AS16285 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS16285 serves as a transit provider the following ASes, delivering the BGP routes needed for global connectivity. This downstream relationship underscores AS16285's role in extending Internet access beyond its own infrastructure.