MLB.TV Said “Blackout” After I Paid to Remove the Blackout

The Nationals broadcast was already in the second inning when the MLB app replaced the player with “This game is blacked out in your area.” I was in an apartment in Arlington, Virginia, less than ten miles from the ballpark, and I had purchased Nationals.TV specifically because it included local games without the old regional blackout. I blamed the television app, signed out and entered the activation code again. The same message returned before the next batter reached the plate.

My father was watching from his home across town.

We had agreed to keep a video call open during the game, something we had done for years before his health made attending in person difficult.

His message arrived while I stared at the error:

“Are you behind?”

I was not behind.

I was not watching at all.

The blackout should not have applied

For years, MLB.TV was primarily an out-of-market service. Fans could watch teams from elsewhere, while local games were often reserved for regional broadcasters.

That changed significantly in 2026.

MLB began offering in-market streaming subscriptions for 20 clubs, including the Nationals. Those packages were designed to let local subscribers watch their team without the traditional regional blackout. (Mlb)

My package was not standard out-of-market MLB.TV.

It was Nationals.TV.

The game was a local broadcast, not a national exclusive, and the subscription included it. (Mlb)

I was inside the correct territory.

I had paid for the correct package.

The error therefore did not mean the game was unavailable to me. It meant the service did not trust the location or route attached to my connection.

That distinction mattered because the word blackout encouraged the wrong response:

Move the connection somewhere else.

A distant server made a valid subscription look suspicious

I had enabled a well-known commercial VPN because the apartment’s internet was included with the building and ran through equipment I did not control.

The provider had a polished application, years of public history and servers across dozens of American cities.

It had connected automatically to New York.

That suddenly looked like the problem.

MLB bases blackout decisions on physical location and may use the connection’s IP address as one of its location signals. (Mlb)

My subscription said I belonged in the Nationals’ home territory.

My device was physically in Northern Virginia.

The VPN exit said New York.

I had taken legitimate local access and given it an out-of-market network identity.

So I switched to Washington, D.C.

The blackout message remained.

I tried another nearby server.

The game page loaded, showed a spinning baseball and returned to the same error.

The city label was now correct, but the route was still being rejected.

My father sent another message:

“Still fixing it?”

I replied with the least convincing phrase in technical support:

“Almost.”

MLB’s official fix removed the protection

I opened MLB’s blackout troubleshooting page.

For an incorrect blackout, MLB advises viewers to check that a VPN is not active and refresh the connection. (Mlb)

I disconnected the established provider.

The game opened immediately.

The pitcher was walking back to the mound. I heard the announcer finish a sentence that had started before the player appeared.

The subscription worked.

The territory was correct.

The VPN had triggered the error.

That proved the cause, but it did not complete my actual task.

I did not merely want the game to play. I wanted it to play through a protected connection on a network managed by my temporary building.

Turning off the VPN restored the stream by removing the protection I had installed it for.

I needed a VPN that could stay on without preventing MLB from recognising the access I had already purchased.

More nearby servers produced the same failure

I reconnected to the established provider and tried its closest options.

Ashburn.

Washington.

Baltimore.

Then New York again, in case the first server had simply been unlucky.

Each attempt required a disconnect, a reconnect and another trip through the MLB app.

Sometimes I received the blackout message.

One server opened the schedule but returned an access error when I pressed Watch.

Another prevented the game page from loading properly.

Fans describe the same practical frustration in simpler terms: once the VPN is enabled, MLB may block more than the individual game and send the user into repeated server changes. (Reddit)

That was exactly what my evening had become.

I had assumed that a server near Washington would be enough.

It was not.

Streaming platforms see the public address where VPN traffic exits. Addresses associated with VPNs, proxies and hosting providers can be classified in commercial databases. (Maxmind) A server can therefore be physically close to the ballpark and still look like a familiar shared VPN exit.

The map in the VPN app was showing geography.

MLB was judging the route.

By the fourth inning, the distinction was impossible to ignore.

I had been trying to solve the wrong blackout

A traditional sports blackout means the viewer is inside a territory where another broadcaster holds the live rights.

That was not my situation.

I had purchased the local streaming product created to carry the Nationals broadcast inside that territory.

