Who can believe what we just saw? The Nats had a 5-2 lead going into the 7th inning and the game turned quickly as Gio Gonzalez pitched the bottom of the 7th with a pitch count of 96 and Gio quickly gave up double to put the Nats in a spot and Dusty Baker brought in Treinen who gave up an infield single that was deflected as the run scored to make it a 5-3 lead. Felipe Rivero gave up a run in the 8th to make it a 5-4 game. The Nationals got back a run in the top of the 9th to make it 6-4.
Dusty Baker brought in Jonathan Papelbon who you could quickly see did not look right.
Papelbon averaged only 90.9 mph tonight on his fastball. He had nothing on it. Papelbon’s velocity had dropped 3.1 mph from Friday to tonight.
Here is what Papelbon looked like on Friday night:
We now have to worry if Papelbon is injured. Dusty Baker did not pull Papelbon even though he had Oliver Perez and Shawn Kelley both ready. You could see Papelbon wasn’t right as he walked the leadoff batter. The Indians went to the pinch-hitter Tyler Naquin who is left-handed. Still, Dusty wouldn’t pull Papelbon as he could have countered with Oliver Perez. Papelbon got Naquin in an 0-2 count, but Naquin drove an RBI double into the gap to make the score 6-5 and Naquin represented the tying run on 2nd and still Dusty wouldn’t pull Papelbon. On a sacrifice bunt to Zimmerman, he threw the ball down the rightfield line and Naquin scored the tying run.
By the way, Dusty Baker eventually pulled Papelbon with bases loaded and no outs and the score tied. It didn’t get better after that as the Indians walked it off for a 7-6 win.
“He doesn’t have his command…is evident when he walks the lead-off hitter,” Dusty acknowledged that after the game about Papelbon. If Dusty knew that, why didn’t he pull him immediately? Both Oliver Perez and Shawn Kelley were ready to come into the game.



We recently upgraded our comment system to improve reliability, performance, and long-term control, and we’re currently running both systems during the transition. This shift moves us away from an external service to a system we run and control directly—meaning we own the content and can continue improving it over time. We’ve also reduced the comment refresh delay from about 30 seconds to 10 seconds, making it much closer to real-time.
We understand there have been frustrations and increased feedback, and we’re actively working to improve things. What we ask is simple: use the system and give it a fair shot. If you run into issues, please submit them through the support form so we can track and fix them properly. Repeated complaints without details don’t help us solve problems—we appreciate your patience as we continue refining the experience.
If you’d like a full side-by-side comparison of the platforms and the reasons behind this decision, please refer to the chart below. This change is being made with the long-term benefit of the entire community in mind.