The Kansas City Chiefs walked out of Sunday night with a 20-3 loss to the Seattle Seahawks, and Harrison Butker’s rough evening became one of the clearest reasons why things went sideways.
Kansas City’s offense never found a rhythm in the primetime defeat, but the veteran kicker had a night that stood out for the wrong reasons. Butker finished 1-for-3 on field goals, good for a 33.3% success rate.
He did connect from 50 yards to put the Chiefs on the board, but the two misses carried real weight. The most damaging came early in the fourth quarter, when Kansas City trailed 13-3 and a make from 45 yards would have cut the gap to one score.
Instead, the kick drifted wide right, and Seattle finished the job late.
After the game, Andy Reid didn’t sugarcoat where things stand.
“He's been one of the most consistent kickers in football, but he's off a bit - gotta fix it,” Reid said.
That kind of blunt response fits the moment. Butker, a Georgia Tech product, got a lucrative contract extension in the offseason that made him one of the highest-paid kickers in the NFL.
For years, he’s been the Chiefs’ reliable answer in pressure moments, the kind of specialist teams trust to settle things down when the stakes rise. But an early-season slump is a different story, especially for a team that depends on squeezing out every point it can.
Andy Reid on Harrison Butker's early-season struggles:
— KC Sports Network (@KCSportsNetwork) October 26, 2026
“He's been one of the most consistent kickers in football, but he's off a bit — gotta fix it.” pic.twitter.com/MyPCz6j2JA
Reid’s message was simple enough: the Chiefs need Butker back on track, and soon. In a league where close games come down to a handful of plays, leaving points behind can be the difference between survival and frustration.
In Other News...
Kenneth Walkers Homecoming Exposed A Chiefs Problem Fans Didnt Expect
Sunday night in Seattle brought a rude reminder of how quickly an offense can get squeezed when the ground game never gets going. The Seahawks beat the Chiefs 20-3 to hand Kansas City its first loss of the season, and Kenneth Walkers return to face his former team never found much traction as the Chiefs kept leaning into a game plan that never opened up.
The bigger concern for Kansas City was the overall shape of the offense. Patrick Mahomes was bottled up for much of the night, and the Chiefs spent long stretches chasing a rhythm they could not quite find against a Seattle defense that controlled the line of scrimmage and turned the game into a slog. [Read more 🡒]
Travis Kelce Gave Chiefs Fans One Reason To Smile After That Loss
The loss to Seattle didnt leave Kansas City with much to celebrate, but Travis Kelce still gave Chiefs fans a reminder of how much history he has piled up in red and gold. In Week 7, the veteran tight end added another milestone to a resume that already looked untouchable, moving into a new place on one of the NFLs most exclusive career lists.
Kelces latest climb came in the middle of a frustrating afternoon for the Chiefs, but it underscored just how sustained his production has been across his career. Even with the team taking a hit in the standings, he kept adding to a legacy that has long since moved beyond weekly stats and into the record book. [Read more 🡒]
Seahawks Added Insult To Chiefs First Loss In Brutal Fashion
Kansas Citys first loss of the season came with an ugly scoreline in Seattle, where the Seahawks controlled the game from start to finish in a 20-3 Week 7 win. Travis Kelce still managed a piece of history in the defeat, setting the record for the most combined regular-season and playoff receiving yards by a tight end, but it did little to soften the blow for a Chiefs team that never found its rhythm offensively.
The sting lingered after the final whistle, when Seattle took a victory lap on social media and aimed its celebration at one of the most visible parts of the Chiefs spotlight. For a fan base already frustrated by the way the afternoon unfolded, the post only added another layer to a loss that felt as sharp off the field as it did on it. [Read more 🡒]