Connectivity issue between Verizon and Amazon EC2

Ray Van Dolson rvandolson at esri.com
Tue Jul 22 05:54:59 UTC 2014


Others appear to have repoted this.  Seems like Verizon is pointing at
AWS:

https://forums.aws.amazon.com/thread.jspa?messageID=558094

Ray

On Mon, Jul 21, 2014 at 08:56:27PM -0700, Tim Heckman wrote:
> Realized I sent the reply to Roland. Apologies.
> 
> Here it is in full:
> 
> ####
> 
> I am seeing the same issue between AWS US-WEST 2 and Hurricane Electric's
> Fremont 2 location (Linode). Looks to be deep within Amanzon's network based on
> changes in latency in a simple trace route.
> 
> I would provide an mtr, however my network configuration is something mtr
> doesn't support.
> 
> Cheers! 
> -Tim
> 
> On Jul 21, 2014 8:34 PM, "Ray Van Dolson" <rvandolson at esri.com> wrote:
> 
>     I'm short some important details on this one, but hopefully can fill in
>     more shortly.
> 
>     We're seeing poor performance (very slow download speeds -- <
>     100KB/sec) to certain EC2 instances via our Verizon hosted circuits.
>     The issue is reproducible on both our production Gigabit circuit as
>     well as a consumer grade Verizion FIOS line.
> 
>     Speeds are normal (10MB/sec plus) via non-Verizon circuits we've
>     tested.
> 
>     Source IP's are in the 198.102.62.0/24 range and destination on the EC2
>     side is 54.197.239.228.  I'm not sure in which availability zone the
>     latter IP sits, but hope to find out shortly.
> 
>     MTR traceroute details are as follows:
> 
>     Host                                               Loss%   Snt Drop   Avg
>      Best  Wrst StDev
>     1. 198.102.62.253                                   0.0%   526    0   0.2  
>     0.2   0.5   0.0
>     2. 152.179.250.141                                  0.0%   526    0  14.1  
>     7.0  19.4   3.6
>     3. 140.222.225.135                                 37.5%   526  197   7.7  
>     6.8  35.8   1.9
>     4. 129.250.8.85                                     0.0%   526    0   8.1  
>     7.4  11.7   0.3
>     5. 129.250.2.229                                   10.3%   525   54  11.4  
>     7.1  85.7   9.6
>     6. 129.250.2.169                                   41.5%   525  218  63.0
>      45.5 130.7  10.3
>     7. 129.250.2.154                                    0.2%   525    1  59.9
>      44.5  69.0   4.0
>     8. ???
>     9. 54.240.229.96                                    7.8%   525   41  76.6
>      71.3 119.9   8.6
>         54.240.229.104
>         54.240.229.106
>     10. 54.240.229.2                                     6.9%   525   36  74.7
>      71.6 109.1   4.9
>         54.240.229.4
>         54.240.229.20
>         54.240.229.8
>         54.240.229.14
>         54.240.228.254
>         54.240.229.16
>         54.240.229.10
>     11. 54.240.229.174                                   5.5%   525   29  76.0
>      71.7 109.0   7.3
>         54.240.229.162
>         54.240.229.160
>         54.240.229.170
>         54.240.229.172
>         54.240.229.168
>         54.240.229.164
>     12. 54.240.228.167                                  94.5%   525  495  76.4
>      71.7 126.0  11.6
>         54.240.228.169
>         54.240.228.165
>         54.240.228.163
>     13. 72.21.220.108                                    5.1%   525   27  75.2
>      71.3 112.6   6.8
>         205.251.244.12
>         72.21.220.8
>         205.251.244.64
>         72.21.220.96
>         205.251.244.8
>         72.21.220.6
>         205.251.244.4
>     14. 72.21.220.45                                     9.0%   525   47  74.0
>      71.6 199.5   8.5
>         72.21.220.149
>         72.21.220.29
>         72.21.220.125
>         72.21.220.37
>         72.21.220.61
>         72.21.220.2
>         72.21.220.69
>     15. 72.21.222.33                                    10.5%   525   55  73.4
>      71.5  87.1   1.5
>         205.251.245.65
>         72.21.222.149
>         72.21.222.35
>         72.21.220.29
>         72.21.222.131
>         72.21.222.147
>         72.21.220.37
>     16. 205.251.245.65                                  93.9%   525  492  73.1
>      72.2  76.2   1.2
>         72.21.222.35
>         72.21.222.131
>     17. ???
>     18. ???
>     19. 216.182.224.79                                  13.5%   524   71  77.9
>      72.4 101.2   5.4
>         216.182.224.81
>         216.182.224.95
>         216.182.224.77
>     20. 216.182.224.81                                  94.1%   524  492  77.9
>      72.8  93.0   6.3
>         216.182.224.95
>         216.182.224.77
>     21. ???
> 
>     The 140.222.225.135 shows up in the traceroutes via our Verizon
>     Business FIOS line as well.
> 
>     Will be opening a ticket with both Verizon and AWS to assist, but
>     hoping someone out there can take a look or chime in.  Feel free to
>     reply off list.
> 
>     Thanks,
>     Ray


More information about the NANOG mailing list