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
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
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
We saw disconnections to Comcast via HE, A subnet was announced with a bogus path. -- During the problem -- 98.224.0.0/11 via 162.11.22.209 on vlan500 [ibgp_border 12:09:48 from 162.11.22.212] * (100/15) [AS65021i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 6939 200759 65021 BGP.next_hop: 184.5.5.69 BGP.local_pref: 100 -- Returned to normal -- 98.192.0.0/10 via 162.11.22.209 on vlan500 [ibgp_border 2016-03-17 from 162.11.22.212] (100/15) [AS7922i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 6939 7922 BGP.next_hop: 184.5.5.69 BGP.local_pref: 100 On Fri, Apr 22, 2016 at 12:22 PM, Ken Chase <math@sizone.org> 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
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
On 04/22/2016 12:31 PM, Frank Bulk wrote:
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
Hijack: https://twitter.com/bgpmon?ref_src=twsrc%5Etfw -James
-----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
It appears HE and others accepted 'hijacked' routes from AS200759. A quick initial investigation shows close to 2,000 prefixes were affected including prefixes normally announced by networks such as Facebook, Google, Amazon, Twitter, Apple, Akamai, Time Warner Cable and more. Also see more details on the bgpmon blog here: http://www.bgpmon.net/large-hijack-affects-reachability-of-high-traffic-dest... Cheers Andree My secret spy satellite informs me that Frank Bulk wrote On 2016-04-22, 10:31 AM:
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
participants (6)
-
Andree Toonk -
Frank Bulk -
James Stahr -
Ken Chase -
Ray Van Dolson -
Thomas Johnson