212.220.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 | 212.220.0.0/16 |
| Registry | RIPE |
| ID | RU-RTK-980311 |
WHOIS Details
inetnum: 212.220.0.0 - 212.220.255.255 netname: RU-RTK-980311 country: RU org: ORG-JR8-RIPE admin-c: PRTT1-RIPE tech-c: RTNC-RIPE status: ALLOCATED PA notify: [email protected] mnt-by: RIPE-NCC-HM-MNT mnt-by: ROSTELECOM-MNT mnt-lower: ROSTELECOM-MNT mnt-routes: ROSTELECOM-MNT created: 2002-04-17T07:41:29Z last-modified: 2024-06-04T11:37:33Z source: RIPE abuse-email: [email protected] abuse-c: RTNC-RIPE abuse-org: ORG-JR8-RIPE organisation: ORG-JR8-RIPE org-name: PJSC Rostelecom country: RU org-type: LIR address: 14 A, Sinopskaya nabereznaya address: 191167 address: S.Peterburg address: RUSSIAN FEDERATION phone: +7 499 999-82-83 fax-no: +74999953619 e-mail: [email protected] admin-c: PRTT1-RIPE admin-c: IE1277-RIPE admin-c: NM7547-RIPE admin-c: AA728-RIPE abuse-c: RTNC-RIPE mnt-ref: RIPE-NCC-HM-MNT mnt-ref: ROSTELECOM-MNT mnt-ref: ROSNIIROS-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: ROSTELECOM-MNT created: 2005-03-22T11:11:20Z last-modified: 2025-08-12T04:03:18Z source: RIPE abuse-email: [email protected] abuse-c: RTNC-RIPE abuse-org: undefined 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: 212.220.0.0/16 descr: Rostelecom networks (UR) origin: AS12389 notify: [email protected] mnt-by: ROSTELECOM-MNT created: 2018-09-27T08:58:22Z last-modified: 2018-09-27T08:58:22Z source: RIPE
Overlapping Ranges
BGP prefixes that contain 212.220.64.0/18
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 212.220.0.0/16 | AS12389 | PJSC Rostelecom | 65,536 |
Nearby Ranges
BGP prefixes that overlap with 212.220.0.0/16
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 212.220.0.0/16 | AS12389 | PJSC Rostelecom | 65,536 |
| 212.220.0.0/20 | AS12389 | Dynamic distribution IP's for broadband services | 4,096 |
| 212.220.198.0/23 | AS12389 | Uralsviazinform Corporative Network | 512 |
| 212.220.222.0/23 | AS6828 | Uralsviazinform - Internet v kredit | 512 |
Hosted domains
There are 96 domain names hosted across 63 IP addresses on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|---|---|
| 212.220.113.168 | gwitems.site | 3 |
| 212.220.99.164 | serova32.su | 2 |
| 212.220.105.29 | vboost.gg | 2 |
| 212.220.116.60 | 1xxx.win | 2 |
| 212.220.115.100 | involts.ru | 2 |
| 212.220.99.156 | xn--80akrjlccflc2b8e.xn--p1ai | 2 |
| 212.220.116.194 | seeleme.ru | 2 |
| 212.220.99.44 | dubass.ru | 1 |
| 212.220.115.151 | pakhandev.ru | 1 |
| 212.220.99.141 | rekuha.ru | 1 |
| 212.220.85.100 | wattbe.ru | 1 |
| 212.220.110.145 | nas-st.ru | 1 |
| 212.220.85.12 | bakovkin.ru | 1 |
| 212.220.124.131 | aleskovsky.ru | 1 |
| 212.220.113.90 | uprng.ru | 1 |
| 212.220.110.154 | nedosp.ru | 1 |
| 212.220.99.214 | holy-paradise.ru | 1 |
| 212.220.113.155 | bridge96.ru | 1 |
| 212.220.105.92 | pes70.ru | 1 |
| 212.220.115.204 | nrlogy.ru | 1 |
Hosted domains API
Pingable IPs
1,790 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 212.220.64.146 |
0.16ms from Yekaterinburg,
RU
|
|
| 212.220.74.193 |
0.91ms from Yekaterinburg,
RU
|
|
| 212.220.116.195 |
0.73ms from Yekaterinburg,
RU
|
|
| 212.220.90.33 |
0.75ms from Yekaterinburg,
RU
|
|
| 212.220.105.18 |
0.66ms from Yekaterinburg,
RU
|
|
| 212.220.92.1 |
0.81ms from Yekaterinburg,
RU
|
|
| 212.220.110.154 |
0.68ms from Yekaterinburg,
RU
|
|
| 212.220.91.41 |
0.83ms from Yekaterinburg,
RU
|
|
| 212.220.75.65 |
0.94ms from Yekaterinburg,
RU
|
|
| 212.220.71.177 |
0.75ms from Yekaterinburg,
RU
|
|
| 212.220.67.1 |
0.89ms from Yekaterinburg,
RU
|
|
| 212.220.78.241 |
0.82ms from Yekaterinburg,
RU
|
|
| 212.220.84.242 |
0.76ms from Yekaterinburg,
RU
|
|
| 212.220.113.14 |
0.76ms from Yekaterinburg,
RU
|
|
| 212.220.89.169 |
0.74ms from Yekaterinburg,
RU
|
|
| 212.220.79.165 |
0.82ms from Yekaterinburg,
RU
|
|
| 212.220.66.218 |
0.70ms from Yekaterinburg,
RU
|
|
| 212.220.73.118 |
0.80ms from Yekaterinburg,
RU
|
|
| 212.220.88.77 |
0.62ms from Yekaterinburg,
RU
|
|
| 212.220.76.81 |
0.85ms from Yekaterinburg,
RU
|
|
| 212.220.77.153 |
0.67ms from Yekaterinburg,
RU
|
|
| 212.220.115.118 |
0.70ms from Yekaterinburg,
RU
|
|
| 212.220.85.136 |
0.78ms from Yekaterinburg,
RU
|
|
| 212.220.83.53 |
0.75ms from Yekaterinburg,
RU
|
|
| 212.220.99.169 |
0.78ms 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 |
|---|---|---|
| 129.80.157.178 |
0.38ms from Ashburn,
US
|
|
| 51.0.141.2 |
0.71ms from Berlin,
DE
|
|
| 50.93.111.50 |
0.18ms from Boardman,
US
|
|
| 54.70.222.98 |
0.22ms from Boardman,
US
|
|
| 213.246.254.226 |
0.33ms from Brussels,
BE
|
|
| 170.81.230.98 |
13.14ms from Buenos Aires,
AR
|
|
| 97.209.66.242 |
15.49ms from Chicago,
US
|
|
| 82.206.164.2 |
3.39ms from Frankfurt am Main,
DE
|
|
| 5.146.155.98 |
10.86ms from Frankfurt am Main,
DE
|
|
| 84.130.32.98 |
9.66ms from Frankfurt am Main,
DE
|
|
| 84.144.159.82 |
4.35ms from Hamburg,
DE
|
|
| 194.215.93.162 |
2.70ms from Helsinki,
FI
|
|
| 88.115.244.2 |
0.54ms from Helsinki,
FI
|
|
| 198.51.50.210 |
8.53ms from Lincoln,
US
|
|
| 148.69.172.130 |
0.94ms from Lisbon,
PT
|
|
| 85.236.133.210 |
6.03ms from London,
GB
|
|
| 76.81.184.178 |
3.05ms from Los Angeles,
US
|
|
| 97.131.74.2 |
13.21ms from Los Angeles,
US
|
|
| 5.167.91.226 |
6.37ms from Moscow,
RU
|
|
| 148.137.147.82 |
11.22ms from New York City,
US
|
|
| 92.168.0.194 |
0.99ms from Paris,
FR
|
|
| 98.35.129.162 |
6.01ms from San Jose,
US
|
|
| 3.37.68.226 |
0.31ms from Seoul,
KR
|
|
| 61.35.196.2 |
2.49ms from Seoul,
KR
|
|
| 175.228.35.146 |
1.48ms from Seoul,
KR
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Ashburn, US
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