Amazon unavailable for anyone else?

[FG Lurker]

I'm having trouble accessing Amazon.com and Amazon.co.jp from my computer today, and some other domains as well. I'm on Asahi-net. Docomo-based phone seems fine though.

Anyone else having weird problems? Anyone know what's up?

[Coligny]

I'm having trouble accessing Amazon.com and Amazon.co.jp from my computer today, and some other domains as well. I'm on Asahi-net. Docomo-based phone seems fine though.

Anyone else having weird problems? Anyone know what's up?

Asahi.net BigT here, no probs on both amazon.
But since few weeks there's hiccups at some random times of the day... no pattern...

[FG Lurker]

Asahi.net BigT here, no probs on both amazon.
But since few weeks there's hiccups at some random times of the day... no pattern...

It's weird, very flakey. Sometimes up, sometimes down, sometimes very slow.

Could you post a tracert to Amazon.co.jp? My DNS resolves Amazon to 54.240.252.0 which seems...odd...but not necessarily invalid depending on how the addresses are being doled out.

[Taro Toporific]

I'm having trouble accessing Amazon.com and Amazon.co.jp from my computer today, and some other domains as well. I'm on Asahi-net. Docomo-based phone seems fine though.

Using Softbank.jp, as well as Softbank + a VPN based out California.
No problems.

[FG Lurker]

It seems to be back now. Don't know what it was, as long as it stays stable now I won't worry about it. Thanks for checking Taro and Coligny!

[yanpa]

It was probably just the NSA rebooting their routers after an upgrade.

[Samurai_Jerk]

I've been having issues with certain sites the last few days on both my home and work computers. Sunspots?

[Coligny]

Tracert when I'm home
dakedo... I remember for the last few days having timeouts at checkout with amazon and dealextreme.

Btw parcel delivery from china still super slow...

Sumthing wrong...

[yanpa]

I've been having issues with certain sites the last few days on both my home and work computers. Sunspots?

One possiblility is that the affected site are on the wrong end of a route shared by some ISPs which is having some sort of issues. And/or the affected sites are using some clown cloud computing platform which is having problems.

BTW if anyone ever tells you "the internet routes around damage", slap them around the head with a dead fish.

[Coligny]

this afternoon:

Code: Select all

traceroute to www.amazon.co.jp (54.240.250.0), 64 hops max, 52 byte packets
 1  tacoma (192.168.117.254)  0.406 ms  0.199 ms  0.160 ms
 2  ngyniky.asahi-net.or.jp (202.224.38.16)  4.924 ms  5.765 ms  4.473 ms
 3  tkybi3-v7.asahi-net.or.jp (202.224.38.1)  9.209 ms  9.464 ms  10.300 ms
 4  tkyni91.asahi-net.or.jp (202.224.32.91)  10.153 ms  9.979 ms  9.831 ms
 5  xe-0-2-0-30.r00.tokyjp05.jp.bb.gin.ntt.net (61.120.146.29)  10.514 ms  10.081 ms  10.153 ms
 6  ae-17.r25.tokyjp05.jp.bb.gin.ntt.net (129.250.2.22)  10.162 ms
    ae-17.r24.tokyjp05.jp.bb.gin.ntt.net (129.250.2.20)  10.313 ms  10.688 ms
 7  ae-1.r20.tokyjp05.jp.bb.gin.ntt.net (129.250.6.210)  10.414 ms
    ae-2.r20.tokyjp05.jp.bb.gin.ntt.net (129.250.6.214)  10.837 ms
    ae-1.r20.tokyjp05.jp.bb.gin.ntt.net (129.250.6.210)  11.199 ms
 8  ae-2.r20.sttlwa01.us.bb.gin.ntt.net (129.250.3.12)  94.197 ms  126.030 ms  101.594 ms
 9  ae-1.r04.sttlwa01.us.bb.gin.ntt.net (129.250.5.43)  115.877 ms  105.784 ms  115.531 ms
10  ae-4.amazon.sttlwa01.us.bb.gin.ntt.net (198.104.202.186)  92.776 ms  93.346 ms
    ae-3.amazon.sttlwa01.us.bb.gin.ntt.net (198.104.202.182)  114.781 ms
