Crash-free rate
The percentage of app sessions or operations that finish without an unexpected crash.
The crash-free rate tells you how reliable an application is. It measures how often the app works as expected and completes its tasks without suddenly stopping or closing.
A high crash-free rate means the app is stable and you can count on it to run smoothly. For example, if an app has a 99% crash-free rate, it means that out of 100 times someone uses it, it will crash only once.
The crash-free rate is a key performance indicator (KPI) for software stability, typically expressed as a percentage. It is calculated as (Total Sessions - Crashed Sessions) / Total Sessions * 100, or equivalently, (Total Operations - Crashed Operations) / Total Operations * 100. This metric is crucial for user experience, as unexpected terminations can lead to data loss and frustration. Monitoring this rate helps developers identify and fix bugs that cause instability.
This term is relevant as frontier AI labs increasingly ship complex applications and tools. Ensuring these AI-powered products are stable and reliable for users is critical for adoption and trust, as highlighted by the development of applications like Sora.
- How We Used Codex to Ship Sora for Android in 28 DaysOpenAI · OpenAI News ·
- OpenAI ChatGPT
- OpenAI's development of applications like the Sora Android app relies on stable software, making crash-free rates an important metric for their product releases.
- Availability
- Availability measures if a system is operational and accessible, w
- Error rate
- Error rate tracks any type of error, not just those that cause a com
The concept of crash-free rate originates from general software engineering and quality assurance practices, used to quantify application stability.
Open a popular application on your phone or computer, like a web browser or a messaging app. Use it for a few minutes, performing various actions. If the app doesn't close unexpectedly during your session, you've experienced a 'crash-free' moment. To see a low rate, try using less stable or beta software.
The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.
- PromptRole-play a student struggling with math for AI tutor simulationSimulate a student's math struggles and uncertainty for AI tutor evaluation. · 5 min
- TemplateReusable workflow templates for healthcare teamsTeams can create and share templates for common workflows like documentation or prior authorizations. · 15 min
- TemplateTemplate for building an AI tool tailored to your workA structured approach to defining and building a custom AI tool for specific business needs. · 15 min
- TemplateEvals CSV prompt list for agent skillsA CSV file template for listing prompts used in evaluating agent skills. · 20 min
- HeuristicDouble coding agent task completion with docs linksProviding coding agents with a documentation link significantly increases their task completion rate. · 2 min
Questions people ask
- What is considered a good crash-free rate?
- Generally, a crash-free rate of 99% or higher is considered good for most applications, though expectations can vary based on the complexity and type of software.
- How is crash-free rate different from uptime?
- Uptime measures if a service is available, while crash-free rate measures if an application terminates unexpectedly during its use.
First seen on Subvolts Dec 12, 2025. Updated Sep 15, 2026. Written by an AI model from the items above and reviewed against them weekly; report an error.