Sanhok Map Probability Reduced After Update 33.1 Performance Issues

Hey folks. I have been deep into PUBG: BATTLEGROUNDS for a long time, and Sanhok has always been one of those maps that can either make your night or completely wreck it. After Update 33.1 landed, a lot of us noticed that the map was not running the way it should. Frames were dropping, fights felt jittery, and queueing into Sanhok became more frustrating than fun. That is why the official notice from the PUBG team caught my attention. They did not pretend everything was fine. They acknowledged the performance issues, made the problem a top priority, and decided to actually adjust matchmaking while they worked on a fix.

Let me be honest. I love the idea of destructible terrain and buildings. But when a map runs poorly, even the coolest features lose their appeal. The team reduced Sanhok’s probability in the Random Map regions from an initial 40%. That change started in Week 3. As someone who plays random queues often, this mattered a lot. I was tired of seeing Sanhok pop up when I knew the performance was unstable. Fewer Sanhok matches meant a better overall experience for the lobby.

What Changed

Here is the official adjustment schedule. Keep in mind these times are in UTC.

The console date was listed as to be updated in the original statement, which makes sense because console updates sometimes follow a slightly different pipeline. Still, the intent was clear. They wanted to lower the odds quickly.

Why did they make this change? According to the team, the reason was simple. They wanted to ensure a more enjoyable experience for all players. That sounds like standard wording, but in this case it matched what many of us were feeling. Nobody wants to fight both the enemy squad and a stuttering map. The reduction also helped people who were still experiencing crashes or freezes on Sanhok. Yes, lowering a map's appearance rate does not fix the core problem, but it protects the player experience while engineers dig into the technical side.

I also appreciated the apology. The team specifically said they were sorry for the disappointment caused by the performance issues, especially for players who were looking forward to the Sanhok destruction features. That part hit home for me. A lot of players waited for destructible elements, and then the map became hard to enjoy because of technical problems. It is frustrating when a long-awaited feature arrives in a rough state. At least the developers recognized it.

There are a few takeaways from the announcement.

• 🔹 The PUBG team treated Sanhok performance as a top priority.

• 🔹 Sanhok’s probability in Random Map regions was reduced from 40%.

• 🔹 The change went live for PC first, with console following later.

• 🔹 The team promised to keep working on the underlying issues.

• 🔹 The apology specifically mentioned the destruction features.

For me, this was the right move. Some players argued that the map should have been pulled entirely, but I think lowering its frequency was a fair middle ground. It kept Sanhok available for those who still wanted to play it, while saving random queue players from constant bad matches. A full removal would have upset people who enjoyed the new destructible areas despite the issues.

By 2026, PUBG has gone through many updates, but this kind of communication still stands out. It shows that map probability is not set in stone. Developers can and should adjust it when something is clearly wrong. I hope future updates continue to include this level of honesty. If a map starts causing widespread performance problems, the worst thing a team can do is stay silent. The PUBG team did not stay silent here. They gave us dates, reasons, and a plan.

So if you were one of those players stuck in back-to-back Sanhok matches after Update 33.1, you were not alone. The change may have come a little late for some, but it was still better than nothing. I am glad the team listened. Now, let's just hope the next big map feature arrives a bit smoother.

Data referenced from Esports Charts helps frame why PUBG’s decision to reduce Sanhok’s Random Map probability after Update 33.1 matters beyond everyday matchmaking: when performance hiccups cause stutters, crashes, or inconsistent fights, they don’t just frustrate casual squads—they can also undermine the reliability players expect in competitive environments where stable FPS and smooth engagements are essential for fair outcomes. In that sense, temporarily lowering Sanhok’s frequency is a practical mitigation step while the underlying optimization work catches up, keeping the broader play experience steadier without fully removing the map.