11  205.251.225.164 (205.251.225.164)  146.468 ms
    205.251.225.162 (205.251.225.162)  123.126 ms
    205.251.225.166 (205.251.225.166)  128.004 ms
12  205.251.232.90 (205.251.232.90)  114.421 ms  113.829 ms
    205.251.232.92 (205.251.232.92)  161.500 ms
13  205.251.232.149 (205.251.232.149)  115.237 ms
    205.251.232.161 (205.251.232.161)  116.917 ms
    205.251.232.143 (205.251.232.143)  123.639 ms
14  205.251.232.167 (205.251.232.167)  122.969 ms  132.658 ms  132.159 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * *^C

Just nao:

Code: Select all

traceroute to www.amazon.co.jp (54.240.248.0), 64 hops max, 52 byte packets
 1  tacoma (192.168.117.254)  0.423 ms  0.244 ms  0.235 ms
 2  ngyniky.asahi-net.or.jp (202.224.38.16)  4.817 ms  3.842 ms  4.082 ms
 3  tkybi3-v7.asahi-net.or.jp (202.224.38.1)  9.409 ms  9.430 ms  9.340 ms
 4  tkyni91.asahi-net.or.jp (202.224.32.91)  9.863 ms  10.285 ms  10.241 ms
 5  xe-0-2-0-30.r00.tokyjp05.jp.bb.gin.ntt.net (61.120.146.29)  10.783 ms  10.831 ms  10.867 ms
 6  ae-17.r24.tokyjp05.jp.bb.gin.ntt.net (129.250.2.20)  11.119 ms  16.463 ms  11.383 ms
 7  ae-1.r20.tokyjp05.jp.bb.gin.ntt.net (129.250.6.210)  19.562 ms  10.238 ms  10.779 ms
 8  ae-2.r20.sttlwa01.us.bb.gin.ntt.net (129.250.3.12)  110.394 ms * *
 9  ae-1.r04.sttlwa01.us.bb.gin.ntt.net (129.250.5.43)  120.031 ms  115.828 ms  103.400 ms
10  ae-5.amazon.sttlwa01.us.bb.gin.ntt.net (198.104.202.190)  115.592 ms  111.271 ms  103.278 ms
11  205.251.225.200 (205.251.225.200)  119.541 ms
    205.251.226.187 (205.251.226.187)  118.146 ms  150.238 ms
12  205.251.232.92 (205.251.232.92)  117.880 ms
    205.251.232.94 (205.251.232.94)  143.932 ms
    205.251.232.90 (205.251.232.90)  128.391 ms
13  205.251.232.141 (205.251.232.141)  124.098 ms
    205.251.232.159 (205.251.232.159)  127.986 ms
    205.251.232.153 (205.251.232.153)  127.071 ms
14  205.251.232.63 (205.251.232.63)  123.602 ms  111.440 ms
    205.251.232.165 (205.251.232.165)  111.620 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * *^C

but it's accessible...

[yanpa]

Wow, NTT is peering directly with Amazon. Well, probably makes sense. Probably one of dem routers was broken, so any ISPs peering with NTT at this end were screwed, whereas any which go via KDDI or someone else were probably fine.

[FG Lurker]

Not surprised to see Amazon peering directly with major carriers, as AWS is one of the largest cloud services, if not the largest. Not sure it was a problem with NTT as my Docomo iPhone worked fine while Asahi-net was borked.

My tracert now goes:

Code: Select all

Tracing route to amazon.co.jp [54.240.250.0] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [my router]
  2     2 ms     2 ms     2 ms  osknij31.asahi-net.or.jp [124.155.64.47]
  3    10 ms    11 ms    10 ms  tkybi5-v9.asahi-net.or.jp [124.155.64.1]
  4    11 ms    11 ms    11 ms  tkyni91.asahi-net.or.jp [202.224.32.91]
  5    12 ms    11 ms    11 ms  xe-0-2-0-30.r00.tokyjp05.jp.bb.gin.ntt.net [61.120.146.29]
  6    12 ms    12 ms    11 ms  ae-17.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.2.20]
  7    12 ms    17 ms    18 ms  ae-2.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.6.214]
  8   103 ms   102 ms   105 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.3.12]
  9   109 ms   109 ms   109 ms  ae-1.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.43]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13  ^C


Everything has been stable for the last 5 or 6 hours so hopefully whatever the problem was has been fixed.