188.168.96.0/23
AS15774 · Limited Liability Company TTK-Svyaz
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
Russia
|
| Domain | ttk.ru |
| ASN | AS15774 |
| Parent Range | 188.168.0.0/16 |
| Registry | RIPE |
| ID | TTK-KAZAN |
WHOIS Details
inetnum: 188.168.96.0 - 188.168.96.255 netname: TTK-Kazan descr: PPPoE pool static country: RU admin-c: TTK52-RIPE tech-c: TTK52-RIPE notify: ripe@transtk.ru notify: noc@vtt.net notify: noc@volga.ttk.ru status: ASSIGNED PA mnt-by: MNT-TTK mnt-by: VTT-MNT remarks: infra-aw created: 2024-08-29T13:29:56Z last-modified: 2024-08-29T13:29:56Z source: RIPE abuse-email: a.zorin@ttk.ru abuse-c: AR63191-RIPE abuse-org: ORG-LLC51-RIPE role: NOC TTK-Volga address: JSC TransTeleCom Company Volga branch address: Russia, Nizhny Novgorod address: Semashko str,37 e-mail: noc@volga.ttk.ru e-mail: noc@vtt.net nic-hdl: TTK52-RIPE mnt-by: VTT-MNT abuse-mailbox: noc@volga.ttk.ru tech-c: IPv6-RU tech-c: CVB-RIPE admin-c: IPv6-RU created: 2013-05-31T07:23:37Z last-modified: 2024-11-04T17:09:32Z source: RIPE route: 188.168.0.0/16 descr: TTK-Retail route object origin: AS15774 mnt-by: MNT-TTK notify: lir-retail@ttk.ru created: 2009-07-31T11:13:58Z last-modified: 2009-11-09T10:18:38Z source: RIPE route: 188.168.0.0/16 descr: TTK-Retail route object origin: AS20485 mnt-by: TRANSTELECOM-MNT created: 2015-07-08T09:13:53Z last-modified: 2015-07-08T09:13:53Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 188.168.96.0/23
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 188.168.0.0/16 | AS15774 | Limited Liability Company TTK-Svyaz | 65,536 |
Nearby Ranges
BGP prefixes that overlap with 188.168.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 188.168.0.0/16 | AS15774 | Limited Liability Company TTK-Svyaz | 65,536 |
| 188.168.16.0/20 | AS15774 | TTK-Baikal/BRAS in Irkutsk (static pool) | 4,096 |
| 188.168.176.0/21 | AS15774 | (CL000844) Telesot, | 2,048 |
| 188.168.232.0/21 | AS15774 | Volga-TTK/BRAS3 in Saratov (subnet 2) | 2,048 |
| 188.168.80.0/21 | AS20485 | TTK-Chita/BRAS in Chita | 2,048 |
| 188.168.104.0/21 | AS15774 | TTK-Sever/BRAS2 in Yaroslavl | 2,048 |
| 188.168.216.0/21 | AS15774 | TTK-Sever/BRAS3 in Yaroslavl (subnet 3) | 2,048 |
| 188.168.40.0/21 | AS15774 | TTK-SZ/BRAS1 in SPb (static and dynamic pools) | 2,048 |
| 188.168.80.0/21 | AS15774 | TTK-Chita/BRAS in Chita | 2,048 |
| 188.168.240.0/21 | AS15774 | TTK-Volga/BRAS, Saratov | 2,048 |
| 188.168.144.0/21 | AS15774 | TTK-Baikal/BRAS in Irkutsk | 2,048 |
| 188.168.48.0/21 | AS15774 | TTK-Sever/BRAS1 in Yaroslavl (static and dynamic pools) | 2,048 |
| 188.168.160.0/21 | AS15774 | (MS003940) UV-TTK, | 2,048 |
| 188.168.152.0/21 | AS15774 | TTK-Baikal/BRAS in Irkutsk | 2,048 |
| 188.168.168.0/21 | AS15774 | TTK-Sahalin/BRAS in USahalinsk (ip-pools, server farm) | 2,048 |
| 188.168.224.0/22 | AS15774 | TTK-NN/BRAS in NN (PPPoE customers) | 1,024 |
| 188.168.252.0/22 | AS15774 | SPB-TTK /BRAS-Piter | 1,024 |
| 188.168.208.0/22 | AS20485 | (MS003877) CentrTTK , | 1,024 |
| 188.168.100.0/22 | AS20485 | TTK-Center/BRAS2 in Novomoskovsk (subnet 2) | 1,024 |
| 188.168.92.0/22 | AS15774 | TTK-NN/BRAS1 in NNovgorod | 1,024 |
| 188.168.64.0/22 | AS15774 | TTK-Sahalin/BRAS in USahalinsk (ip-pools, server farm) | 1,024 |
| 188.168.56.0/22 | AS15774 | TTK-Kavkaz/BRAS1 in Rostov-on-Don (static pool) | 1,024 |
| 188.168.88.0/22 | AS20485 | TTK-Center/BRAS1 in Novomoskovsk | 1,024 |
| 188.168.228.0/22 | AS15774 | TTK-Ural/BRAS in Ekaterinburg | 1,024 |
| 188.168.138.0/23 | AS20485 | (MS004164) Retail-KgdTTK, | 512 |
| 188.168.130.0/23 | AS15774 | IDLE_FOR_Kavkaz | 512 |
| 188.168.188.0/23 | AS15774 | PPPoE pool | 512 |
| 188.168.198.0/23 | AS15774 | TTK-Ural/BRAS in Ekaterinburg (PPoE ITR13895) | 512 |
| 188.168.2.0/23 | AS15774 | TTK-Samara/BRAS1 in Samara (dynamic and static pools) | 512 |
| 188.168.36.0/23 | AS15774 | TTK-Retail WiMax (dynamic pool) | 512 |
| 188.168.4.0/23 | AS15774 | TTK-Samara/BRAS2 in Samara (dynamic and static pools) | 512 |
| 188.168.6.0/23 | AS15774 | TTK-SZ/BRAS1 in SPb (second subnet) | 512 |
| 188.168.34.0/23 | AS20485 | TTK-Kaliningrad/BRAS1 in Kaliningrad (static pool) | 512 |
| 188.168.68.0/24 | AS20485 | TTK-Chita/BRAS4 in Chernyshevsk (PPPoE pool) | 256 |
| 188.168.15.0/24 | AS15774 | (MS004528) VolgaTransTelecom, | 256 |
| 188.168.143.0/24 | AS15774 | TTK-Ural/BRAS in Ekaterinburg | 256 |
| 188.168.60.0/24 | AS15774 | TTK-Chita/BRAS1 in Shilka (PPPoE pool) | 256 |
| 188.168.128.0/24 | AS15774 | TTK-Samara/Bras4 in Penza (dynamic pool) | 256 |
| 188.168.142.0/24 | AS15774 | (MS105000) TTK-Chita/BRAS, | 256 |
| 188.168.68.0/24 | AS15774 | TTK-Chita/BRAS4 in Chernyshevsk (PPPoE pool) | 256 |
| 188.168.69.0/24 | AS15774 | TTK-Chita/BRAS8 in Karymskoe | 256 |
| 188.168.70.0/24 | AS15774 | TTK-Ural/BRAS2 in Mendeleevo | 256 |
| 188.168.71.0/24 | AS15774 | TTK-Chita/BRAS in Shimanovsk | 256 |
| 188.168.141.0/24 | AS15774 | TTK-Ural/BRAS in Ekaterinburg | 256 |
| 188.168.14.0/24 | AS15774 | TTK-Samara/BRAS5 in Samara (dynamic and static pools) | 256 |
| 188.168.98.0/24 | AS15774 | TTK-Chita/BRAS in Svobodniy | 256 |
| 188.168.140.0/24 | AS15774 | (MS105000) TTK-Chita/BRAS, | 256 |
| 188.168.133.0/24 | AS15774 | TTC RETAIL POOL for corporate customers | 256 |
| 188.168.13.0/24 | AS15774 | TTK-Samara/BRAS2 in Ulyanovsk (dynamic and static pools) | 256 |
| 188.168.12.0/24 | AS15774 | TTK-Chita/BRAS1 in Hilok | 256 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
58 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 188.168.97.21 |
13.05ms from Moscow,
RU
|
|
| 188.168.96.159 |
11.69ms from Kazan,
RU
|
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 188.202.63.247 |
1.51ms from Amsterdam,
NL
|
|
| 175.16.233.231 |
3.10ms from Changchun,
CN
|
|
| 118.24.144.39 |
0.81ms from Chengdu,
CN
|
|
| 75.197.115.23 |
13.74ms from Chicago,
US
|
|
| 104.237.112.87 |
8.79ms from Chicago,
US
|
|
| 23.234.77.151 |
0.07ms from Durham,
US
|
|
| 45.200.192.183 |
0.25ms from Hong Kong,
HK
|
|
| 104.54.163.119 |
3.46ms from Houston,
US
|
|
| 73.155.103.39 |
3.47ms from Houston,
US
|
|
| 39.35.140.231 |
17.36ms from Islamabad,
PK
|
|
| 103.216.204.7 |
0.37ms from Kolkata,
IN
|
|
| 81.33.211.55 |
1.80ms from Madrid,
ES
|
|
| 84.121.98.167 |
11.64ms from Madrid,
ES
|
|
| 223.30.179.183 |
1.37ms from Mumbai,
IN
|
|
| 90.21.21.183 |
15.00ms from Paris,
FR
|
|
| 97.115.252.151 |
1.41ms from Portland,
US
|
|
| 178.164.34.199 |
8.54ms from Sandefjord,
NO
|
|
| 104.41.14.231 |
0.18ms from Sao Paulo,
BR
|
|
| 126.66.65.23 |
3.76ms from Tokyo,
JP
|
|
| 124.219.133.39 |
2.02ms from Tokyo,
JP
|
|
| 24.231.75.55 |
9.55ms from Toronto,
CA
|
|
| 144.202.132.87 |
2.40ms from Ashburn,
US
|
|
| 54.39.100.87 |
0.05ms from Beauharnois,
CA
|
|
| 190.228.226.151 |
1.49ms from Buenos Aires,
AR
|
|
| 34.68.115.23 |
0.10ms from Council Bluffs,
US
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all toolsSummarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs