Braze SLA
Uptime guarantee vs measured reliability
24h Uptime
—
7d Uptime
—
30d Uptime
—
Pricing & SLA by Tier
| Plan | SLA Guarantee | Price | Meeting 30d? |
|---|---|---|---|
| Core (quote-based) | No uptime SLA | Custom (~$40K–$100K/yr mid-market benchmarks) | — |
| Pro (quote-based) | No uptime SLA | Custom | — |
| Enterprise (quote-based) | No uptime SLA | Custom (~$300K–$1M+/yr enterprise benchmarks) | — |
Source: braze.com/pricing
Industry SLA Tier Compliance
| Tier | Downtime Budget/Month | 24h | 7d | 30d |
|---|---|---|---|---|
| 99.9%(three nines) | 43m 12s | |||
| 99.95% | 21m 36s | |||
| 99.99%(four nines) | 4m 19s | |||
| 99.999%(five nines) | 26s |
Equivalent Downtime
Last 24 hours
—
Last 7 days
—
Last 30 days
—
Incident Summary (90 days)
Total Incidents
6
Active Now
0
Resolved
6
Avg. Resolution
3h 20m
Braze SLA: What You Need to Know
Service Level Agreements (SLAs) define the minimum uptime a provider guarantees. Common tiers include 99.9% (the “three nines”), 99.95%, 99.99% (“four nines”), and 99.999% (“five nines”). Each additional nine dramatically reduces the allowable downtime — from about 43 minutes per month at 99.9% to just 26 seconds at 99.999%.
Based on DevHelm's continuous monitoring, Braze currently shows a 30-day measured uptime of —.
Impact on Your Application
Once sufficient monitoring data is collected, this section will show projected annual downtime. If your application depends on additional services, their independent failure probabilities compound — making dependency monitoring essential for maintaining your own SLA commitments.
Monitoring Methodology
DevHelm tracks Braze's official status page continuously and aggregates component-level status data into uptime percentages. Data is refreshed every 5 minutes. Uptime is calculated as the percentage of time all components report operational status.