The message looked like a rights restriction, but the visible cause was connection classification.

Moving farther away would not make my subscription more valid.

Choosing more city names would not change the package attached to my account.

What I needed was simpler:

a protected route that did not interfere with the local access I had already bought.

Once I framed the problem that way, the large server list stopped looking like an advantage.

It was only giving me more versions of the same failed test.

The smaller app started with the game, not the map

I closed the established provider and opened the smaller backup on my laptop.

The first screen did not ask me to choose a city.

It asked what I was trying to do.

I selected the preset for streaming on a shared network.

The connection opened.

I returned to the same game page and pressed Watch.

The player appeared.

The broadcast began without the blackout message.

No location loop.

No access error.

No fifth server.

The score was still close enough that my father had not spoiled anything important.

I called him.

“You finally in?”

“Yes.”

“Good. Their bullpen’s already making me nervous.”

I connected the laptop to the television and left the game running. The stream stayed in high definition through the rest of the inning.

The smaller app used an obfuscated streaming route rather than presenting the same familiar VPN pattern I had just tested repeatedly.

I could not observe MLB’s internal location and filtering rules or identify exactly why one exit was rejected and another accepted. I could compare the outcome: the local package worked with no VPN, failed across the established provider’s nearby servers and played immediately through the smaller app.

That settled the comparison.

The useful VPN was not the one with the most American cities.

It was the one that let my legitimate local subscription reach the player.

The package still determined what I could watch

The successful connection did not transform every MLB.TV subscription into a local television package.

Standard MLB.TV remains focused on out-of-market games, and national exclusives can still affect local club subscriptions. (Mlb)

The smaller app did not change the rights attached to my account.

It allowed the rights I already had to work without forcing me to abandon protection on the building’s network.

That difference is important because some fans seeing a blackout message genuinely have the wrong package for the game.

Had I owned only standard MLB.TV, the local restriction might have been correct.

Had the game belonged exclusively to a national partner, Nationals.TV might not have included it.

Neither condition applied.

My entitlement was valid.

The established VPN was getting between that entitlement and the stream.

The network changed without ending the inning

In the sixth, the apartment Wi-Fi slowed sharply.

The picture softened, recovered and froze on a full count.

My phone still had a strong 5G signal, so I enabled its hotspot and moved the laptop away from the building network.

The video paused briefly.

Then the same at-bat continued.

The player did not return to the schedule.

The blackout warning did not reappear.

The app did not ask me to choose another route.

The smaller service uses an HTTP/3-based connection that can recover when a device moves between network paths.

The practical result needed less explanation:

The laptop changed networks.

The game stayed open.

Passing the initial location check had solved the urgent problem. Surviving the switch to mobile data solved the smaller one that appeared later.

By then, I was no longer managing the VPN.

I was arguing with my father about whether the manager had waited too long to visit the mound.

The second screen joined before the pitching change

My father normally watched on his television, but he wanted the box score and alternate audio on his tablet.

The smaller app displayed a device-sharing code.

I read it to him over the call.

He entered the code without using my email address or asking me to dictate a VPN password.

The second device connected.

He opened the game page and found the same broadcast.

That was not why the smaller app had earned its place. The first stream had already solved the main problem.

The code simply removed the next piece of friction before the inning ended.

A minute later, he said:

“Okay, now I can see the pitch chart.”

Then the reliever threw four straight balls.

For the next half hour, neither of us mentioned the VPN again.

That was exactly how the software should have behaved.

The largest network had answered the wrong question

The smaller service has fewer locations, fewer independent reviews and a shorter public history than the established provider. That is its clearest limitation.

Before the game, those differences made the larger provider look safer.

It had more American cities.

More nearby exits.

More chances to select a place that appeared correct.

But my subscription was already correct.

My physical location was already correct.

The game was already included.

The server list kept answering a question I did not need to ask.

The smaller app focused on the actual failure: MLB was rejecting the protected route before my valid local access could reach the player.

The established provider gave me Washington, Ashburn, Baltimore and New York.

The smaller app gave me the rest of the game with my father.

For a false MLB.TV blackout, the useful VPN was not the one that moved me farthest from home.

It was the one that stopped getting between my home-team subscription and the game I had already paid to watch.