What is Bug Escape Rate?

Bug escape rate is the share of defects that reach production undetected and measures the effectiveness of QA before release. A high rate erodes customer trust and increases costly emergency fixes. Underreporting production bugs makes QA look better than it is and hides the real risk. For context, lower is better; track the trend downward over releases, with elite teams catching the vast majority of defects before production. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Bug Escape Rate alongside Defect Density and Change Failure Rate; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Make sure the numerator and denominator cover compatible populations and periods, and avoid dividing by a partial or unusually small base. Use stable production boundaries and timestamp definitions, and distinguish planned work from incidents, rollbacks and failed deployments. Measure at service or team level and keep the start event, end event and production boundary stable; portfolio averages can hide a fragile component. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Treat the metric as a prompt for system improvement: reduce batch size, automate safe delivery, strengthen observability, rehearse recovery and use blameless reviews to eliminate recurring failure modes. Common pitfalls: underreporting production bugs. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.