Hatena::Grouptech

id:rx7(@namikawa)の技術メモ このページをアンテナに追加 RSSフィード

過去記事一覧 | Main Blog (元RX-7乗りの適当な日々) | SBM (id:rx7のBookmark)

2013/08/20

AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute

| AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ AWS(ap-northeast - Tokyo) to AWS(us-east - Northern Virginia)のtraceroute - id:rx7(@namikawa)の技術メモ のブックマークコメント


メモメモ。

上記エントリを書いたときに、AWS東京リージョンの各ゾーンに立ち上げたインスタンスを使って、

us-eastにあるインスタンスへの経路を調べてみた。そのログ。

もちろん経路は日に日によくなっていくと思うので、あくまで現時点のスナップショットの参考までに。


尚、「ap-northeast-1{a,b,c}」と呼ばれる3つのAvailability Zoneは、アカウントID毎にマッピングが違うので、注意してください。(私のアカウントが指す"ap-northeast-1a"と、貴方のアカウントが指している"ap-northeast-1a"は違うZoneかもしれない。)

↑の詳細は、昔のエントリですが、以下に詳細を書いています。


AWS東京リージョンとBGPピアを確立するとレイテンシはどう変わるか+α - 元RX-7乗りの適当な日々

どうも、ap-northeast-1bとap-northeast-1cについては、大阪のKDDI経由で海を渡っているように見えますね。

ap-northeast-1aは、東京のNTT経由で海を渡っているっぽい。

(今、思えばAS_PATHも出しておけばよかった。)


ap-northeast-1a

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-156-108-3.ap-northeast-1.compute.internal (10.156.108.3)  0.377 ms  0.483 ms  0.534 ms
 2  ip-10-1-26-9.ap-northeast-1.compute.internal (10.1.26.9)  0.499 ms  0.496 ms  0.705 ms
 3  ec2-175-41-192-20.ap-northeast-1.compute.amazonaws.com (175.41.192.20)  0.483 ms  0.723 ms  0.721 ms
 4  27.0.0.146 (27.0.0.146)  1.605 ms  1.635 ms  1.597 ms
 5  27.0.0.128 (27.0.0.128)  5.609 ms  5.631 ms  5.629 ms
 6  ae-10.r00.tokyjp03.jp.bb.gin.ntt.net (61.213.145.1)  2.236 ms  2.166 ms  2.337 ms
 7  ae-12.r25.tokyjp05.jp.bb.gin.ntt.net (129.250.2.4)  2.445 ms  2.919 ms  3.423 ms
 8  ae-13.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.6.191)  2.210 ms  2.493 ms  2.912 ms
 9  as-1.r20.sttlwa01.us.bb.gin.ntt.net (129.250.4.189)  110.040 ms  109.638 ms  109.528 ms
10  ae-0.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.54)  98.180 ms  95.605 ms  95.834 ms
11  ae-5.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.181)  178.537 ms  178.883 ms  166.984 ms
12  ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  180.304 ms ae-2.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.114)  180.557 ms  305.481 ms
13  ae-0.amazon.asbnva02.us.bb.gin.ntt.net (168.143.191.18)  181.180 ms  174.775 ms ae-2.amazon.asbnva02.us.bb.gin.ntt.net (168.143.228.38)  303.935 ms
14  72.21.220.29 (72.21.220.29)  179.761 ms 72.21.220.45 (72.21.220.45)  211.616 ms  211.171 ms
15  205.251.245.65 (205.251.245.65)  209.080 ms  233.459 ms  197.146 ms
16  * * *
17  * * *
18  * * *
19  216.182.224.73 (216.182.224.73)  167.761 ms  164.851 ms  168.619 ms
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  175.786 ms  167.933 ms  176.793 ms

ap-northeast-1b

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-160-160-3.ap-northeast-1.compute.internal (10.160.160.3)  0.403 ms  0.483 ms  0.641 ms
 2  ip-10-1-14-13.ap-northeast-1.compute.internal (10.1.14.13)  0.389 ms  0.620 ms  0.643 ms
 3  100.64.28.67 (100.64.28.67)  0.575 ms  0.691 ms  0.799 ms
 4  ec2-175-41-192-214.ap-northeast-1.compute.amazonaws.com (175.41.192.214)  0.619 ms  0.641 ms  0.635 ms
 5  27.0.0.210 (27.0.0.210)  61.510 ms  61.528 ms  61.524 ms
 6  27.0.0.196 (27.0.0.196)  11.319 ms  11.029 ms  11.037 ms
 7  113.157.231.13 (113.157.231.13)  11.600 ms  11.615 ms  11.602 ms
 8  obpjbb206.int-gw.kddi.ne.jp (118.155.199.69)  11.109 ms  11.237 ms  11.228 ms
 9  pajbb002.int-gw.kddi.ne.jp (203.181.100.186)  123.949 ms  123.966 ms  123.870 ms
10  ix-pa9.int-gw.kddi.ne.jp (111.87.3.78)  121.361 ms  121.353 ms  121.339 ms
11  xe-4-2-0.pao10.ip4.tinet.net (77.67.77.25)  125.929 ms  125.938 ms  126.145 ms
12  xe-5-1-0.was10.ip4.tinet.net (141.136.108.198)  205.577 ms  205.601 ms  196.477 ms
13  77.67.108.34 (77.67.108.34)  202.309 ms  202.414 ms  202.332 ms
14  72.21.220.69 (72.21.220.69)  200.366 ms  200.452 ms  200.329 ms
15  205.251.245.65 (205.251.245.65)  192.250 ms  192.317 ms  192.222 ms
16  * * *
17  * * *
18  * * *
19  216.182.224.209 (216.182.224.209)  201.964 ms  201.673 ms  202.144 ms
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  199.841 ms  200.351 ms  192.572 ms

ap-northeast-1c

