network issue on ec2 classic us-east-1??

Fri Jan 15 22:02:06 UTC 2016

Gotcha, thanks for the info.
I am at 128 instances and counting in the last 8 hrs

-Grant

On Fri, Jan 15, 2016 at 1:58 PM, Neil Robst <neil.robst at piksel.com> wrote:

> Hi Grant,
>         We saw the first confirmed issue last week. So far only
> experienced 2
> confirmed - that last week and one this morning, but its possible there
> have been others.
>
> Neil
>
> From:  Grant Ridder <shortdudey123 at gmail.com>
> Date:  Friday, January 15, 2016 at 1:54 PM
> To:  Neil Robst <neil.robst at piksel.com>
> Cc:  "dovid at telecurve.com" <dovid at telecurve.com>, NANOG
> <nanog-bounces at nanog.org>, "nanog at nanog.org" <nanog at nanog.org>
> Subject:  Re: network issue on ec2 classic us-east-1??
>
>
> Neil / Dovid,
> How long ago did your issues start?  Symptoms are the same, but the issue
> for me started early this morning at an alarming rate.
>
> -Grant
>
>
> On Fri, Jan 15, 2016 at 1:45 PM, Neil Robst
> <neil.robst at piksel.com> wrote:
>
> Hi David and Grant,
>
>         We have been experiencing exactly the same issue also now whereby
> our
> instances randomly stop getting their DHCP reservation and then drop
> offline. A simple reboot in the AWS console usually sorts it but as yet we
> do not know the root cause.
>
> Regards,
> Neil
>
> On 1/15/16, 1:31 PM, "NANOG on behalf of Dovid Bender"
> <nanog-bounces at nanog.org on behalf of
> dovid at telecurve.com> wrote:
>
> >Grant,
> >
> >We have been having issues for a few weeks now with instances that
> >randomly stop getting their IP from DHCP. Did you see any dhcp errors?
> >
> >
> >Regards,
> >
> >Dovid
> >
> >-----Original Message-----
> >From: Grant Ridder <shortdudey123 at gmail.com>
> >Sender: "NANOG" <nanog-bounces at nanog.org>Date: Fri, 15 Jan 2016 12:58:58
> >To: nanog at nanog.org<nanog at nanog.org>
> >Subject: network issue on ec2 classic us-east-1??
> >
> >Hi,
> >
> >Over the last 6 hrs i have had over 100 instances in us-east-1 in EC2
> >Classic fail their instance health checks and a reboot via the console
> >solves them.  Logs on the host point to a loss of all network
> >connectivity.  Anyone else experiencing something like this?
> >
> >Reached out to AWS support and haven't gotten anywhere with that yet.
> >
> >-Grant
>
>
>
>
>
>
>
>
>