Being discussed on outages, too. Our monitoring system saw access to www.amazon.com and www.cablelabs.com (over v6) down via HE ... amazon came back up for me via Zayo, but when www.cablelabs.com came back up, it was on HE. So the same as you. So I suspect HE had a hiccup. Frank -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Ken Chase Sent: Friday, April 22, 2016 12:22 PM To: NANOG <nanog@nanog.org> Subject: google and amazon wierdness via HE right now
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