$ traceroute -I hootsuite.com
traceroute to hootsuite.com (184.72.95.234), 30 hops max, 60 byte packets
 1  ip-10-118-37-193.ap-northeast-1.compute.internal (10.118.37.193)  0.851 ms  1.153 ms  1.431 ms
 2  100.65.9.15 (100.65.9.15)  0.692 ms  0.726 ms  0.722 ms
 3  100.65.9.38 (100.65.9.38)  0.588 ms  0.822 ms  0.845 ms
 4  100.66.56.1 (100.66.56.1)  0.445 ms  0.531 ms  0.675 ms
 5  100.64.12.75 (100.64.12.75)  0.604 ms  0.729 ms  0.836 ms
 6  ec2-175-41-192-202.ap-northeast-1.compute.amazonaws.com (175.41.192.202)  0.720 ms  0.517 ms  0.691 ms
 7  27.0.0.73 (27.0.0.73)  10.012 ms  9.987 ms  9.961 ms
 8  27.0.0.103 (27.0.0.103)  9.721 ms  9.997 ms  10.014 ms
 9  113.157.231.13 (113.157.231.13)  21.369 ms  21.376 ms  20.814 ms
10  obpjbb206.int-gw.kddi.ne.jp (118.155.199.65)  10.369 ms  10.582 ms  10.594 ms
11  pajbb002.int-gw.kddi.ne.jp (203.181.100.186)  122.456 ms  122.392 ms  122.376 ms
12  ix-pa9.int-gw.kddi.ne.jp (111.87.3.34)  124.511 ms  124.719 ms  124.539 ms
13  xe-4-2-0.pao10.ip4.tinet.net (77.67.77.25)  118.176 ms  117.697 ms  117.849 ms
14  xe-5-1-0.was10.ip4.tinet.net (141.136.108.198)  193.591 ms  193.602 ms  193.617 ms
15  77.67.108.34 (77.67.108.34)  193.447 ms  194.641 ms  194.565 ms
16  72.21.220.69 (72.21.220.69)  187.107 ms  187.193 ms  187.341 ms
17  205.251.245.65 (205.251.245.65)  199.024 ms  198.700 ms  214.925 ms
18  * * *
19  * * *
20  * * *
21  216.182.224.79 (216.182.224.79)  201.972 ms  201.438 ms  201.600 ms
22  * * *
23  * * *
24  * * *
25  ec2-184-72-95-234.compute-1.amazonaws.com (184.72.95.234)  183.568 ms  183.584 ms  183.773 ms
トラックバック - http://tech.g.hatena.ne.jp/rx7/20130820

2012/07/26

High I/O Quadruple Extra Large Instance (hi1.4xlarge) のスペック

| High I/O Quadruple Extra Large Instance (hi1.4xlarge) のスペック - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - High I/O Quadruple Extra Large Instance (hi1.4xlarge) のスペック - id:rx7(@namikawa)の技術メモ High I/O Quadruple Extra Large Instance (hi1.4xlarge) のスペック - id:rx7(@namikawa)の技術メモ のブックマークコメント

「Amazon Linux AMI 2012.03」の64bitでチェック。

f:id:rx7:20120726212210p:image


メモリは60.5GB

# cat /proc/meminfo
MemTotal:       62168992 kB
MemFree:        61845164 kB
Buffers:            6820 kB
Cached:           137948 kB
SwapCached:            0 kB
Active:           138104 kB
Inactive:          29500 kB
Active(anon):      22904 kB
Inactive(anon):        8 kB
Active(file):     115200 kB
Inactive(file):    29492 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:         22904 kB
Mapped:             7832 kB
Shmem:                64 kB
Slab:              27276 kB
SReclaimable:      10272 kB
SUnreclaim:        17004 kB
KernelStack:        1120 kB
PageTables:         2588 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    31084496 kB
Committed_AS:      69828 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      116104 kB
VmallocChunk:   34359620200 kB
DirectMap4k:    63496192 kB
DirectMap2M:           0 kB


CPUは、Intel Xeon E5620が2つ積まれていると思われる。8コア x 2 (HT)

# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
stepping        : 2
microcode       : 0x13
cpu MHz         : 2400.084
cache size      : 12288 KB
physical id     : 0
siblings        : 16
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 32
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu de tsc msr pae cx8 sep cmov pat clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl nonstop_tsc pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 popcnt aes hypervisor lahf_lm arat dts
bogomips        : 4800.16
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

・・・・・15までズラッと

おまけ。

# cat /proc/version
Linux version 3.2.21-1.32.6.amzn1.x86_64 (mockbuild@gobi-build-31004) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Sat Jun 23 02:32:15 UTC 2012
トラックバック - http://tech.g.hatena.ne.jp/rx7/20120726

2010/07/24

ap-southeastからのtraceroute

| ap-southeastからのtraceroute - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - ap-southeastからのtraceroute - id:rx7(@namikawa)の技術メモ ap-southeastからのtraceroute - id:rx7(@namikawa)の技術メモ のブックマークコメント

ap-southeastリージョンのAmazon EC2インスタンスにてtracerouteを実行。

いくつか思いついたものだけ。ロサンゼルス経由のルートになっているものも有り。


www.google.co.jp

$ traceroute www.google.co.jp
traceroute to www.google.co.jp (72.14.254.104), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.606 ms  0.557 ms  0.545 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.297 ms  0.352 ms  0.342 ms
 3  203.83.223.22 (203.83.223.22)  0.791 ms  0.837 ms  0.767 ms
 4  203.83.223.3 (203.83.223.3)  44.094 ms  44.086 ms  44.079 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.116 ms  1.097 ms  1.095 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.558 ms  78.450 ms  78.391 ms
 7  xe-4-1.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.154)  78.694 ms  78.608 ms  78.636 ms
 8  xe-1-3.a17.tokyjp01.jp.ra.gin.ntt.net (61.213.169.174)  76.124 ms  76.114 ms  76.104 ms
 9  209.85.241.90 (209.85.241.90)  77.031 ms 209.85.241.94 (209.85.241.94)  76.413 ms  76.408 ms
10  209.85.255.36 (209.85.255.36)  76.780 ms  76.683 ms  85.005 ms
11  72.14.232.114 (72.14.232.114)  76.417 ms  77.111 ms  76.726 ms
12  72.14.233.107 (72.14.233.107)  77.266 ms  77.204 ms  77.123 ms
13  sin01s04-in-f104.1e100.net (72.14.254.104)  76.254 ms  76.533 ms  76.179 ms

www.yahoo.co.jp

