5.140.168.0/22
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 | 5.136.0.0/13 |
| Registry | RIPE |
| ID | USI_ADSL_USERS |
WHOIS Details
inetnum: 5.140.112.0 - 5.140.255.255 netname: USI_ADSL_USERS descr: Dynamic distribution IP's for broadband services descr: OJSC Rostelecom, regional branch Urals country: RU admin-c: PRTT1-RIPE tech-c: RTNC-RIPE status: SUB-ALLOCATED PA mnt-domains: MFIST-MNT mnt-by: ROSTELECOM-MNT created: 2025-08-26T13:21:53Z last-modified: 2025-08-26T13:21:53Z source: RIPE abuse-email: [email protected] abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE role: PJSC Rostelecom Technical Team address: PJSC Rostelecom Russian Federation e-mail: [email protected] nic-hdl: PRTT1-RIPE mnt-by: ROSTELECOM-MNT created: 2024-05-20T01:54:00Z last-modified: 2024-05-20T01:54:00Z source: RIPE role: PJSC Rostelecom Technical Team address: PJSC Rostelecom address: Russian Federation e-mail: [email protected] abuse-mailbox: [email protected] admin-c: IE1277-RIPE tech-c: IE1277-RIPE remarks: trouble: --------------------------------------------------------------- remarks: trouble: Rostelecom NOC is available 24 x 7 remarks: trouble: e-mail [email protected] remarks: trouble: --------------------------------------------------------------- remarks: ------------------------------------------------------------------------ remarks: peering requests: [email protected] remarks: ------------------------------------------------------------------------ remarks: http://www.rostelecom.ru/, looking-glass http://lg.ip.rt.ru/ remarks: ------------------------------------------------------------------------ notify: [email protected] nic-hdl: RTNC-RIPE mnt-by: ROSTELECOM-MNT created: 2007-11-27T13:28:11Z last-modified: 2022-12-12T07:46:18Z source: RIPE route: 5.136.0.0/13 origin: AS12389 mnt-by: ROSTELECOM-MNT created: 2024-04-03T08:47:21Z last-modified: 2024-04-03T08:47:21Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 5.140.168.0/22
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 5.136.0.0/13 | AS12389 | PJSC Rostelecom | 524,288 |
| 5.136.0.0/13 | AS197571 | PJSC Rostelecom | 524,288 |
| 5.136.0.0/13 | AS50714 | PJSC Rostelecom | 524,288 |
Nearby Ranges
BGP prefixes that overlap with 5.140.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 5.136.0.0/13 | AS12389 | PJSC Rostelecom | 524,288 |
| 5.136.0.0/13 | AS197571 | PJSC Rostelecom | 524,288 |
| 5.136.0.0/13 | AS50714 | PJSC Rostelecom | 524,288 |
| 5.140.64.0/19 | AS12389 | Dynamic distribution IP's for broadband services | 8,192 |
| 5.140.0.0/19 | AS12389 | Dynamic distribution IP's for broadband services | 8,192 |
| 5.140.48.0/20 | AS12389 | Dynamic distribution IP's for broadband services | 4,096 |
| 5.140.96.0/20 | AS12389 | Dynamic distribution IP's for broadband services | 4,096 |
| 5.140.32.0/20 | AS12389 | Dynamic distribution IP's for broadband services | 4,096 |
Hosted domains
There are 6 domain names hosted across 4 IP addresses on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|---|---|
| 5.140.171.210 | api-monitoring.ru | 3 |
| 5.140.168.162 | a-okami.ru | 1 |
| 5.140.168.94 | uvoural.ru | 1 |
| 5.140.168.113 | uprcom.su | 1 |
Hosted domains API
Pingable IPs
190 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 5.140.168.5 |
0.74ms from Yekaterinburg,
RU
|
|
| 5.140.170.5 |
1.21ms from Yekaterinburg,
RU
|
|
| 5.140.169.180 |
8.73ms from Yekaterinburg,
RU
|
|
| 5.140.171.89 |
0.15ms from Yekaterinburg,
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 |
|---|---|---|
| 104.151.225.150 |
3.10ms from Atlanta,
US
|
|
| 104.188.50.118 |
12.00ms from Atlanta,
US
|
|
| 171.100.64.230 |
2.31ms from Bangkok,
TH
|
|
| 223.72.220.70 |
2.34ms from Beijing,
CN
|
|
| 201.185.115.134 |
6.51ms from Bogota,
CO
|
|
| 62.77.236.70 |
5.81ms from Budapest,
HU
|
|
| 103.110.7.150 |
0.53ms from Delhi,
IN
|
|
| 40.113.234.38 |
0.33ms from Des Moines,
US
|
|
| 212.193.23.22 |
0.51ms from Helsinki,
FI
|
|
| 88.157.156.54 |
0.32ms from Lisbon,
PT
|
|
| 72.193.141.54 |
9.73ms from Los Angeles,
US
|
|
| 44.198.2.6 |
0.22ms from Reston,
US
|
|
| 64.64.31.86 |
0.13ms from San Jose,
US
|
|
| 63.227.128.102 |
10.91ms from Seattle,
US
|
|
| 218.212.146.54 |
2.05ms from Singapore,
SG
|
|
| 87.118.168.102 |
2.63ms from Sofia,
BG
|
|
| 123.252.123.22 |
1.34ms from Taipei,
TW
|
|
| 126.78.51.70 |
3.13ms from Tokyo,
JP
|
|
| 70.31.146.38 |
1.72ms from Toronto,
CA
|
|
| 60.6.109.70 |
10.04ms from Beijing,
CN
|
|
| 16.145.218.166 |
0.13ms from Boardman,
US
|
|
| 162.230.46.102 |
14.90ms from Chicago,
US
|
|
| 24.106.133.102 |
10.86ms from Columbus,
US
|
|
| 23.95.47.230 |
0.31ms from Dallas,
US
|
|
| 79.201.122.118 |
7.08ms from Frankfurt am Main,
DE
|
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