[outages] Azure US-WEST connectivity

[John Kinsella]

Sorry folks - we’re on azure and aws, coffee hasn’t kicked in yet.

> On Nov 16, 2016, at 8:15 AM, John Kinsella <jlk at thrashyour.com> wrote:
> 
> us-west-1 or us-west-2? I’m fine up to Oregon (west2) from San Francisco, going through Equinix per norm:
> 
>  4. x.204.247.173.web-pass.com <http://204.247.173.web-pass.com/>                                 87.5%     9    1.2   1.2   1.2   1.2   0.0
>  5. x.204.247.173.web-pass.com <http://204.247.173.web-pass.com/>                                  0.0%     9    1.5   2.8   1.5   5.9   1.7
>  6. equinix01-sfo5.amazon.com <http://equinix01-sfo5.amazon.com/>                                   0.0%     9    3.4   3.5   3.2   3.7   0.0
>  7. 54.240.242.152                                              0.0%     9   24.6  16.2   7.0  24.6   5.3
>  8. 54.240.242.155                                              0.0%     9    5.4   4.9   3.4  13.4   3.2
>  9. 205.251.229.67                                              0.0%     9   24.8  25.7  24.8  31.5   2.1
> 10. 54.239.43.51                                                0.0%     9   24.6  27.0  24.5  45.3   6.8
> 11. 52.93.14.112                                                0.0%     9   26.6  35.8  26.6  66.5  13.3
> 12. 52.93.14.111                                                0.0%     9   25.2  25.0  24.5  26.8   0.6
> 13. 52.93.15.34                                                 0.0%     9   26.7  37.9  26.7  58.0   9.6
> 14. 52.93.15.55                                                 0.0%     9   32.4  25.7  24.6  32.4   2.5
> 15. 205.251.232.222                                             0.0%     9   24.5  24.5  24.2  25.1   0.0
> 
> 
> The aws status page is all green, not that that means much.
> 
>> On Nov 16, 2016, at 8:03 AM, Sam Munkes via Outages <outages at outages.org <mailto:outages at outages.org>> wrote:
>> 
>> Anyone else having trouble connecting to vms in the us-west? as of a half hour ago all connections are dropping:
>> 
>> Tracing route to ip-67-201-56-x.external-dns.prod-rb.com <http://ip-67-201-56-x.external-dns.prod-rb.com/> [52.179.125.x]
>> over a maximum of 30 hops:
>> 
>>   4    13 ms    16 ms    14 ms  agg22.lamrcadq01r.socal.rr.com <http://agg22.lamrcadq01r.socal.rr.com/> [72.129.9.86]
>>   5    18 ms    14 ms    15 ms  agg28.lsancarc01r.socal.rr.com <http://agg28.lsancarc01r.socal.rr.com/> [72.129.9.0]
>>   6    18 ms    22 ms    14 ms  bu-ether26.lsancarc0yw-bcr00.tbone.rr.com <http://bu-ether26.lsancarc0yw-bcr00.tbone.rr.com/> [66.109.3.230]
>>   7    27 ms    15 ms    14 ms  ae2.lsancarc0yw-bpr01.tbone.rr.com <http://ae2.lsancarc0yw-bpr01.tbone.rr.com/> [66.109.1.41]
>>   8    14 ms    14 ms    15 ms  66.109.7.134
>>   9    72 ms    75 ms    79 ms  be-72-0.ibr02.lax03.ntwk.msn.net <http://be-72-0.ibr02.lax03.ntwk.msn.net/> [104.44.8.110]
>>  10    76 ms    75 ms    82 ms  be-3-0.ibr01.sn4.ntwk.msn.net <http://be-3-0.ibr01.sn4.ntwk.msn.net/> [104.44.4.5]
>>  11    73 ms    75 ms    73 ms  be-1-0.ibr02.sn4.ntwk.msn.net <http://be-1-0.ibr02.sn4.ntwk.msn.net/> [104.44.4.204]
>>  12    73 ms    74 ms    78 ms  be-6-0.ibr01.atb.ntwk.msn.net <http://be-6-0.ibr01.atb.ntwk.msn.net/> [104.44.4.46]
>>  13    74 ms    77 ms    75 ms  be-3-0.ibr03.atb.ntwk.msn.net <http://be-3-0.ibr03.atb.ntwk.msn.net/> [104.44.4.43]
>>  14    72 ms    72 ms    73 ms  be-4-0.ibr01.was05.ntwk.msn.net <http://be-4-0.ibr01.was05.ntwk.msn.net/> [104.44.4.22]
>>  15    72 ms    72 ms    72 ms  ae61-0.bl2-96c-1a.ntwk.msn.net <http://ae61-0.bl2-96c-1a.ntwk.msn.net/> [104.44.8.169]
>>  16     *        *        *     Request timed out.
>>  17     *        *        *     Request timed out.
>>  18     *        *
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org <mailto:Outages at outages.org>
>> https://puck.nether.net/mailman/listinfo/outages
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20161116/997d22dc/attachment.htm>