www.netflix.com / EC2 problem -- Persistent problems from Palo Alto to destinations to Netflix and other destinations with content on Amazon EC2 - 2000ms latency

Peter Kranz pkranz at unwiredltd.com
Mon Mar 6 17:33:04 UTC 2017


First version got a little munged:

I'm not making progress with GTT's NOC on this issue, can someone clued in
at Netflix or Amazon comment on this problem. I believe it started after
Amazons outage last week.
 
This is an MTR to www.netflix.com <http://www.netflix.com>  (52.5.161.36)
from 208.71.159.3  . this should be just a couple of ms away from Palo Alto:

                                                               Packets
Pings
 Host                                                        Loss%   Snt
Last   Avg  Best  Wrst StDev
 1. 208.71.159.113                                            0.0%     9
0.4   0.5   0.4   0.7   0.0
 2. 204.11.106.45                                             0.0%     9
2.1   2.1   2.0   2.2   0.0
 3. 173.205.47.153                                            0.0%     9
36.4   5.8   1.9  36.4  11.5
 4. 89.149.184.177                                            0.0%     9
37.8  38.1  37.6  40.5   0.6
 5. 173.205.39.122                                            0.0%     9
37.9  37.8  37.6  38.3   0.0
 6. 176.32.125.164                                            0.0%     9
50.0  48.4  39.0  55.5   5.8
 7. 176.32.125.169                                            0.0%     9
38.0  37.9  37.7  38.5   0.0
 8. 54.239.43.200                                            12.5%     9
1117. 1096. 862.8 1662. 274.5
 9. 54.239.43.174                                            12.5%     8
1146. 1092. 872.1 1627. 261.4
10. ???
11. 54.239.110.227                                           12.5%     8
1266. 1247. 908.7 1566. 236.7
12. 54.239.111.67                                            12.5%     8
1230. 1075. 883.4 1511. 227.7
13. 205.251.244.193                                          12.5%     8
1247. 1068. 890.1 1477. 219.1
14. ???

Via GTT's own looking glass tool: (Note the latency and packet loss starting
at hop 5)
 
IPv4 traceroute to 52.5.161.36

HOST: pao11-re0                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. et-2-1-0.cr4-dal3.ip4.gtt.ne  0.0%     5   42.3  39.4  36.1  42.3   2.2
  2. ip4.gtt.net                   0.0%     5   36.1  38.6  36.1  41.5   2.4
  3. 176.32.125.140                0.0%     5   48.5  55.2  48.5  61.9   5.0
  4. 176.32.125.145                0.0%     5   39.5  41.2  36.2  45.0   3.4
  5. 54.239.43.200                20.0%     5  1417. 1784. 1417. 2112. 306.6
  6. 54.239.43.98                 20.0%     5  1413. 1770. 1413. 2116. 312.0
  7. ???                          100.0     5    0.0   0.0   0.0   0.0   0.0
  8. 54.239.110.157               20.0%     5  1420. 1749. 1420. 2104. 306.9
  9. 54.239.109.9                 20.0%     5  1394. 1720. 1394. 2081. 308.7
10. 205.251.245.65               20.0%     5  1395. 1706. 1395. 2072. 305.4
11. ???                          100.0     5    0.0   0.0   0.0   0.0   0.0

 Peter Kranz
www.UnwiredLtd.com <http://www.unwiredltd.com/> 
Desk: 510-868-1614 x100
Mobile: 510-207-0000
pkranz at unwiredltd.com <mailto:pkranz at unwiredltd.com> 

 





More information about the NANOG mailing list