178.35.64.0/18
AS12389 · PJSC Rostelecom
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 | rostelecom.ru |
| ASN | AS12389 |
| Parent Range | 178.35.0.0/17 |
| Registry | RIPE |
| ID | MACROREGIONAL_SOUTH |
WHOIS Details
inetnum: 178.35.0.0 - 178.35.127.255 netname: Macroregional_South descr: OJSC Rostelecom Macroregional Branch South descr: SOES, Vladikavkaz, Russia country: RU admin-c: BVV292-RIPE tech-c: BVV292-RIPE admin-c: SVS14-RIPE tech-c: SVS14-RIPE status: ASSIGNED PA notify: ssv@soes.su notify: geo@ns.kuban.ru mnt-by: STC-MNT created: 2010-01-21T15:57:26Z last-modified: 2021-07-21T12:48:06Z source: RIPE abuse-email: abuse@rt.ru abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE person: Bogdanov Vadim Victorovich address: vadim.bogdanov@south.rt.ru . Vladikavkaz, ul. Kirova 47. phone: +89897498498 nic-hdl: BVV292-RIPE mnt-by: STC-MNT created: 2021-07-21T12:30:38Z last-modified: 2021-07-21T12:30:38Z source: RIPE person: Sergey V Sorokin address: 14, Gorkogo Str.,362040, Vladikavkaz, RSO-A, Russia phone: +7(8672)500001 nic-hdl: SVS14-RIPE notify: ssv@soes.su created: 1970-01-01T00:00:00Z last-modified: 2020-06-04T10:25:31Z source: RIPE mnt-by: ROSTELECOM-MNT route: 178.35.0.0/17 descr: Rostelecom networks origin: AS12389 notify: ripe@rt.ru mnt-by: ROSTELECOM-MNT created: 2018-11-06T11:44:31Z last-modified: 2018-11-06T11:44:31Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 178.35.64.0/18
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 178.35.0.0/17 | AS12389 | OJSC Rostelecom Macroregional Branch South | 32,768 |
Nearby Ranges
BGP prefixes that overlap with 178.35.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 178.35.0.0/17 | AS12389 | OJSC Rostelecom Macroregional Branch South | 32,768 |
| 178.35.192.0/19 | AS35177 | OJSC Rostelecom Macroregional Branch South | 8,192 |
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
9,708 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 178.35.108.199 |
22.04ms from Samara,
RU
|
|
| 178.35.84.139 |
22.08ms from Samara,
RU
|
|
| 178.35.65.21 |
22.04ms from Samara,
RU
|
|
| 178.35.100.215 |
22.08ms from Samara,
RU
|
|
| 178.35.92.109 |
22.04ms from Samara,
RU
|
|
| 178.35.120.109 |
21.99ms from Samara,
RU
|
|
| 178.35.116.29 |
22.22ms from Samara,
RU
|
|
| 178.35.86.93 |
22.28ms from Samara,
RU
|
|
| 178.35.69.29 |
22.28ms from Samara,
RU
|
|
| 178.35.113.50 |
21.89ms from Samara,
RU
|
|
| 178.35.109.47 |
21.99ms from Samara,
RU
|
|
| 178.35.89.20 |
22.14ms from Samara,
RU
|
|
| 178.35.114.151 |
21.98ms from Samara,
RU
|
|
| 178.35.88.239 |
22.07ms from Samara,
RU
|
|
| 178.35.67.236 |
22.13ms from Samara,
RU
|
|
| 178.35.81.233 |
22.17ms from Samara,
RU
|
|
| 178.35.118.90 |
22.12ms from Samara,
RU
|
|
| 178.35.90.42 |
22.11ms from Samara,
RU
|
|
| 178.35.64.1 |
21.90ms from Samara,
RU
|
|
| 178.35.85.102 |
22.02ms from Samara,
RU
|
|
| 178.35.94.8 |
22.00ms from Samara,
RU
|
|
| 178.35.80.18 |
22.18ms from Samara,
RU
|
|
| 178.35.83.218 |
22.08ms from Samara,
RU
|
|
| 178.35.103.119 |
22.07ms from Samara,
RU
|
|
| 178.35.117.95 |
22.21ms from Samara,
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 |
|---|---|---|
| 44.205.47.194 |
0.51ms from Ashburn,
US
|
|
| 111.13.123.178 |
2.06ms from Beijing,
CN
|
|
| 185.232.216.2 |
4.52ms from Berlin,
DE
|
|
| 52.247.7.194 |
0.39ms from Boydton,
US
|
|
| 136.62.0.2 |
5.02ms from Dallas,
US
|
|
| 98.243.242.242 |
8.30ms from Flint,
US
|
|
| 89.114.239.98 |
3.58ms from Lisbon,
PT
|
|
| 93.56.209.2 |
2.72ms from Milan,
IT
|
|
| 93.56.52.194 |
0.81ms from Milan,
IT
|
|
| 87.241.49.98 |
0.70ms from Milan,
IT
|
|
| 180.137.106.162 |
3.18ms from Nanning,
CN
|
|
| 31.32.53.194 |
1.93ms from Paris,
FR
|
|
| 64.39.105.2 |
0.94ms from Phoenix,
US
|
|
| 67.85.158.130 |
3.80ms from Piscataway,
US
|
|
| 85.207.216.2 |
0.38ms from Prague,
CZ
|
|
| 31.37.180.2 |
6.07ms from Saint-Denis,
FR
|
|
| 45.38.154.98 |
0.21ms from Santa Clara,
US
|
|
| 199.250.57.34 |
4.48ms from Seattle,
US
|
|
| 91.25.154.130 |
1.03ms from Berlin,
DE
|
|
| 50.236.67.162 |
1.77ms from Boston,
US
|
|
| 66.69.142.18 |
5.28ms from Dallas,
US
|
|
| 115.208.208.34 |
8.96ms from Hangzhou,
CN
|
|
| 96.73.147.114 |
7.53ms from Herndon,
US
|
|
| 42.200.16.242 |
2.08ms from Hong Kong,
HK
|
|
| 96.66.142.146 |
6.87ms from Miami,
US
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Samara, RU
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 tools
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs