Lost connectivity with an instance in us-east-1 briefly around that time. Got it back within a minute or so. Didn't think much of it but it could be related.
On Tue, Aug 7, 2018, 12:54 Devin Kuhn via Outages <[email protected]> wrote: > At 12:38 EDT we experienced severe routing issues within AWS East. Can > anyone else confirm? > > *DEVIN* KUHN | Engineer II, Architecture, IT Infrastructure, 2U Inc. > <http://www.google.com/url?q=http%3A%2F%2F2u.com%2F&sa=D&sntz=1&usg=AFQjCNE6oJrwtboLV8p57_HHflhQIRaxgA> > 7900 Harkins Road, Lanham, MD 20706 > Cell: (703) 282-9229 | Office: (301) 298-8725 > @2UInc <https://twitter.com/2uinc> | #NOBACKROW > <https://www.youtube.com/watch?v=aI4ZVlyrRZc> > > > *This message contains confidential information and is intended only for > the individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. Please notify the sender > immediately by e-mail if you have received this e-mail by mistake and > delete this e-mail from your system.* > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