$ traceroute www.yahoo.co.jp
traceroute to www.yahoo.co.jp (124.83.147.204), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.537 ms  0.513 ms  0.502 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.393 ms  0.386 ms  0.466 ms
 3  203.83.223.22 (203.83.223.22)  0.720 ms  0.772 ms  0.828 ms
 4  203.83.223.3 (203.83.223.3)  1.687 ms  1.677 ms  1.666 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.042 ms  1.033 ms  1.072 ms
 6  as-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.20)  84.936 ms  71.572 ms  71.563 ms
 7  ae-6.r20.osakjp01.jp.bb.gin.ntt.net (129.250.5.153)  91.959 ms  91.956 ms  91.924 ms
 8  ae-1.a20.osakjp01.jp.ra.gin.ntt.net (61.200.80.130)  97.304 ms  97.295 ms  81.863 ms
 9  61.200.82.38 (61.200.82.38)  82.575 ms  80.618 ms  96.041 ms
10  124.83.128.26 (124.83.128.26)  98.070 ms  84.618 ms  82.717 ms
11  124.83.128.50 (124.83.128.50)  99.345 ms 124.83.128.42 (124.83.128.42)  84.553 ms  82.609 ms
12  124.83.128.50 (124.83.128.50)  84.176 ms !X * *

www.hatena.ne.jp

$ traceroute www.hatena.ne.jp
traceroute to www.hatena.ne.jp (59.106.108.86), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  20.263 ms  20.228 ms  20.212 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  20.190 ms  20.186 ms  20.175 ms
 3  203.83.223.22 (203.83.223.22)  20.171 ms  20.161 ms  20.150 ms
 4  203.83.223.3 (203.83.223.3)  20.143 ms  20.136 ms  20.125 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  20.105 ms  20.093 ms  20.084 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.545 ms  78.487 ms  78.475 ms
 7  po-2.a14.tokyjp01.jp.ra.gin.ntt.net (203.105.72.150)  77.503 ms  77.545 ms  77.637 ms
 8  xe-1-3.a14.tokyjp01.jp.ra.gin.ntt.net (61.120.145.170)  77.373 ms  77.489 ms  77.479 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  59.106.82.204 (59.106.82.204)  79.131 ms  79.049 ms  79.035 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

mixi.jp

$ traceroute mixi.jp
traceroute to mixi.jp (219.112.246.197), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.656 ms  0.634 ms  0.623 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  31.643 ms  31.637 ms  31.627 ms
 3  203.83.223.22 (203.83.223.22)  0.803 ms  0.801 ms  0.808 ms
 4  203.83.223.3 (203.83.223.3)  1.661 ms  1.731 ms  1.723 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.032 ms  1.101 ms  1.090 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.710 ms  78.591 ms  78.580 ms
 7  ae-3.r21.osakjp01.jp.bb.gin.ntt.net (129.250.4.214)  85.941 ms  85.933 ms ae-6.r20.osakjp01.jp.bb.gin.ntt.net (129.250.5.153)  76.838 ms
 8  as-1.r20.lsanca03.us.bb.gin.ntt.net (129.250.3.201)  189.790 ms as-2.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.164)  179.043 ms po-2.r01.lsanca03.us.bb.gin.ntt.net (129.250.3.162)  190.168 ms
 9  po-1.r01.sttlwa01.us.bb.gin.ntt.net (129.250.3.37)  244.081 ms xe-9-0-0.edge1.SanJose3.level3.net (4.68.110.49)  188.337 ms  183.289 ms
10  xe-9-0-0.edge1.SanJose3.level3.net (4.68.110.49)  186.813 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75)  185.189 ms ae-4-90.edge2.LosAngeles9.Level3.net (4.69.144.207)  182.519 ms
11  ae-2-70.edge2.LosAngeles9.Level3.net (4.69.144.79)  188.946 ms KDDI-AMERIC.car1.SanJose2.Level3.net (4.59.0.10)  178.473 ms ae-31-51.ebr1.Seattle1.Level3.net (4.68.105.30)  198.736 ms
12  lacbb002.kddnet.ad.jp (59.128.2.105)  185.449 ms KDDI-AMERIC.car1.SanJose2.Level3.net (4.59.0.10)  180.409 ms ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49)  205.419 ms
13  otejbb203.kddnet.ad.jp (203.181.100.81)  186.605 ms ae-73-73.csw2.SanJose1.Level3.net (4.69.134.230)  198.185 ms lacbb002.kddnet.ad.jp (59.128.2.105)  197.107 ms
14  ae-31-99.car1.SanJose2.Level3.net (4.68.18.203)  196.742 ms ae-21-69.car1.SanJose2.Level3.net (4.68.18.11)  224.399 ms ae-11-79.car1.SanJose2.Level3.net (4.68.18.75)  199.180 ms
15  cm-ote252.kddnet.ad.jp (59.128.7.145)  196.657 ms 124.215.198.38 (124.215.198.38)  301.526 ms KDDI-AMERIC.car1.SanJose2.Level3.net (4.59.0.10)  219.187 ms
16  pacbb002.kddnet.ad.jp (124.211.34.129)  190.389 ms 6-244-112-219.skyarena.com (219.112.244.6)  311.615 ms pacbb002.kddnet.ad.jp (124.211.34.129)  190.691 ms
17  * otejbb204.kddnet.ad.jp (203.181.100.109)  225.129 ms otejbb203.kddnet.ad.jp (203.181.100.85)  225.957 ms
18  cm-ote252.kddnet.ad.jp (59.128.7.209)  214.385 ms  232.386 ms *
19  * 124.215.198.38 (124.215.198.38)  308.376 ms  305.617 ms
20  157-244-112-219.skyarena.com (219.112.244.157)  290.269 ms !X * *

mixi宛は、エラい時間かかってる。ロサンゼルス経由。*.kddnet.ad.jp


$ ping mixi.jp
PING mixi.jp (219.112.246.202) 56(84) bytes of data.
64 bytes from m4-219-112-246-202.mixi.jp (219.112.246.202): icmp_seq=1 ttl=46 time=298 ms
64 bytes from m4-219-112-246-202.mixi.jp (219.112.246.202): icmp_seq=2 ttl=46 time=294 ms
64 bytes from m4-219-112-246-202.mixi.jp (219.112.246.202): icmp_seq=3 ttl=46 time=301 ms
64 bytes from m4-219-112-246-202.mixi.jp (219.112.246.202): icmp_seq=4 ttl=46 time=295 ms
64 bytes from m4-219-112-246-202.mixi.jp (219.112.246.202): icmp_seq=5 ttl=46 time=301 ms

