5.140.128.0/19
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 |
| 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: abuse@rt.ru abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE role: PJSC Rostelecom Technical Team address: PJSC Rostelecom Russian Federation e-mail: ripe.form@rt.ru 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: ripe@rt.ru abuse-mailbox: abuse@rt.ru admin-c: IE1277-RIPE tech-c: IE1277-RIPE remarks: trouble: --------------------------------------------------------------- remarks: trouble: Rostelecom NOC is available 24 x 7 remarks: trouble: e-mail cuss-ip@rt.ru remarks: trouble: --------------------------------------------------------------- remarks: ------------------------------------------------------------------------ remarks: peering requests: peering@rt.ru remarks: ------------------------------------------------------------------------ remarks: http://www.rostelecom.ru/, looking-glass http://lg.ip.rt.ru/ remarks: ------------------------------------------------------------------------ notify: ripe@rt.ru 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
Hosted domains
There is 1 domain name hosted across 1 IP address on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|
Hosted domains API
Pingable IPs
6,511 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 5.140.152.186 |
6.07ms from Yekaterinburg,
RU
|
|
| 5.140.142.143 |
5.41ms from Yekaterinburg,
RU
|
|
| 5.140.131.115 |
6.11ms from Yekaterinburg,
RU
|
|
| 5.140.149.50 |
6.51ms from Yekaterinburg,
RU
|
|
| 5.140.156.19 |
6.16ms from Yekaterinburg,
RU
|
|
| 5.140.150.150 |
5.46ms from Yekaterinburg,
RU
|
|
| 5.140.128.46 |
6.02ms from Yekaterinburg,
RU
|
|
| 5.140.138.170 |
5.70ms from Yekaterinburg,
RU
|
|
| 5.140.151.182 |
6.33ms from Yekaterinburg,
RU
|
|
| 5.140.143.19 |
5.39ms from Yekaterinburg,
RU
|
|
| 5.140.129.200 |
5.88ms from Yekaterinburg,
RU
|
|
| 5.140.153.173 |
5.82ms from Yekaterinburg,
RU
|
|
| 5.140.154.242 |
5.90ms from Yekaterinburg,
RU
|
|
| 5.140.140.96 |
6.19ms from Yekaterinburg,
RU
|
|
| 5.140.141.249 |
5.93ms from Yekaterinburg,
RU
|
|
| 5.140.147.185 |
6.35ms from Yekaterinburg,
RU
|
|
| 5.140.144.72 |
5.52ms from Yekaterinburg,
RU
|
|
| 5.140.135.111 |
5.59ms from Yekaterinburg,
RU
|
|
| 5.140.159.148 |
5.44ms from Yekaterinburg,
RU
|
|
| 5.140.132.196 |
6.04ms from Yekaterinburg,
RU
|
|
| 5.140.158.60 |
5.37ms from Yekaterinburg,
RU
|
|
| 5.140.136.169 |
6.32ms from Yekaterinburg,
RU
|
|
| 5.140.145.39 |
5.94ms from Yekaterinburg,
RU
|
|
| 5.140.157.133 |
5.90ms from Yekaterinburg,
RU
|
|
| 5.140.148.76 |
5.33ms 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 |
|---|---|---|
| 77.165.97.3 |
2.98ms from Amsterdam,
NL
|
|
| 13.69.31.179 |
0.20ms from Amsterdam,
NL
|
|
| 40.176.198.243 |
1.96ms from Calgary,
CA
|
|
| 8.33.248.3 |
6.87ms from Dallas,
US
|
|
| 176.147.195.179 |
6.34ms from Frankfurt am Main,
DE
|
|
| 46.142.179.35 |
7.13ms from Frankfurt am Main,
DE
|
|
| 163.202.232.35 |
2.01ms from Johannesburg,
ZA
|
|
| 212.171.68.51 |
12.05ms from Milan,
IT
|
|
| 180.146.182.179 |
2.01ms from Osaka,
JP
|
|
| 91.68.3.35 |
9.68ms from Paris,
FR
|
|
| 3.113.221.115 |
0.15ms from Tokyo,
JP
|
|
| 125.200.18.99 |
13.61ms from Tokyo,
JP
|
|
| 94.249.106.3 |
1.10ms from Amman,
JO
|
|
| 173.53.86.115 |
4.44ms from Ashburn,
US
|
|
| 31.32.246.83 |
7.97ms from Duesseldorf,
DE
|
|
| 199.185.210.3 |
0.64ms from Edmonton,
CA
|
|
| 181.66.87.163 |
18.16ms from Lima,
PE
|
|
| 34.142.126.195 |
0.09ms from London,
GB
|
|
| 143.0.7.227 |
14.54ms from Osasco,
BR
|
|
| 50.214.71.227 |
6.42ms from Portland,
US
|
|
| 52.7.38.195 |
0.20ms from Reston,
US
|
|
| 211.39.138.99 |
1.26ms from Seoul,
KR
|
|
| 122.214.151.195 |
1.01ms from Tokyo,
JP
|
|
| 222.230.190.35 |
0.84ms from Tokyo,
JP
|
|
| 213.42.212.115 |
2.05ms from Al Fujairah City,
AE
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Palermo, IT
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