Beginning at 09:43 UTC today (6 June 2019), Swiss data center colocation company Safe Host (AS21217) leaked over 70,000 routes to China Telecom (AS4134) in Frankfurt, Germany.
Yet another incident of Border Gateway Protocol (BGP) hijack, with the latest victim this time in Taiwan.
Google recently faced a major outage in many parts of the world thanks to a BGP leak.
It’s been a busy couple of weeks for routing security. First, on 23 April, we introduced a new category of MANRS participants aimed specifically at Internet Exchange Points.
Yesterday, we reported some initial news and details about the Amazon Route 53 BGP hijack that resulted in a loss to some cryptocurrency users.
Another BGP hijacking event is in the news today. This time, the event is affecting the Ethereum cryptocurrency. (Read more about it here, or here.) Users were faced with an insecure SSL certificate.
How was the state of the Internet’s routing system in 2017? Let’s take a look back using data from BGPStre
Yesterday, there were two BGP routing incidents in which several high-profile sites (Google, Apple, Facebook, Microsoft, Twitch, NTT Communications and Riot Games) were rerouted to a previously unused Russian AS.
Today over on the Internet Society Internet Technology Matters blog, I wrote a piece about RFC 7908 being published. Most of us have heard the term “route leak,” but it was a vague term without an official, technical definition.