Search for "Korea Telecom"
| IP Pool | Country | State / Region | City | Coordinates | Timezone |
|---|---|---|---|---|---|
| 119.220.135.0 - 119.220.135.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.135.128 - 119.220.135.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.136.64 - 119.220.136.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.136.192 - 119.220.137.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.137.192 - 119.220.137.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.138.192 - 119.220.139.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.140.0 - 119.220.141.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.141.192 - 119.220.142.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.143.64 - 119.220.143.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.144.0 - 119.220.144.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.144.64 - 119.220.144.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.145.0 - 119.220.145.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.146.0 - 119.220.146.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.147.128 - 119.220.147.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.149.0 - 119.220.149.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.149.192 - 119.220.150.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.152.0 - 119.220.152.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.152.64 - 119.220.152.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.152.192 - 119.220.152.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.153.128 - 119.220.153.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.154.0 - 119.220.154.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.154.128 - 119.220.154.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.155.128 - 119.220.155.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.156.64 - 119.220.156.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.157.0 - 119.220.157.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.157.64 - 119.220.157.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.157.128 - 119.220.157.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.157.192 - 119.220.158.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.158.128 - 119.220.158.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.158.192 - 119.220.159.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.159.64 - 119.220.159.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.160.0 - 119.220.160.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.162.128 - 119.220.162.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.162.192 - 119.220.163.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.163.160 - 119.220.163.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.164.0 - 119.220.164.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.164.128 - 119.220.164.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.165.0 - 119.220.165.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.165.192 - 119.220.165.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.166.0 - 119.220.166.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.167.192 - 119.220.167.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.168.0 - 119.220.168.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.169.0 - 119.220.169.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.170.192 - 119.220.170.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.171.192 - 119.220.173.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.173.128 - 119.220.176.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.176.192 - 119.220.176.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.177.64 - 119.220.177.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.178.0 - 119.220.178.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.178.64 - 119.220.178.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.178.128 - 119.220.178.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.179.0 - 119.220.179.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.180.0 - 119.220.181.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.181.128 - 119.220.181.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.182.0 - 119.220.182.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.182.64 - 119.220.182.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.182.192 - 119.220.182.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.183.192 - 119.220.183.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.185.0 - 119.220.185.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.186.0 - 119.220.187.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.188.0 - 119.220.188.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.189.0 - 119.220.190.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.190.192 - 119.220.190.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.191.0 - 119.220.191.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.191.128 - 119.220.191.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.191.192 - 119.220.191.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.192.0 - 119.220.192.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.192.128 - 119.220.192.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.193.0 - 119.220.193.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.193.192 - 119.220.194.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.194.64 - 119.220.194.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.194.128 - 119.220.194.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.194.192 - 119.220.195.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.195.64 - 119.220.195.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.196.0 - 119.220.196.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.196.192 - 119.220.197.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.197.192 - 119.220.197.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si (Bundang-dong) ISP | ORG |
37.3671, 127.145 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.198.0 - 119.220.198.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.198.128 - 119.220.198.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.199.0 - 119.220.199.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.199.64 - 119.220.199.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.200.0 - 119.220.200.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.200.192 - 119.220.200.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.201.64 - 119.220.201.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.202.0 - 119.220.202.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.202.128 - 119.220.202.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.202.192 - 119.220.202.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.203.0 - 119.220.203.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.203.128 - 119.220.203.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.204.0 - 119.220.204.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.205.0 - 119.220.205.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.205.128 - 119.220.205.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.206.0 - 119.220.206.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.206.128 - 119.220.207.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.208.0 - 119.220.208.63 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.208.64 - 119.220.208.127 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.208.128 - 119.220.208.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.208.192 - 119.220.208.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.210.192 - 119.220.210.255 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
| 119.220.211.128 - 119.220.211.191 | South Korea ISP | ORG |
Gyeonggi-do ISP | ORG |
Seongnam-si ISP | ORG |
37.3827, 127.119 | Asia/Seoul (UTC+9) ISP | ORG |
Russian