Fired hours after a 17-1 win. The timing says everything.
The Boston Red Sox beat the Baltimore Orioles 17-1 on Saturday. They scored 10 runs in the ninth inning. Three players went deep. It was the kind of performance that usually earns a manager a pat on the back and a rare quiet night.
A few hours later, Alex Cora was fired.
That is the sentence that is going to define the 2026 Boston Red Sox for a long time. Not the 17-1 win. Not the 10-17 record. The timing. The fact that one of the most lopsided wins of the season was not enough to save an eight-year manager's job says more about the state of this franchise than any box score could.
What Happened
- Manager fired: Alex Cora
- Date: April 25, 2026
- Red Sox record at the time: 10-17
- Final game before the firing: Red Sox 17, Orioles 1
- Interim manager: Chad Tracy
That is a chaotic summary for a team that entered the season thinking it was supposed to contend.
Eight Years, One Ring, and a Brutal Exit
Before we get into whether the decision was right, it is worth being clear about what Cora was in Boston.
He took over in 2018 and won the World Series in his first season. Not just won - dominated. That Red Sox team went 108-54, tore through the Yankees in the ALDS, beat the Astros in the ALCS, and handled the Dodgers in five games in the World Series. It was one of the most complete seasons in recent baseball memory.
He went on to take Boston back to the postseason multiple times over eight seasons and finished with a 620-541 record. By any reasonable standard, he was one of the better managers in the game.
He deserved better than a Saturday night dismissal after a blowout win.
Was It the Right Call?
This is where it gets complicated.
The numbers heading into the firing were genuinely ugly. Boston was slashing .233/.312/.354 as a team, and the starting rotation owned a 5.22 ERA. Garrett Crochet's velocity had become a concern. Sonny Gray and Johan Oviedo, two offseason additions meant to stabilize the staff, had already been hit hard.
That is the front office case for making a change: the team was underperforming badly, the offense had stalled, and the relationship between Cora and chief baseball officer Craig Breslow reportedly had grown strained.
That part is real.
But here is the harder question: was this actually a manager problem, or was it a roster problem wearing a manager's name tag?
Cora did not build this roster. Breslow did. The offseason moves that were supposed to move Boston closer to contention were not Cora's calls. Yet Cora was the one who paid the price for them.
That is why so many people looked at this firing and saw something bigger than a bad April. A 10-17 record gave the front office the cover to act on a relationship that may already have been broken.
The Players Said More Than the Front Office Did
When a manager gets fired and the players sound stunned, it usually means the clubhouse did not quit on him.
Trevor Story said the direction of the franchise felt "up in the air." That is not the reaction of a room that had tuned out its manager. It is the reaction of a room that respected him and did not fully understand why he was the one being shown the door.
That matters.
You can fire a manager for understandable reasons and still make the organization look unstable in the way you do it. That is what happened here.
What Chad Tracy Can and Cannot Fix
Worcester manager Chad Tracy takes over as interim manager, and there is every reason to believe he can provide a short-term jolt.
He is respected in the organization. Players who came through the system know him. A fresh voice can sometimes loosen a team up enough to stop the bleeding.
But Tracy is inheriting the same problems Cora had.
The offense still cannot hit fastballs. The rotation is still underperforming. The roster still lacks the depth and punch a real AL East contender needs. A new manager can change tone. He cannot change roster construction.
That is what makes this move feel incomplete.
The Phillies Called. He Said No.
Here is a detail that tells you everything about how the baseball world views Cora.
Three days after Boston let him go, the Philadelphia Phillies fired Rob Thomson — their own manager — after a 9-19 start. Their first call to fill the vacancy was Alex Cora. The man who had just been fired by one team was immediately the top candidate for another.
Cora turned it down. Don Mattingly got the Phillies job instead.
That sequence says two things clearly. The baseball world still has tremendous respect for what Cora brings to a clubhouse. And the fact that Philadelphia moved that fast — calling a freshly fired manager within days — shows just how badly two supposed contenders have spiraled at the same time.
Two managers fired in one week. Same pattern, different cities. We wrote about the Phillies situation separately — the parallel is worth understanding.
The Bigger Picture in Boston
This is the kind of move front offices make when they need to show urgency but do not want to admit the deeper problem might live upstairs.
Boston has a payroll that should create expectations. The fan base still expects October baseball. And the roster decisions that shaped this start were made long before the manager got the final blame.
Firing Cora looks decisive from the outside. It does not guarantee anything changes underneath.
Cora is out. The lineup is still inconsistent. The rotation is still shaky. The franchise direction still feels uncertain to players inside the clubhouse.
A 17-1 win and a pink slip. That is 2026 in Boston so far.
Follow the Red Sox and make your daily MLB picks at Crystal Ball Picks.
