[172333] in North American Network Operators' Group
Re: S3, US Standard Problems?
daemon@ATHENA.MIT.EDU (Jared Mauch)
Fri Jun 13 12:43:40 2014
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAOb1_VPRY9z2icGCZ+mAVwx_004hau_WzzO_9nQHstLojPm=Gg@mail.gmail.com>
Date: Fri, 13 Jun 2014 12:41:36 -0400
To: Bryan Socha <bryan@digitalocean.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
If you are still seeing problems can you please contact me with details? =
I=92ve seen some things done and am looking for confirmation it=92s =
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 =
problem in
> NYC between NTT(2914) and Amazon.
>=20
>=20
> Bryan Socha
> Network Engineer
> DigitalOcean
>=20
>=20
>=20
> On Thu, Jun 12, 2014 at 9:39 AM, Owen DeLong <owen@delong.com> wrote:
>=20
>> I still can=92t get to them from 2620:0:930::/48.
>>=20
>> But this is not a new problem. It has persisted as long as I can =
remember.
>>=20
>> Owen
>>=20
>> On Jun 11, 2014, at 9:16 PM, Bryan Socha <bryan@digitalocean.com> =
wrote:
>>=20
>>> 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...
>>>=20
>>> Mostly coming from connections originating in the NYC area or from =
europe
>>> passing through nyc on it's way.
>>>=20
>>> Bryan Socha
>>> Network Engineer
>>> DigitalOcean
>>=20
>>=20
