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

Fri Jan 15 22:52:18 UTC 2016

Could be residual from this incident yesterday? AWS claims it's been
resolved, though.

[RESOLVED] Instance Connectivity
3:13 PM PST We are investigating connectivity issues for some instances in
the US-EAST-1 Region.
3:33 PM PST We can confirm connectivity issues when using public IP
addresses for some instances within the EC2-Classic network in the
US-EAST-1 Region. Connectivity between instances when using private IP
addresses is not affected. We continue to work on resolution.
4:00 PM PST We continue to work on resolving the connectivity issues when
using public IP addresses for some instances within the EC2-Classic network
in the US-EAST-1 Region. For instances with an associated Elastic IP
address (EIP), we have confirmed that re-associating the EIP address will
restore connectivity. For instances using EC2 provided public IP addresses,
associating a new EIP address will restore connectivity.
6:19 PM PST  We continue to work on resolving public IP address
connectivity for some EC2-Classic instances in the US-EAST-1 Region. We
have started to see recovery for some of the affected instances and
continue to work towards full recovery.
7:11 PM PST Between 2:26 PM and 7:10 PM PST we experienced connectivity
issues when using public IP addresses for some instances within the EC2
Classic network in the US-EAST-1 Region. Connectivity between instances
using the private IP address was not affected. The issue has been resolved
and the service is operating normally.

On Fri, Jan 15, 2016 at 2:02 PM, Grant Ridder <shortdudey123 at gmail.com>
wrote:

> 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
>