Canelo Alvarez vs Jermall Charlo: Boxinh News: Boxing fans have taken to social media to criticize the potential upcoming fight between Canelo Alvarez and Jermall Charlo. According to ESPNmx, the fight is expected to take place as a defense of Canelo’s undisputed WBA, WBC, IBF & WBO super-middleweight world titles. Let’s dive into the details of this matchup in future.
Boxing Fans Criticize Canelo Alvarez vs Jermall Charlo Reportedly Getting In Works- “Benavidez and Bivol Both Wanted Him At 168”
Boxing Fans Lambasted on Canelo Alvarez for his upcoming matchup against Jermall Charlo
One boxing fan expressed their disappointment with the potential matchup, calling out the fact that Charlo hasn’t fought in two years and suggesting that other fighters, such as David Benavidez and Dmitry Bivol, were more worthy opponents for Alvarez at the 168-pound weight class.
Despite the criticism, both Alvarez and Charlo have impressive records and would undoubtedly put on a show in the ring. Alvarez currently boasts a record of 59 wins, 2 losses, and 2 draws, with 39 of his wins coming by way of knockout. Charlo, on the other hand, is undefeated in 32 fights with 22 of those wins coming by way of knockout.
While opinions may differ on the potential matchup, there’s no denying that both fighters are among the best in the sport. Alvarez has proven time and time again that he has what it takes to dominate in the ring, while Charlo has yet to taste defeat in his professional career.
Of course, it remains to be seen whether the fight will actually take place as nothing has been officially confirmed as of yet. However, if it does happen, it’s sure to be an exciting event for boxing fans around the world.
In the end, whether or not the matchup between Alvarez and Charlo is deemed worthy by fans and critics alike, one thing is for certain the two fighters are sure to put on a display of skill, strength, and endurance that will leave viewers on the edge of their seats.
Follow InsideSport on GOOGLE NEWS / For UFC News updates with InsideSport.IN