--- mixi.jp ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 294.723/298.412/301.599/3.009 ms

この通り。


gree.jp

$ traceroute gree.jp
traceroute to gree.jp (112.137.188.44), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.658 ms  0.638 ms  0.627 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.425 ms  0.420 ms  0.407 ms
 3  203.83.223.22 (203.83.223.22)  0.766 ms  0.816 ms  0.804 ms
 4  203.83.223.3 (203.83.223.3)  1.720 ms  1.714 ms  1.705 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.100 ms  1.164 ms  1.156 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  88.306 ms  87.983 ms  87.970 ms
 7  ae-5.a21.tokyjp01.jp.ra.gin.ntt.net (61.213.162.174)  77.326 ms  77.296 ms  77.284 ms
 8  xe-4-1-0.a21.tokyjp01.jp.ra.gin.ntt.net (61.120.145.198)  79.314 ms  79.241 ms  79.281 ms
 9  * * *
10  * * *
11  * * *
12  61.206.157.54 (61.206.157.54)  79.430 ms  79.327 ms  79.350 ms
13  203.140.224.98 (203.140.224.98)  78.102 ms  78.113 ms  78.103 ms
14  203.140.224.81 (203.140.224.81)  78.425 ms  78.233 ms  78.174 ms
15  112.137.191.2 (112.137.191.2)  79.657 ms  79.577 ms  79.592 ms
16  112-137-184-13.gree.jp (112.137.184.13)  79.049 ms  79.032 ms  81.265 ms
17  112-137-188-44.gree.jp (112.137.188.44)  78.242 ms  78.218 ms  78.121 ms

www.livedoor.com

$ traceroute www.livedoor.com
traceroute to www.livedoor.com (125.6.172.15), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.556 ms  0.517 ms  0.504 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.381 ms  0.377 ms  0.366 ms
 3  203.83.223.35 (203.83.223.35)  0.450 ms  0.446 ms  0.435 ms
 4  203.83.223.75 (203.83.223.75)  2.447 ms  2.442 ms  2.473 ms
 5  203.83.223.59 (203.83.223.59)  2.034 ms  2.027 ms  2.018 ms
 6  Gi10-3.gw5.sin1.asianetcom.net (203.192.168.65)  3.661 ms  3.385 ms  3.373 ms
 7  po1-1-0.cr1.nrt1.asianetcom.net (202.147.48.118)  183.840 ms  183.497 ms  183.884 ms
 8  po0-0.gw2.nrt1.asianetcom.net (202.147.0.206)  193.252 ms  193.306 ms  193.292 ms
 9  Livedoor.gw2.nrt1.asianetcom.net (203.192.131.250)  80.928 ms  80.940 ms  80.936 ms
10  m320-1-ae2.data-hotel.net (203.174.64.9)  80.916 ms  80.904 ms  80.892 ms
11  240-1-xe100.data-hotel.net (203.174.64.138)  80.979 ms  80.969 ms  80.948 ms
12  c65-5b-R-v40.data-hotel.net (203.174.64.166)  80.835 ms  80.842 ms  81.004 ms
13  125-6-172-15.data-hotel.net (125.6.172.15)  80.945 ms  81.116 ms  81.079 ms

twitter.com

$ traceroute twitter.com
traceroute to twitter.com (128.242.240.148), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.524 ms  0.508 ms  0.495 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  27.659 ms  27.650 ms  27.641 ms
 3  203.83.223.22 (203.83.223.22)  0.768 ms  0.825 ms  0.817 ms
 4  203.83.223.3 (203.83.223.3)  1.655 ms  1.647 ms  1.640 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.056 ms  1.049 ms  1.098 ms
 6  as-1.r22.tokyjp01.jp.bb.gin.ntt.net (129.250.5.20)  70.311 ms  71.839 ms  71.825 ms
 7  ae-6.r20.osakjp01.jp.bb.gin.ntt.net (129.250.5.153)  92.316 ms  92.231 ms  92.314 ms
 8  as-2.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.164)  194.259 ms  220.872 ms  207.469 ms
 9  ae-2.r20.mlpsca01.us.bb.gin.ntt.net (129.250.5.6)  182.544 ms  191.306 ms  193.795 ms
10  mg-1.c20.mlpsca01.us.da.verio.net (129.250.28.81)  194.888 ms  192.347 ms  207.729 ms
11  128.241.122.213 (128.241.122.213)  193.246 ms  182.399 ms  193.579 ms
12  128.241.122.213 (128.241.122.213)  194.235 ms !X * *

おっと、これは日本国内ではなかったな。アメリカ西海岸。


www.iij.ad.jp

$ traceroute www.iij.ad.jp
traceroute to www.iij.ad.jp (210.130.137.80), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  17.207 ms  17.181 ms  17.169 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  17.135 ms  17.141 ms  17.131 ms
 3  203.83.223.22 (203.83.223.22)  17.126 ms  17.113 ms  17.103 ms
 4  203.83.223.3 (203.83.223.3)  17.098 ms  17.089 ms  17.078 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  17.062 ms  17.054 ms  17.045 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.820 ms  78.709 ms  78.573 ms
 7  ae-2.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.3.209)  74.634 ms  74.650 ms  74.642 ms
 8  po-1.a15.tokyjp01.jp.ra.gin.ntt.net (203.105.72.154)  77.482 ms  77.623 ms  77.545 ms
 9  210.173.177.6 (210.173.177.6)  79.305 ms  79.422 ms  79.414 ms
10  tky001bf00.IIJ.Net (58.138.80.121)  79.407 ms  79.502 ms tky008bf01.IIJ.Net (58.138.80.133)  80.586 ms
11  tky008bb00.IIJ.Net (58.138.80.70)  80.450 ms tky008bb01.IIJ.Net (58.138.80.242)  80.092 ms tky008bb00.IIJ.Net (58.138.80.50)  80.416 ms
12  tky008agr00.IIJ.Net (58.138.104.30)  80.605 ms  80.354 ms tky008agr00.IIJ.Net (58.138.104.26)  79.874 ms
13  www-v4.iij.ad.jp (210.130.137.80)  79.483 ms  80.170 ms  79.847 ms

