178.35.0.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.0.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,823 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 178.35.8.181 |
11.85ms from Krasnodar,
RU
|
|
| 178.35.13.113 |
11.83ms from Krasnodar,
RU
|
|
| 178.35.41.134 |
11.84ms from Krasnodar,
RU
|
|
| 178.35.49.221 |
11.87ms from Krasnodar,
RU
|
|
| 178.35.36.176 |
11.83ms from Krasnodar,
RU
|
|
| 178.35.31.184 |
11.80ms from Krasnodar,
RU
|
|
| 178.35.23.96 |
11.96ms from Krasnodar,
RU
|
|
| 178.35.3.157 |
11.85ms from Krasnodar,
RU
|
|
| 178.35.62.119 |
11.90ms from Krasnodar,
RU
|
|
| 178.35.58.33 |
11.73ms from Krasnodar,
RU
|
|
| 178.35.4.96 |
11.66ms from Krasnodar,
RU
|
|
| 178.35.27.100 |
11.75ms from Krasnodar,
RU
|
|
| 178.35.18.143 |
11.98ms from Krasnodar,
RU
|
|
| 178.35.54.148 |
11.97ms from Krasnodar,
RU
|
|
| 178.35.28.90 |
11.72ms from Krasnodar,
RU
|
|
| 178.35.52.56 |
11.58ms from Krasnodar,
RU
|
|
| 178.35.5.37 |
11.81ms from Krasnodar,
RU
|
|
| 178.35.33.142 |
11.80ms from Krasnodar,
RU
|
|
| 178.35.59.93 |
11.83ms from Krasnodar,
RU
|
|
| 178.35.21.64 |
11.81ms from Krasnodar,
RU
|
|
| 178.35.44.224 |
11.74ms from Krasnodar,
RU
|
|
| 178.35.53.65 |
11.62ms from Krasnodar,
RU
|
|
| 178.35.61.42 |
11.76ms from Krasnodar,
RU
|
|
| 178.35.20.209 |
11.88ms from Krasnodar,
RU
|
|
| 178.35.1.66 |
11.92ms from Krasnodar,
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 |
|---|---|---|
| 92.69.87.98 |
15.03ms from Amsterdam,
NL
|
|
| 20.71.3.82 |
0.23ms from Amsterdam,
NL
|
|
| 71.69.171.130 |
11.58ms from Ashburn,
US
|
|
| 161.199.214.2 |
14.61ms from Dallas,
US
|
|
| 122.179.105.50 |
6.49ms from Delhi,
IN
|
|
| 73.229.209.210 |
2.65ms from Denver,
US
|
|
| 54.170.224.98 |
0.25ms from Dublin,
IE
|
|
| 3.125.213.50 |
0.17ms from Frankfurt am Main,
DE
|
|
| 84.118.73.146 |
9.95ms from Frankfurt am Main,
DE
|
|
| 81.131.111.98 |
5.21ms from London,
GB
|
|
| 47.136.141.82 |
8.42ms from Los Angeles,
US
|
|
| 194.190.142.130 |
0.93ms from Moscow,
RU
|
|
| 196.207.31.2 |
0.66ms from Nairobi,
KE
|
|
| 37.49.234.66 |
0.37ms from Paris,
FR
|
|
| 172.110.187.242 |
2.12ms from Phoenix,
US
|
|
| 40.125.68.178 |
0.33ms from Quincy,
US
|
|
| 92.255.205.194 |
8.24ms from Samara,
RU
|
|
| 52.185.229.210 |
0.30ms from San Antonio,
US
|
|
| 220.78.230.18 |
1.96ms from Seoul,
KR
|
|
| 3.172.95.66 |
3.76ms from Sheffield,
GB
|
|
| 126.234.248.98 |
3.07ms from Tokyo,
JP
|
|
| 218.41.149.18 |
16.95ms from Tokyo,
JP
|
|
| 173.206.115.2 |
1.21ms from Toronto,
CA
|
|
| 20.104.110.2 |
0.20ms from Toronto,
CA
|
|
| 85.75.233.18 |
9.12ms from Athens,
GR
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Saint Petersburg, 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