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.

Colts get screwed on bizarre Marcus Peters interception call
The Indianapolis Colts got screwed in the second half of their game against the Baltimore Ravens on this ridiculous Marcus Peters INT.