www.ocn.ne.jp

$ traceroute www.ocn.ne.jp
traceroute to www.ocn.ne.jp (210.163.219.84), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.574 ms  0.534 ms  0.523 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.340 ms  0.374 ms  0.365 ms
 3  203.83.223.22 (203.83.223.22)  1.026 ms  1.018 ms  1.010 ms
 4  203.83.223.3 (203.83.223.3)  1.770 ms  1.764 ms  1.756 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.084 ms  1.075 ms  1.116 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.756 ms  78.661 ms  78.626 ms
 7  ae-2.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.3.209)  74.635 ms  74.775 ms  74.765 ms
 8  129.250.11.114 (129.250.11.114)  78.877 ms  100.120 ms  100.101 ms
 9  122.28.104.177 (122.28.104.177)  100.090 ms  100.083 ms 210.254.187.185 (210.254.187.185)  77.617 ms
10  118.23.168.2 (118.23.168.2)  77.921 ms 60.37.27.130 (60.37.27.130)  99.434 ms 118.23.168.2 (118.23.168.2)  99.413 ms
11  125.170.97.73 (125.170.97.73)  99.425 ms 122.1.245.9 (122.1.245.9)  78.523 ms  78.211 ms
12  210.254.188.238 (210.254.188.238)  78.517 ms  78.490 ms  78.523 ms
13  61.118.21.54 (61.118.21.54)  81.721 ms  81.767 ms 61.118.21.50 (61.118.21.50)  80.568 ms
14  210.227.235.18 (210.227.235.18)  84.924 ms  86.779 ms  85.030 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

www.kddi.com

$ traceroute www.kddi.com
traceroute to www.kddi.com (61.200.220.160), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  27.697 ms  27.674 ms  27.663 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  27.635 ms  27.629 ms  27.621 ms
 3  203.83.223.35 (203.83.223.35)  27.612 ms  27.606 ms  27.596 ms
 4  203.83.223.75 (203.83.223.75)  27.596 ms  27.589 ms  27.581 ms
 5  203.83.223.57 (203.83.223.57)  27.564 ms  27.556 ms  27.547 ms
 6  if-12-3.icore1.S9U-Singapore.as6453.net (116.0.83.69)  27.540 ms  2.681 ms  2.015 ms
 7  if-14-0-0-39.core1.S9R-Singapore.as6453.net (209.58.82.189)  2.152 ms  2.148 ms if-15-0-0-1125.core1.S9R-Singapore.as6453.net (116.0.83.22)  2.325 ms
 8  if-10-0-0.core2.S9R-Singapore.as6453.net (209.58.82.46)  2.364 ms  2.452 ms  2.439 ms
 9  if-10-0-0-1921.core1.TV2-Tokyo.as6453.net (209.58.96.38)  70.058 ms  70.121 ms Vlan10.ihar1.OVC-Tokyo.as6453.net (116.0.88.18)  86.473 ms
10  Vlan11.ihar2.OVC-Tokyo.as6453.net (209.58.61.26)  75.526 ms  75.649 ms 118.155.194.61 (118.155.194.61)  89.755 ms
11  Port-channel2.ihar1.OVC-Tokyo.as6453.net (116.0.91.2)  86.442 ms otecbb104.kddnet.ad.jp (124.211.33.67)  81.038 ms Port-channel2.ihar1.OVC-Tokyo.as6453.net (116.0.91.2)  86.422 ms
12  118.155.194.61 (118.155.194.61)  87.603 ms otejbb203.kddnet.ad.jp (59.128.4.161)  80.800 ms 118.155.194.61 (118.155.194.61)  87.458 ms
13  otecbb104.kddnet.ad.jp (124.211.33.67)  75.879 ms otecbb103.kddnet.ad.jp (124.211.33.65)  75.789 ms otecbb104.kddnet.ad.jp (124.211.33.67)  75.708 ms
14  otejbb203.kddnet.ad.jp (59.128.4.161)  75.879 ms  75.567 ms otejbb203.kddnet.ad.jp (59.128.4.165)  75.680 ms
15  sjkrgs001.kddnet.ad.jp (203.181.99.94)  75.893 ms  75.684 ms *
16  61.200.161.238 (61.200.161.238)  76.128 ms !X * *

www.biglobe.ne.jp

$ traceroute www.biglobe.ne.jp
traceroute to www.biglobe.ne.jp (111.168.16.65), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.606 ms  0.562 ms  0.550 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.354 ms  0.455 ms  0.446 ms
 3  203.83.223.22 (203.83.223.22)  0.745 ms  0.817 ms  0.804 ms
 4  203.83.223.3 (203.83.223.3)  1.715 ms  1.708 ms  1.700 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.071 ms  1.063 ms  1.108 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.605 ms  78.423 ms  78.430 ms
 7  po-2.a15.tokyjp01.jp.ra.gin.ntt.net (203.105.72.158)  78.719 ms  78.661 ms  78.725 ms
 8  203.105.72.194 (203.105.72.194)  78.498 ms  78.521 ms  78.488 ms
 9  122.133.0.6 (122.133.0.6)  104.400 ms  104.386 ms  104.371 ms
10  122.133.0.9 (122.133.0.9)  78.844 ms  78.729 ms  78.807 ms
11  133.205.46.42 (133.205.46.42)  80.367 ms  80.370 ms  80.388 ms
12  133.205.48.198 (133.205.48.198)  80.535 ms  80.410 ms  80.435 ms
13  133.205.48.42 (133.205.48.42)  79.203 ms  79.204 ms  79.303 ms
14  www.biglobe.ne.jp (111.168.16.65)  79.240 ms  79.239 ms  79.229 ms

www.u-netsurf.ne.jp

