nanog mailing list archives
Re: S3, US Standard Problems?
From: Bryan Socha <bryan () digitalocean com>
Date: Fri, 13 Jun 2014 13:52:48 -0400
It appears to be fixed. Feel free to test from us if you want to look closer at a test. Thanks, Bryan Socha Network Engineer DigitalOcean On Fri, Jun 13, 2014 at 12:41 PM, Jared Mauch <jared () puck nether net> wrote:
If you are still seeing problems can you please contact me with details? I’ve seen some things done and am looking for confirmation it’s fixed. (or still broken). - Jared On Jun 13, 2014, at 1:48 AM, Bryan Socha <bryan () digitalocean com> wrote:The problem we are seeing we had to route around. There is a probleminNYC between NTT(2914) and Amazon. Bryan Socha Network Engineer DigitalOcean On Thu, Jun 12, 2014 at 9:39 AM, Owen DeLong <owen () delong com> wrote:I still can’t get to them from 2620:0:930::/48. But this is not a new problem. It has persisted as long as I canremember.Owen On Jun 11, 2014, at 9:16 PM, Bryan Socha <bryan () digitalocean com>wrote:Is anyone else noticing a lot of problems with Amazon S3 US Standard problems. We're seeing a lot of customer complaints of connects then hangs/timesout mid transfer... Mostly coming from connections originating in the NYC area or fromeuropepassing through nyc on it's way. Bryan Socha Network Engineer DigitalOcean
Current thread:
- S3, US Standard Problems? Bryan Socha (Jun 11)
- Re: S3, US Standard Problems? Bryan Socha (Jun 11)
- Re: S3, US Standard Problems? Owen DeLong (Jun 12)
- Re: S3, US Standard Problems? Bryan Socha (Jun 12)
- Re: S3, US Standard Problems? Jared Mauch (Jun 13)
- Re: S3, US Standard Problems? Bryan Socha (Jun 13)
- Re: S3, US Standard Problems? Bryan Socha (Jun 12)