Philip Rivers blasts refs with savage comment about Marcus Peters interception

The controversial call that went in the Ravens’ favor did not sit well with Colts QB Philip Rivers.
The Indianapolis Colts looked like they were heading into a favorable matchup against the Baltimore Ravens, who had just lost left tackle Ronnie Stanley to a season-ending injury and cornerback Marlon Humphrey to the COVID-19 list. But then the dust settled and the Colts lost 24-10 despite leading 10-7 at the half.
A big reason for that, however, was a nonsensical ruling made by the referees that gave Marcus Peters an interception early in the third quarter, which changed the entire complexion of the game.
You all saw it. Peters caught the ball for a brief moment and had it knocked out of his hands by Marcus Johnson. However, the refs ruled Peters had control of it as he took three steps before falling to the ground. Philip Rivers didn’t agree with the decision and went off in the postgame.
"Somebody that's sitting back watching who probably hasn't thrown a football in his life gets to call it."
— 𝐓𝐡𝐞 𝐒𝐩𝐨𝐫𝐭𝐢𝐧𝐠 𝐍𝐞𝐰𝐬 (@sportingnews) November 8, 2020
Philip Rivers was upset over the Ravens' controversial interception. pic.twitter.com/DriMo7Td1a
That’s we love Phil! No, not because he throws interceptions … because he doesn’t mince words. As always, the veteran quarterback was brutally honest, and it’s safe to say just about everybody agrees with him. We’re not sure on what planet the referees call that a catch if the receiver handles the ball in that manner. Look no further than Dez Bryant …
It’s irresponsible to pin this game on the refs with the way the Colts played for the most part, but we can say that call certainly turned the tides. Baltimore then went on a 10-play, 54-yard drive to score the go-ahead touchdown and never looked back.
A breakdown of the interception in #BALvsIND: pic.twitter.com/eteo6CPctq
— NFL Officiating (@NFLOfficiating) November 8, 2020
With all of the inconsistencies in officiating we’ve seen over the years, Colts fans can’t help but throw their hands in the air, especially after the NFL Officiating Twitter account confirmed the ruling with a bogus explanation. How is this any different from a receiver coming down with the ball and “making a football move”?
There are just too many ways to define what a catch is or isn’t, and this is yet another example that will join the NFL’s wall of shame.