$ traceroute www.u-netsurf.ne.jp
traceroute to www.u-netsurf.ne.jp (202.233.2.250), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.664 ms  0.619 ms  0.608 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.390 ms  0.389 ms  0.379 ms
 3  203.83.223.22 (203.83.223.22)  2.544 ms  2.537 ms  2.571 ms
 4  203.83.223.3 (203.83.223.3)  1.707 ms  1.701 ms  1.691 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.082 ms  1.074 ms  1.121 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  78.572 ms  78.500 ms  78.486 ms
 7  po-2.a14.tokyjp01.jp.ra.gin.ntt.net (203.105.72.150)  77.416 ms  77.369 ms  77.444 ms
 8  xe-1-2.a14.tokyjp01.jp.ra.gin.ntt.net (61.213.161.6)  78.610 ms  78.566 ms  78.657 ms
 9  kddni1.asahi-net.or.jp (202.224.32.50)  77.436 ms  77.413 ms  77.503 ms
10  kdduni.asahi-net.or.jp (202.224.33.202)  77.771 ms  77.701 ms  77.759 ms
11  at-gate1-e1-1.netsurf.ad.jp (202.233.0.201)  77.806 ms  77.800 ms  77.748 ms
12  at-dist1-e1.netsurf.ad.jp (202.233.52.53)  79.386 ms  79.139 ms  79.227 ms
13  www.u-netsurf.ne.jp (202.233.2.250)  79.300 ms  79.290 ms  79.134 ms

www.dti.ad.jp

$ traceroute www.dti.ad.jp
traceroute to www.dti.ad.jp (202.216.229.65), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.440 ms  0.407 ms  0.482 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.369 ms  0.368 ms  0.359 ms
 3  203.83.223.35 (203.83.223.35)  27.440 ms  27.431 ms  27.429 ms
 4  203.83.223.75 (203.83.223.75)  2.361 ms  2.354 ms  2.451 ms
 5  203.83.223.57 (203.83.223.57)  1.935 ms  2.005 ms  1.995 ms
 6  if-12-3.icore1.S9U-Singapore.as6453.net (116.0.83.69)  27.340 ms  26.866 ms  26.692 ms
 7  Vlan1146.icore2.LAA-LosAngeles.as6453.net (116.0.83.34)  183.237 ms  183.344 ms  183.339 ms
 8  Vlan552.icore2.LAA-LosAngeles.as6453.net (216.6.84.66)  180.075 ms  180.195 ms  180.194 ms
 9  ae-1.r21.lsanca03.us.bb.gin.ntt.net (129.250.5.249)  183.531 ms  183.648 ms  183.503 ms
10  as-1.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.3.146)  195.527 ms  198.796 ms  197.854 ms
11  * * *
12  xe-3-4.a16.tokyjp01.jp.ra.gin.ntt.net (61.213.169.86)  183.146 ms  189.332 ms  189.828 ms
13  ix1-gate-oi1.oi.dti.ad.jp (202.216.225.182)  183.625 ms  183.638 ms  182.244 ms
14  core3-10.oi.dti.ad.jp (203.181.69.66)  182.736 ms  182.739 ms  182.726 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

ここも時間かかってる。ロス経由。


$ ping www.dti.ad.jp
PING www.dti.ad.jp (202.216.229.65) 56(84) bytes of data.
64 bytes from www00.dti.ad.jp (202.216.229.65): icmp_seq=1 ttl=53 time=184 ms
64 bytes from www00.dti.ad.jp (202.216.229.65): icmp_seq=2 ttl=53 time=183 ms
64 bytes from www00.dti.ad.jp (202.216.229.65): icmp_seq=3 ttl=53 time=182 ms
64 bytes from www00.dti.ad.jp (202.216.229.65): icmp_seq=4 ttl=53 time=184 ms
64 bytes from www00.dti.ad.jp (202.216.229.65): icmp_seq=5 ttl=53 time=185 ms

--- www.dti.ad.jp ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 182.975/184.113/185.021/0.831 ms

www.u-tokyo.ac.jp

$ traceroute www.u-tokyo.ac.jp
traceroute to www.u-tokyo.ac.jp (133.11.114.194), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.970 ms  0.937 ms  0.925 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.472 ms  0.467 ms  0.458 ms
 3  203.83.223.35 (203.83.223.35)  0.442 ms  0.428 ms  0.418 ms
 4  203.83.223.75 (203.83.223.75)  2.339 ms  2.329 ms  2.365 ms
 5  203.83.223.59 (203.83.223.59)  2.088 ms  2.082 ms  2.074 ms
 6  Gi10-3.gw5.sin1.asianetcom.net (203.192.168.65)  3.340 ms  3.063 ms  3.062 ms
 7  po13-1-1.cr2.nrt1.asianetcom.net (202.147.48.102)  183.118 ms  183.126 ms  183.119 ms
 8  ge-2-1-0-0.gw3.nrt5.asianetcom.net (202.147.0.182)  192.982 ms  193.131 ms  193.011 ms
 9  AS2907.ix.jpix.ad.jp (210.171.224.150)  81.638 ms  81.764 ms  81.874 ms
10  tokyo1-dc-RM-GE-1-2-0-102.sinet.ad.jp (150.99.189.125)  81.386 ms  81.381 ms  81.515 ms
11  UTnet-1.gw.sinet.ad.jp (150.99.190.102)  80.413 ms  80.224 ms  80.382 ms
12  ra36-vlan3.nc.u-tokyo.ac.jp (133.11.127.66)  80.378 ms  80.394 ms  80.494 ms
13  ra35.nc.u-tokyo.ac.jp (133.11.127.41)  79.011 ms  79.200 ms  79.071 ms
14  www.u-tokyo.ac.jp (133.11.114.194)  78.792 ms  78.778 ms  78.899 ms

www.kyoto-u.ac.jp

$ traceroute www.kyoto-u.ac.jp
traceroute to www.kyoto-u.ac.jp (130.54.120.215), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.604 ms  0.559 ms  0.551 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.524 ms  0.521 ms  0.514 ms
 3  203.83.223.35 (203.83.223.35)  0.500 ms  0.490 ms  0.468 ms
 4  203.83.223.75 (203.83.223.75)  2.556 ms  2.546 ms  2.537 ms
 5  203.83.223.57 (203.83.223.57)  2.047 ms  2.039 ms  2.068 ms
 6  Gi5-3.gw2.sin1.asianetcom.net (203.192.169.245)  6.205 ms  5.674 ms  5.663 ms
 7  gi0-0-0.gw5.sin1.asianetcom.net (202.147.48.94)  5.943 ms  5.938 ms  5.930 ms
 8  po13-1-1.cr2.nrt1.asianetcom.net (202.147.48.102)  183.369 ms  183.364 ms  183.355 ms
 9  ge-2-1-0-0.gw3.nrt5.asianetcom.net (202.147.0.182)  193.068 ms  192.874 ms  193.079 ms
