Ongoing discussion - posted 19 hours ago and still high up on the front page:<p><a href="https://news.ycombinator.com/item?id=16914698" rel="nofollow">https://news.ycombinator.com/item?id=16914698</a>
<a href="https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad2/" rel="nofollow">https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad...</a><p>Some traceroutes captured during the incident. The results that show "Target unreachable" were the ones seeing the hijacked paths.
It's interesting to note that, although in this case the HTTPS certificate presented by the attackers wasn't valid, they may have been able to acquire an apparently legitimate certificate if the misrouting's effect extended to the infrastructure of a certificate authority.