Yes, and, to be fair, it's been a known problem for years. There are some potential solutions in the works but you can't just pick an arbitrary day and flip a s

Yes, and, to be fair, it's been a known problem for years. There are some potential solutions in the works but you can't just pick an arbitrary day and flip a switch and turn it on. Most of these incidents are accidental and could easily be prevented. The network operator community can't even get everyone to implement BCP38, though, so something like a full Internet-wide RPKI is a pipe dream. Even basic filtering would prevent much of this but that's apparently asking too much as well. The amount of filtering, if any, varies tremendously from network to network. Some won't accept routes without IRR entries, LOAs, and a bunch of paperwork. Others (such as AS31133, apparently) will accept any prefix you want and as many of 'em as you want. I'll give (some of) the Tier 1's a bit of a break, as filtering on every single BGP session just isn't feasible (although some of them wouldn't bother filtering even if they could!). Pretty much everyone else should be filtering. But they aren't. And they won't be any time soon. And so we'll continue to have incidents like this for the foreseeable future.