10  AS2907.ix.jpix.ad.jp (210.171.224.150)  81.455 ms  81.400 ms  81.357 ms
11  tokyo1-dc-RM-GE-1-2-0-102.sinet.ad.jp (150.99.189.125)  81.167 ms  81.558 ms  81.356 ms
12  nagoya-dc-RM-AE-0-11.sinet.ad.jp (150.99.203.26)  87.567 ms  87.410 ms  87.321 ms
13  osaka-dc-RM-AE-0-11.sinet.ad.jp (150.99.203.30)  86.049 ms  86.040 ms  86.185 ms
14  kyoto-dc-RM-AE-0-11.sinet.ad.jp (150.99.203.34)  91.169 ms  91.153 ms  90.997 ms
15  www.kyoto-u.ac.jp (130.54.120.215)  91.375 ms !X  91.455 ms !X  91.421 ms !X

www.naist.jp

$ traceroute www.naist.jp
traceroute to www.naist.jp (163.221.80.83), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.381 ms  0.507 ms  0.497 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.332 ms  0.360 ms  0.351 ms
 3  203.83.223.22 (203.83.223.22)  0.878 ms  0.873 ms  0.906 ms
 4  203.83.223.3 (203.83.223.3)  1.720 ms  1.714 ms  1.705 ms
 5  xe-3-1-0.r02.sngpsi02.sg.bb.gin.ntt.net (129.250.11.209)  1.065 ms  1.050 ms  1.093 ms
 6  p64-4-1-2.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.6.21)  82.195 ms  81.917 ms  81.895 ms
 7  po-2.a15.tokyjp01.jp.ra.gin.ntt.net (203.105.72.158)  212.024 ms  212.096 ms  212.047 ms
 8  203.105.72.18 (203.105.72.18)  157.208 ms  156.498 ms  156.590 ms
 9  ve-61.cisco2.dojima.wide.ad.jp (203.178.136.238)  86.328 ms  86.323 ms  86.453 ms
10  ve-7.hitachi2.nara.wide.ad.jp (203.178.136.171)  89.071 ms  90.588 ms  92.870 ms
11  juniper-itc3.naist.jp (163.221.1.13)  85.788 ms  108.024 ms  108.010 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

www.riken.go.jp

$ traceroute www.riken.go.jp
traceroute to www.riken.go.jp (134.160.243.141), 30 hops max, 40 byte packets
 1  ip-10-128-68-2.ap-southeast-1.compute.internal (10.128.68.2)  0.623 ms  0.578 ms  0.568 ms
 2  ec2-175-41-128-21.ap-southeast-1.compute.amazonaws.com (175.41.128.21)  0.349 ms  0.343 ms  0.334 ms
 3  203.83.223.35 (203.83.223.35)  0.511 ms  0.505 ms  0.491 ms
 4  203.83.223.75 (203.83.223.75)  2.482 ms  2.477 ms  2.507 ms
 5  203.83.223.57 (203.83.223.57)  2.023 ms  2.016 ms  2.007 ms
 6  Gi5-3.gw2.sin1.asianetcom.net (203.192.169.245)  4.498 ms  4.364 ms  4.353 ms
 7  po15-0-1.cr1.nrt1.asianetcom.net (202.147.32.90)  193.140 ms  192.835 ms  192.897 ms
 8  gi1-0-0.cr2.nrt1.asianetcom.net (202.147.0.58)  183.168 ms  183.233 ms  183.388 ms
 9  ge-2-1-0-0.gw3.nrt5.asianetcom.net (202.147.0.182)  193.220 ms  193.060 ms  193.141 ms
10  AS2907.ix.jpix.ad.jp (210.171.224.150)  81.909 ms  81.426 ms  81.381 ms
11  tokyo1-dc-RM-GE-1-2-0-102.sinet.ad.jp (150.99.189.125)  81.501 ms  81.721 ms  81.628 ms
12  * * *
13  134.160.6.2 (134.160.6.2)  85.020 ms  84.918 ms  84.788 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
トラックバック - http://tech.g.hatena.ne.jp/rx7/20100724

2010/07/23

Amazon EC2の各リージョンから日本国内へのネットワークレイテンシ

| Amazon EC2の各リージョンから日本国内へのネットワークレイテンシ - id:rx7(@namikawa)の技術メモ を含むブックマーク はてなブックマーク - Amazon EC2の各リージョンから日本国内へのネットワークレイテンシ - id:rx7(@namikawa)の技術メモ Amazon EC2の各リージョンから日本国内へのネットワークレイテンシ - id:rx7(@namikawa)の技術メモ のブックマークコメント


レイテンシは「Amazon EC2/S3/他がアジア(シンガポール)で利用可能になったのでレイテンシを計測してみた - 元RX-7乗りの適当な日々」でも計測したのだけど、現在時点の各リージョンのEC2インスタンスから、日本のOCNトップとYahooトップにpingをうってみた結果。


・・・今思えば、tracerouteも取ればよかった。それはまた次回。


from "us-east"

$ ping www.ocn.ne.jp
PING www.ocn.ne.jp (210.163.219.84) 56(84) bytes of data.
64 bytes from 210.163.219.84: icmp_seq=1 ttl=109 time=185 ms
64 bytes from 210.163.219.84: icmp_seq=2 ttl=109 time=183 ms
64 bytes from 210.163.219.84: icmp_seq=3 ttl=109 time=183 ms
64 bytes from 210.163.219.84: icmp_seq=4 ttl=109 time=183 ms
64 bytes from 210.163.219.84: icmp_seq=5 ttl=108 time=178 ms
64 bytes from 210.163.219.84: icmp_seq=6 ttl=109 time=179 ms
64 bytes from 210.163.219.84: icmp_seq=7 ttl=109 time=184 ms
64 bytes from 210.163.219.84: icmp_seq=8 ttl=109 time=188 ms
64 bytes from 210.163.219.84: icmp_seq=9 ttl=108 time=185 ms
64 bytes from 210.163.219.84: icmp_seq=10 ttl=109 time=185 ms

