Why did my crash-free rate suddenly drop?

Most likely a bad update introduced a regression, a new crash that hits players, dragging the rate down. A sudden drop usually coincides with a release, pointing at a regression that update caused. Other causes include a platform/OS update breaking your game or a surge of new players on crashing devices. Tracking crash-free rate per version reveals whether a release caused the drop and which build, turning 'stability got worse' into 'this update introduced this crash' so you can fix it fast.

How do I respond to a falling crash-free rate?

Find what's dragging it down: per-version crash tracking reveals whether a release caused the drop (and which version), and grouped, ranked crashes show the specific issue behind it. Then fix the regression, or roll back to the previous known-good version if it's serious and urgent, and watch the rate recover. A drop in crash-free rate is an early warning, so identifying and fixing the cause fast (using per-version data and impact ranking) limits how many players are affected before you act.

What Causes a Drop in Crash-Free Rate?

Quick answer: A drop in crash-free rate means more players are crashing, usually from a new crash introduced by a bad update (a regression), a platform or OS change, or a surge of players on crashing devices. Per-version tracking reveals whether a release caused it.

Your crash-free rate dropping means a larger share of players are now hitting crashes, a clear sign your stability worsened. Identifying why is the first step. Here's what causes a drop in crash-free rate.

Why Stability Drops

A falling crash-free rate means crashes increased relative to sessions, so something made more players crash. The causes:

A bad update introducing a regression, a new crash that hits players, the most common cause of a sudden drop
A new crash at scale, an issue reaching many players and dragging the rate down
A platform or OS update, a system change breaking your game on updated devices
A surge of players on crashing devices, new players (from a launch or sale) on untested hardware that crashes
A backend change, a server-side change causing client crashes
Gradual accumulation, regressions piling up over updates, slowly eroding the rate

A sudden drop usually points at a bad update or a new crash at scale; a gradual decline points at accumulating regressions.

Why Per-Version Tracking Reveals It

The crash-free rate is most useful tracked per version, because a drop tied to a specific release reveals the cause: that update introduced a regression. Comparing the rate across versions shows exactly when it dropped and on which build, pointing at what changed.

Bugnet tracks crash rate by version, so a drop on the latest build stands out and you can see which release caused it. This per-version view is what turns 'stability got worse' into 'this update introduced this crash,' enabling a targeted fix.

Responding to a Drop

Responding means finding what's dragging the rate down: per-version data reveals if a release caused it, and grouped, ranked crashes show the specific issue. Then you fix the regression (or roll back), and watch the rate recover. A drop is an early warning to act before more players are affected.

Bugnet tracks the rate per version and ranks the crashes behind a drop, so you can identify and fix the cause fast. So a drop in crash-free rate is usually caused by a regression from a bad update, a platform change, or a player surge on crashing devices, and per-version tracking reveals which, so you can fix it and recover the rate.

A drop in crash-free rate means more players are crashing, usually a regression from a bad update, a platform change, or a player surge on crashing devices. Per-version tracking reveals which, so you can fix it and recover the rate.