Traceroute (api-manager.upbit.com)

Dallas, Texas, United States
%> traceroute api-manager.upbit.com
traceroute to 104.18.223.119 (104.18.223.119), 20 hops max, 60 byte packets
1 100.74.8.6 (100.74.8.6) 1.006 ms 0.941 ms *
2 100.74.8.3 (100.74.8.3) 0.892 ms * 100.74.8.2 (100.74.8.2) 0.843 ms
3 * * 174.127.115.6.static.midphase.com (174.127.115.6) 0.858 ms
4 206.53.202.83 (206.53.202.83) 3.166 ms 3.132 ms 3.612 ms
5 141.101.74.201 (141.101.74.201) 3.703 ms 206.53.202.83 (206.53.202.83) 3.638 ms 3.605 ms
6 104.18.223.119 (104.18.223.119) 3.148 ms 2.730 ms 2.848 ms
Amsterdam, North Holland, Netherlands
%> traceroute api-manager.upbit.com
traceroute to 104.18.217.119 (104.18.217.119), 20 hops max, 60 byte packets
1 1.169.172.83.in-addr.arpa (83.172.169.1) 0.380 ms 0.276 ms 0.311 ms
2 13335-am1-01-ix.equinix.com (185.1.112.26) 1.345 ms 1.561 ms 1.467 ms
3 141.101.65.113 (141.101.65.113) 2.481 ms 141.101.65.149 (141.101.65.149) 1.416 ms 141.101.65.2 (141.101.65.2) 1.652 ms
4 104.18.217.119 (104.18.217.119) 1.003 ms 0.995 ms 0.978 ms
Hong Kong
%> traceroute api-manager.upbit.com
traceroute to 104.18.223.119 (104.18.223.119), 20 hops max, 60 byte packets
1 1.248.57.103.in-addr.arpa (103.57.248.1) 0.479 ms 0.463 ms 0.527 ms
2 irb-1903.agg1v.hkg1.cn.m247.ro (82.102.29.1) 21.140 ms 8.557 ms 21.090 ms
3 146.70.0.2 (146.70.0.2) 0.757 ms 146.70.0.0 (146.70.0.0) 0.494 ms 146.70.0.2 (146.70.0.2) 0.750 ms
4 13335.hkg.equinix.com (36.255.56.48) 0.924 ms 0.995 ms be-1001.edge1.hkg1.cn.m247.ro (89.44.212.80) 0.403 ms
5 * 13335.hkg.equinix.com (36.255.56.48) 1.396 ms 1.381 ms
6 103.22.203.23 (103.22.203.23) 0.649 ms 104.18.223.119 (104.18.223.119) 0.519 ms 103.22.203.23 (103.22.203.23) 0.655 ms
Tokyo, Kanto, Japan
%> traceroute api-manager.upbit.com
traceroute to 104.18.217.119 (104.18.217.119), 20 hops max, 60 byte packets
1 * irb-115.agg1v.tyo1.jp.m247.ro (37.120.210.113) 9.285 ms *
2 ae101-3101.bb1.tyo1.jp.m247.ro (193.27.15.2) 0.450 ms ae102-3102.bb1.tyo1.jp.m247.ro (82.102.29.24) 0.436 ms 0.415 ms
3 101.203.88.62 (101.203.88.62) 1.587 ms 4.326 ms 1.428 ms
4 103.22.201.31 (103.22.201.31) 0.889 ms 103.22.201.38 (103.22.201.38) 0.730 ms 103.22.201.31 (103.22.201.31) 0.869 ms
5 104.18.217.119 (104.18.217.119) 0.675 ms 0.733 ms 0.853 ms
Singapore
%> traceroute api-manager.upbit.com
traceroute to 104.18.223.119 (104.18.223.119), 20 hops max, 60 byte packets
1 * * *
2 ae102-3102.bb2.wco1.sg.m247.ro (193.27.15.94) 0.686 ms 0.684 ms ae101-3101.bb1.wco1.sg.m247.ro (193.27.15.64) 0.313 ms
3 * 13335.sgw.equinix.com (27.111.230.2) 1.340 ms *
4 162.158.160.151 (162.158.160.151) 14.553 ms 162.158.160.43 (162.158.160.43) 0.921 ms *
5 * 104.18.223.119 (104.18.223.119) 0.670 ms 0.751 ms
London, England, United Kingdom
%> traceroute api-manager.upbit.com
traceroute to 104.18.223.119 (104.18.223.119), 20 hops max, 60 byte packets
1 * * *
2 * * *
3 et-0-1-8.bdr2-m23-lon2-uk.gb.as13213.net (212.78.92.182) 0.311 ms 0.289 ms et-1-1-8.bdr1-m22-lon2-uk.gb.as13213.net (212.78.92.218) 0.942 ms
4 98.158.181.203 (98.158.181.203) 0.577 ms 98.158.181.207 (98.158.181.207) 0.826 ms 0.804 ms
5 linx-lon1.as13335.net (195.66.225.179) 1.728 ms 1.347 ms 1.326 ms
6 141.101.71.117 (141.101.71.117) 3.475 ms 141.101.71.107 (141.101.71.107) 1.140 ms 141.101.71.135 (141.101.71.135) 1.469 ms
7 104.18.223.119 (104.18.223.119) 1.044 ms 1.030 ms 1.094 ms
Moscow, Moscow City, Russian Federation
%> traceroute api-manager.upbit.com
traceroute to 104.18.217.119 (104.18.217.119), 20 hops max, 60 byte packets
1 * 1.66.243.92.in-addr.arpa (92.243.66.1) 0.313 ms *
2 cloudflare.msk.cloud-ix.net (31.28.19.222) 4.713 ms 4.740 ms 4.686 ms
3 172.68.8.51 (172.68.8.51) 1.303 ms 172.68.8.53 (172.68.8.53) 5.226 ms 5.161 ms
4 104.18.217.119 (104.18.217.119) 1.399 ms 1.296 ms 1.312 ms

The Recent IP Traceroute Results