--- www.ocn.ne.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9629ms
rtt min/avg/max/mdev = 178.961/183.920/188.417/2.735 ms
$ ping www.yahoo.co.jp
PING www.ya.gl.yahoo.co.jp (203.216.247.225) 56(84) bytes of data.
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=1 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=2 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=3 ttl=48 time=177 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=4 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=5 ttl=48 time=177 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=6 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=7 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=8 ttl=48 time=178 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=9 ttl=48 time=177 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=10 ttl=48 time=177 ms

--- www.ya.gl.yahoo.co.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9670ms
rtt min/avg/max/mdev = 177.818/178.129/178.605/0.639 ms

from "us-west"

$ ping www.ocn.ne.jp
PING www.ocn.ne.jp (210.163.219.84) 56(84) bytes of data.
64 bytes from 210.163.219.84: icmp_seq=1 ttl=111 time=128 ms
64 bytes from 210.163.219.84: icmp_seq=2 ttl=111 time=130 ms
64 bytes from 210.163.219.84: icmp_seq=3 ttl=111 time=133 ms
64 bytes from 210.163.219.84: icmp_seq=4 ttl=111 time=118 ms
64 bytes from 210.163.219.84: icmp_seq=5 ttl=111 time=130 ms
64 bytes from 210.163.219.84: icmp_seq=6 ttl=111 time=136 ms
64 bytes from 210.163.219.84: icmp_seq=7 ttl=111 time=118 ms
64 bytes from 210.163.219.84: icmp_seq=8 ttl=111 time=130 ms
64 bytes from 210.163.219.84: icmp_seq=9 ttl=111 time=131 ms
64 bytes from 210.163.219.84: icmp_seq=10 ttl=111 time=134 ms

--- www.ocn.ne.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8998ms
rtt min/avg/max/mdev = 118.585/129.306/136.206/5.712 ms
$ ping www.yahoo.co.jp
PING www.ya.gl.yahoo.co.jp (124.83.147.202) 56(84) bytes of data.
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=1 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=2 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=3 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=4 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=5 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=6 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=7 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=8 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=9 ttl=51 time=124 ms
64 bytes from f6.top.vip.ogk.yahoo.co.jp (124.83.147.202): icmp_seq=10 ttl=51 time=124 ms

--- www.ya.gl.yahoo.co.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 124.335/124.487/124.613/0.087 ms

from "eu-west"

$ ping www.ocn.ne.jp
PING www.ocn.ne.jp (210.163.219.84) 56(84) bytes of data.
64 bytes from 210.163.219.84: icmp_seq=1 ttl=111 time=276 ms
64 bytes from 210.163.219.84: icmp_seq=2 ttl=109 time=282 ms
64 bytes from 210.163.219.84: icmp_seq=3 ttl=109 time=280 ms
64 bytes from 210.163.219.84: icmp_seq=4 ttl=111 time=275 ms
64 bytes from 210.163.219.84: icmp_seq=5 ttl=109 time=280 ms
64 bytes from 210.163.219.84: icmp_seq=6 ttl=109 time=275 ms
64 bytes from 210.163.219.84: icmp_seq=7 ttl=111 time=281 ms
64 bytes from 210.163.219.84: icmp_seq=8 ttl=109 time=276 ms
64 bytes from 210.163.219.84: icmp_seq=9 ttl=109 time=280 ms
64 bytes from 210.163.219.84: icmp_seq=10 ttl=111 time=274 ms

--- www.ocn.ne.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8997ms
rtt min/avg/max/mdev = 274.329/278.324/282.850/2.961 ms
$ ping www.yahoo.co.jp
PING www.ya.gl.yahoo.co.jp (203.216.247.225) 56(84) bytes of data.
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=1 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=2 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=3 ttl=49 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=4 ttl=49 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=5 ttl=49 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=6 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=7 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=8 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=9 ttl=51 time=262 ms
64 bytes from f6.top.vip.tnz.yahoo.co.jp (203.216.247.225): icmp_seq=10 ttl=49 time=262 ms

--- www.ya.gl.yahoo.co.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8992ms
rtt min/avg/max/mdev = 262.155/262.590/262.851/0.600 ms

from "ap-southeast"

$ ping www.ocn.ne.jp
PING www.ocn.ne.jp (210.163.219.84) 56(84) bytes of data.
64 bytes from 210.163.219.84: icmp_seq=1 ttl=113 time=86.8 ms
64 bytes from 210.163.219.84: icmp_seq=2 ttl=113 time=85.1 ms
64 bytes from 210.163.219.84: icmp_seq=3 ttl=113 time=84.9 ms
64 bytes from 210.163.219.84: icmp_seq=4 ttl=113 time=84.9 ms
64 bytes from 210.163.219.84: icmp_seq=5 ttl=113 time=84.7 ms
64 bytes from 210.163.219.84: icmp_seq=6 ttl=113 time=84.9 ms
64 bytes from 210.163.219.84: icmp_seq=7 ttl=113 time=85.0 ms
64 bytes from 210.163.219.84: icmp_seq=8 ttl=113 time=87.0 ms
64 bytes from 210.163.219.84: icmp_seq=9 ttl=113 time=86.9 ms
64 bytes from 210.163.219.84: icmp_seq=10 ttl=113 time=86.5 ms

--- www.ocn.ne.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 84.705/85.716/87.061/0.994 ms
$ ping www.yahoo.co.jp
PING www.ya.gl.yahoo.co.jp (203.216.243.218) 56(84) bytes of data.
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=1 ttl=54 time=77.8 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=2 ttl=54 time=77.9 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=3 ttl=54 time=78.0 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=4 ttl=54 time=78.0 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=5 ttl=54 time=77.9 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=6 ttl=54 time=77.8 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=7 ttl=54 time=77.9 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=8 ttl=54 time=78.0 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=9 ttl=54 time=77.8 ms
64 bytes from f4.top.vip.tnz.yahoo.co.jp (203.216.243.218): icmp_seq=10 ttl=54 time=77.9 ms

--- www.ya.gl.yahoo.co.jp ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 77.856/77.956/78.088/0.383 ms
トラックバック - http://tech.g.hatena.ne.jp/rx7/20100723