Colts: Twitter destroyed Rock Ya-Sin for brutal first half
Colts CB Rock Ya-Sin is trending for all the wrong reasons for the second consecutive week.
For the second straight week, Indianapolis Colts CB Rock Ya-Sin has become nationally-known burnt toast. Not ideal.
Last week against the Packers, you might recall Ya-Sin leaping an Aaron Rodgers route spectacularly for a highlight-reel pick-six, only to nearly swing the game just before half with a mind-numbing 51-yard pass interference that allowed the Pack to extend their lead to 14.
Never mind the fact that the Colts defense stormed back with a vengeance in the second half; Ya-Sin’s name was the one on everyone’s lips.
This week? Regrettably, we’re dealing with more of the same. After a first half defined by Derrick Henry’s bruising running through the hole created by Denico Autry and DeForest Buckner’s absences, Ya-Sin also allowed the Titans to prosper…repeatedly. His worst moment? A hands to the face penalty near the goal line, which gave the Titans second life. They then parlayed it into third, fourth, and fifth lives, swiftly sprinting away from Indy.
Yes, just like always (it seems), Ya-Sin was cooking up something extra special for Colts fans in the second quarter on Sunday.
Never mind the fact that Indy simply didn’t have enough personnel to weather any massive mistakes on Sunday. Ya-Sin made sure to render any defensive personnel problems irrelevant by doing the damage all by himself.
When even the out-of-towners are noticing one specific defensive back’s deficiencies, it’s not a good day. That’s a guarantee.
Chris Long, former NFL defensive end and absolutely not a weekly Colts watcher, picked up on the disaster right away.
Henry owned the first half, and by the time the whistle blew, the Colts were as good as dead on their home turf.
Needless to say, the fans on Twitter did not take it well.
Better luck next time for Ya-Sin, who’s unfortunately on a two-week disaster streak.
You never want to be the main character on Twitter. That’s doubly true if you’re an anonymous DB.