2.60.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 | sibirtelecom.ru |
| ASN | AS12389 |
| Registry | RIPE |
| ID | WEBSTREAM |
WHOIS Details
inetnum: 2.60.0.0 - 2.60.31.255 netname: WEBSTREAM descr: OJSC Sibirtelecom remarks: Omsk branch of the OJSC Sibirtelecom remarks: broadband service country: RU remarks: remarks: NCC remarks: INFRA AW remarks: admin-c: VIK3-RIPE tech-c: VAZ14-RIPE mnt-by: ROSTELECOM-MNT status: ASSIGNED PA remarks: remarks: Direct reference for the general info on spam remarks: In unsoluble cases for the general info on spam, remarks: abusing & hacking complaints email abuse@omskelecom.ru remarks: notify: zinov@omskelecom.ru notify: lir@ncc.sibirtelecom.ru created: 2010-11-29T10:24:04Z last-modified: 2025-07-02T08:12:30Z source: RIPE abuse-email: abuse@rt.ru abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE person: Vitaly A. Zinovjev address: Omsk region Electric Communications Joint Stock Comp. address: 3, Gertsen st. address: Omsk, 644099, Russia phone: +7 3812 220107 fax-no: +7 3812 238473 e-mail: zinov@omskelecom.ru nic-hdl: VAZ14-RIPE notify: zinov@omskelecom.ru mnt-by: OEC-MNT created: 2002-12-04T04:19:57Z last-modified: 2004-07-01T07:26:58Z source: RIPE person: Vladimir I. Khlystov address: Omsk region Electric Communications Joint Stock Comp. address: 3, Gertsen st. address: Omsk, 644099 address: Russia phone: +7 3812 241219 fax-no: +7 3812 238473 e-mail: adm@omskelecom.ru nic-hdl: VIK3-RIPE notify: adm@omskelecom.ru mnt-by: OEC-MNT created: 1970-01-01T00:00:00Z last-modified: 2002-12-04T04:25:33Z source: RIPE route: 2.60.0.0/18 descr: JSC Rostelecom regional branch Siberia remarks: Omsk branch origin: AS12389 mnt-by: ROSTELECOM-MNT notify: lir@ncc.sibirtelecom.ru created: 2019-04-30T02:08:54Z last-modified: 2025-06-27T05:44:15Z source: RIPE
Hosted domains
There are no domains currently hosted on this ASN.
Hosted domains API
Pingable IPs
11,512 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 2.60.9.108 |
8.90ms from Novosibirsk,
RU
|
|
| 2.60.59.98 |
8.70ms from Novosibirsk,
RU
|
|
| 2.60.18.108 |
8.68ms from Novosibirsk,
RU
|
|
| 2.60.34.246 |
8.66ms from Novosibirsk,
RU
|
|
| 2.60.39.133 |
8.49ms from Novosibirsk,
RU
|
|
| 2.60.27.175 |
8.50ms from Novosibirsk,
RU
|
|
| 2.60.17.67 |
8.59ms from Novosibirsk,
RU
|
|
| 2.60.29.69 |
9.12ms from Novosibirsk,
RU
|
|
| 2.60.19.229 |
8.26ms from Novosibirsk,
RU
|
|
| 2.60.2.79 |
8.63ms from Novosibirsk,
RU
|
|
| 2.60.7.111 |
8.79ms from Novosibirsk,
RU
|
|
| 2.60.31.169 |
8.46ms from Novosibirsk,
RU
|
|
| 2.60.51.102 |
8.19ms from Novosibirsk,
RU
|
|
| 2.60.40.219 |
8.53ms from Novosibirsk,
RU
|
|
| 2.60.48.192 |
8.50ms from Novosibirsk,
RU
|
|
| 2.60.25.64 |
8.51ms from Novosibirsk,
RU
|
|
| 2.60.0.31 |
8.44ms from Novosibirsk,
RU
|
|
| 2.60.56.11 |
8.48ms from Novosibirsk,
RU
|
|
| 2.60.26.172 |
8.59ms from Novosibirsk,
RU
|
|
| 2.60.33.241 |
8.55ms from Novosibirsk,
RU
|
|
| 2.60.5.178 |
8.82ms from Novosibirsk,
RU
|
|
| 2.60.28.207 |
8.65ms from Novosibirsk,
RU
|
|
| 2.60.6.26 |
8.65ms from Novosibirsk,
RU
|
|
| 2.60.62.156 |
8.88ms from Novosibirsk,
RU
|
|
| 2.60.13.66 |
8.44ms from Novosibirsk,
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 |
|---|---|---|
| 58.96.104.2 |
4.89ms from Adelaide,
AU
|
|
| 45.88.57.130 |
0.77ms from Amsterdam,
NL
|
|
| 118.82.199.226 |
19.36ms from Auckland,
NZ
|
|
| 211.64.116.34 |
9.46ms from Beijing,
CN
|
|
| 202.4.182.242 |
1.23ms from Bengaluru,
IN
|
|
| 103.199.241.2 |
0.99ms from Chennai,
IN
|
|
| 96.11.167.226 |
4.04ms from Columbus,
US
|
|
| 14.181.131.34 |
2.78ms from Hanoi,
VN
|
|
| 66.193.202.194 |
1.52ms from Honolulu,
US
|
|
| 66.64.62.178 |
1.67ms from Houston,
US
|
|
| 75.148.219.18 |
9.91ms from Houston,
US
|
|
| 213.143.226.98 |
0.90ms from Istanbul,
TR
|
|
| 98.178.172.2 |
5.41ms from Kansas City,
US
|
|
| 37.229.163.146 |
8.60ms from Kyiv,
UA
|
|
| 38.96.42.194 |
4.07ms from Los Angeles,
US
|
|
| 216.17.93.34 |
0.49ms from Minneapolis,
US
|
|
| 12.89.106.178 |
2.85ms from New York City,
US
|
|
| 96.59.145.130 |
9.81ms from Orlando,
US
|
|
| 50.187.158.130 |
8.15ms from Providence,
US
|
|
| 157.56.209.178 |
0.34ms from Quincy,
US
|
|
| 96.92.95.242 |
5.80ms from Salt Lake City,
US
|
|
| 118.48.36.178 |
1.62ms from Seoul,
KR
|
|
| 125.136.123.226 |
5.66ms from Seoul,
KR
|
|
| 85.25.58.2 |
0.83ms from Strasbourg,
FR
|
|
| 3.25.142.210 |
0.41ms from Sydney,
AU
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Novosibirsk, 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