Duke’s first loss of the 2026 season came with a lot to unpack.
The Blue Devils fell 28-25 at Georgia Tech on Saturday, a result that knocked them out of the top spot in the ACC and left them dealing with a loss that simply doesn’t look good on the resume. Georgia Tech came in as a below-.500 team, but Duke still had every reason to believe it could survive Atlanta with a win. Instead, the Blue Devils walked away with a narrow defeat after fighting back hard and coming close to erasing the damage.
Even with the loss, there was plenty to like about how Duke competed. The offense kept finding answers, the defense hung around for most of the night, and the Blue Devils were still in position to win deep into the second half.
Nate Sheppard remained the center of everything, even though he clearly wasn’t right for the whole game. The star running back played a good chunk of the night with a taped foot, and while he wasn’t at full strength, he still put together a massive performance. Against a Georgia Tech defense that had entered the game allowing nearly 200 rushing yards per contest and had been the ACC’s worst run defense, Sheppard still found room to work.
He finished with 99 rushing yards and two touchdowns on 27 carries, and he also led Duke in receiving with seven catches for 91 yards. It was technically his worst rushing game of the year because it was the first time he didn’t top 100 yards on the ground, but given the injury situation, it was still a hugely impressive effort. The bigger question now is whether the injury is anything serious.
Walker Eget also gave Duke real hope late. He wasn’t flawless - several deep shots slipped away that could have swung the game even more sharply - but he made enough plays with both his arm and his legs to keep the Blue Devils alive. Eget went 26-of-41 for 259 yards and a touchdown, and his 41 pass attempts were a season high by a wide margin; he hadn’t thrown more than 26 times in any other game this year.
With Sheppard limited, Duke had to adjust what it wanted to do, and Eget handled the burden well enough to give Manny Diaz’s team a chance. The offense moved the chains, stayed functional, and did its part to keep the Blue Devils in striking distance.
The bigger issue was the kind that keeps showing up in the background until it finally costs you. Penalties have been a recurring problem all season, and this time they directly fed the loss. Duke finished with six penalties for 71 yards, but the damage came at the worst possible moments.
Late in the first half, Georgia Tech began a drive near its own goal line and looked ready to hand Duke a stop. Instead, a roughing-the-passer call on Tyshon Reed - a flag the source described as not a great call - kept the possession going.
Another penalty followed, and the Yellow Jackets cashed in with the half winding down. On that sequence alone, Duke gave away 30 free yards.
The second half brought the most painful one. Bradley Gompers was flagged for unnecessary roughness on a 2nd-and-20 with less than two minutes left, and Georgia Tech turned that opening into the go-ahead touchdown. The Blue Devils only had one penalty after halftime, but it was the one that mattered most.
Still, Duke gave itself a real shot. The Blue Devils were down 11 in the third quarter and kept clawing back until the end.
They handled adversity, even with Cosme Salas out and freshman kicker Gavin Strange thrown into a high-pressure spot. The loss wasn’t on Strange, and Duke’s response showed a team that didn’t fold.
Now the Blue Devils are 4-1 overall and 1-1 in ACC play. One loss on the road to a lower-tier league opponent isn’t ideal, but there’s still room to recover if Duke can stack wins over the stretch ahead.
The next one comes Oct. 17 against North Carolina, which just picked up its first ranked win under Bill Belichick by beating No. 25 Pittsburgh 21-17 on the road.
Pitt, though, was without starting quarterback Mason Heintschel after he tore his ACL against Virginia Tech the week before.
Duke still has a path forward. But after this result, the margin for error just got a lot thinner.
In Other News...
Dukes Frustrating Collapse Exposed Two Problems Fans Cant Ignore
Dukes first loss of the season came in Atlanta, where a 28-25 defeat to Georgia Tech left the Blue Devils with plenty to sort through beyond the final score. Walker Eget and linebacker Luke Mergott were among the players who made their presence felt, and Duke actually handled itself well on third and fourth downs, showing enough composure in key spots to stay in the game deep into the afternoon.
Still, the details that tilted the result were hard to ignore. Penalties in the first half repeatedly put Duke behind schedule, and the inside running game never matched the kind of push the Blue Devils needed to control the flow of the game. For a team that had started clean and confident, the loss exposed two issues that will linger until Duke proves it can play cleaner and generate more consistent production between the tackles. [Read more 🡒]
Duke Faces Its First Real Test With Unbeaten Start On The Line
Dukes unbeaten start has given Manny Diaz and his team some early momentum, but the next step looks far more revealing than the first four games. At 4-0, the Blue Devils head into Week 6 with a trip to Georgia Tech looming, and the matchup carries extra weight after the Yellow Jackets came into Durham last season and left with a win.
This time, Duke arrives with a defense that has been tougher and a rushing attack that has helped stabilize the offense. Georgia Tech comes in at 1-3 and is looking for a lift of its own, which makes this a useful checkpoint for Duke before the schedule gets any less demanding. [Read more 🡒]
Duke Let A Winnable Road Game Slip Away In Painful Fashion
For much of the afternoon in Atlanta, Duke had the kind of road game it needed to finish and move on, with Nate Sheppard doing plenty to keep the Blue Devils in front of the conversation. Playing through a foot injury, the running back carried a heavy load and turned in a standout all-around effort, finishing with 99 rushing yards, two touchdowns and 91 receiving yards as Duke tried to stay clean in the ACC race.
Instead, the Blue Devils let a winnable game unravel in painful fashion. Penalties kept handing Georgia Tech extra chances, and when Duke still had a path to force overtime, freshman kicker Gavin Strange missed the late field goal try that would have tied it. The 28-25 loss drops Duke to 4-1 overall and 1-1 in league play, a frustrating result in a game that was there to be taken. [Read more 🡒]
