On Fri, Apr 22, 2016 at 01:22:27PM -0400, Ken Chase wrote: > and of course the second I post it all fixes itself. NANOG works! Thanks! > > (was going on for about 10-15 min) > > On Fri, Apr 22, 2016 at 01:21:47PM -0400, Ken Chase said: > > > >From toronto - something odd - mtr to google.com (google.com > (172.217.3.142)) > > > > 5. v638.core1.tor1.he.net > > 6. 100ge7-2.core1.nyc4.he.net > > 7. 100ge11-1.core1.par2.he.net > > 8. 10ge3-2.core1.zrh1.he.net > > 9. ??? > > > >par is paris, zrh is zurich? > > > >same base path for hitting my EC2 nodes... Cant imagine this is just > affecting Toronto > >HE customers. > > > >EC2 node is in 107.20/14 > > > >/kc > > /kc
There's some chatter about Amazon issues on the Outages mailing list as well. Definitely seems like something blipped. Ray
