What do I do when my crash rate spikes?

Check per-version data to find the build that caused it, identify the specific crash driving it, and roll back or hotfix while watching the crash rate recover. A crash rate spike almost always traces to a recent release introducing a new crash. Check per-version data (if the spike started on a specific build, that release introduced the driving crash), identify the specific crash (rank by impact and find the new or surging signature on the spiking build, with its captured context), and roll back or hotfix (roll back the release if the spike is severe and slow to fix, hotfix the specific crash if you can fix it fast), then watch the crash rate recover per version. Bugnet tracks crash rate per version and groups crashes by signature, so you can see which build the spike started on (the cause) and which crash is driving it (the thing to fix), turning a spike into a specific diagnosis, then roll back or hotfix and watch the crash rate recover.

Why did my crash rate suddenly spike?

Almost always because a recent release introduced a new crash, the spike's timing usually points right at the build that caused it. A crash rate spike is a change from the baseline, and the most common cause is a new crash introduced by an update (new code that crashes under conditions you did not test). Other causes: an OS update that broke something, or a surge of players on a condition that triggers an existing crash. But a release-introduced crash is the most common by far. Check your crash rate per version: if the spike started on a specific build, that release introduced the crash, and signature grouping identifies the specific crash driving it. Bugnet tracks crash rate per version and groups crashes by signature, so when your crash rate spikes you can see which build it started on (the cause) and which crash is driving it (the thing to fix), turning a sudden spike into a specific, actionable diagnosis, then roll back or hotfix and watch the crash rate recover.

Should I roll back when my crash rate spikes?

Roll back if the spike is severe and the crash will take time to fix; hotfix if you can fix the driving crash fast. The choice depends on the spike's severity and your fix speed. Roll back when the spike is large (a serious crash hitting many players) and you cannot fix it quickly, reverting the release that introduced it returns the crash rate toward the previous build's level, stopping the spike while you fix the cause without pressure. Hotfix when you can identify and fix the driving crash fast (the captured stack trace points clearly at the cause), ending the spike without rolling back the rest of the release. Either way, watch the crash rate recover per version. Bugnet's per-version tracking shows the spike and which build caused it, its impact ranking shows the spike's severity (informing the call), and its captured context helps you gauge and execute a fast fix, then its per-version data confirms the crash rate recovered, so you can make and verify the roll-back-versus-hotfix decision with data.

Ways to Handle a Crash Spike

Quick answer: Check per-version data to find the build that caused it, identify the specific crash driving it, and roll back or hotfix while watching the crash rate recover, a spike almost always traces to a new crash on a recent build.

A crash rate spike means something changed, usually a new crash from a recent build. Here are the best ways to handle a crash spike.

Check Per-Version Data for What Changed

Handle a crash spike by checking per-version data, if the spike started on a specific build, that release introduced the crash driving it. Per-version comparison isolates the spike to a version, the cause.

Bugnet tracks crash rate per version, so when your crash rate spikes you can see which build it started on, isolating the cause to a release.

Identify the Specific Crash Driving It

Handle a crash spike by identifying the specific crash driving it, rank crashes by impact and find the new or surging signature that appeared on the spiking build. That gives you the exact thing to fix.

Bugnet ranks crashes by affected players and tracks per version, so the crash driving the spike (the new or surging signature) is identifiable, with its captured context to fix it.

Roll Back or Hotfix and Watch It Recover

Handle a crash spike by rolling back or hotfixing, roll back the release if the spike is severe and a fix will take time, or hotfix the specific crash if you can fix it fast, then watch the crash rate recover per version.

Bugnet tracks crash rate per version, so after you roll back or hotfix you can watch the crash rate recover on the new build, confirming the spike is resolved.

Handle a crash spike by checking per-version data to find the build that caused it, identifying the specific crash driving it, and rolling back or hotfixing while watching the crash rate recover. A spike almost always traces to a recent build.