Braze Status: How to Check If Braze Is Down Right Now (2026)
Updated June 2026 · 7 min read · API Status Check
Quick Answer
Check Braze status at status.braze.com (official) for real-time status by cluster and service. Braze operates on regional clusters (US-01, EU-01, etc.) — check the status for your specific cluster, not just the global overview.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
The Official Braze Status Page
Braze maintains an official status page at status.braze.com, built on Statuspage.io. It tracks status per cluster and per service component — critical because Braze operates regional instances that can have independent issues:
Braze Regional Clusters — Why Your Cluster Matters
Braze runs on region-specific clusters. An outage on one cluster doesn't affect others. Your cluster is visible in your Braze dashboard URL or API endpoint:
US-01rest.iad-01.braze.comUS-02rest.iad-02.braze.comUS-03rest.iad-03.braze.comEU-01rest.fra-01.braze.euAU-01rest.syd-01.braze.comWhat Each Braze Status Means
Monitor your Braze API and push delivery independently
Better Stack monitors Braze REST API endpoints and push delivery health from multiple global locations. Get alerted before your campaigns silently fail. Free tier included.
Try Better Stack Free →Why Braze Issues Are Often Not a Platform Outage
Braze delivery failures have several common non-outage causes. Before escalating to Braze support, rule out these issues:
Expired APNs or FCM Push Certificates
The #1 cause of iOS push delivery failure on a healthy Braze platform is an expired Apple Push Notification service (APNs) certificate or a misconfigured Firebase Cloud Messaging (FCM) key. Check your push credentials under Braze Dashboard > Settings > App Settings > Push Notifications. APNs p8 keys don't expire, but p12 certificates do annually.
Braze API Rate Limits
The Braze REST API enforces per-endpoint rate limits (250,000 requests/hour for the /users/track endpoint by default). If your backend is making high-volume API calls without rate limit handling, requests will be rejected with 429 errors. This looks like 'Braze is down' but is actually a rate limit issue. Check your API error responses and implement exponential backoff.
SDK Version Mismatch or Initialization Failure
Braze SDK initialization failures cause silent data loss — events aren't tracked, in-app messages don't display, and push tokens aren't registered. Check your app's Braze SDK initialization logs and verify you're on a supported SDK version. Braze deprecates older SDK versions periodically.
Campaign or Canvas Scheduling Errors
Messages not sending at the right time are often a scheduling or audience segment issue, not a Braze outage. Check the campaign's scheduled time zone, segment re-eligibility settings, and whether the campaign is active. The Braze Message Activity Log (under Analytics) shows per-message delivery status.
5 Ways to Check Braze Status Right Now
Official Braze Status Page
Visit status.braze.com for real-time status by cluster and component. Subscribe to email notifications for your specific cluster (e.g., US-01 or EU-01).
status.braze.com →Braze Status API (Statuspage.io)
Query Braze's status programmatically via the Statuspage.io API. Returns JSON with current status indicator and description for your cluster.
# Check Braze status via Statuspage.io API
curl -s https://status.braze.com/api/v2/status.json | \
python3 -m json.tool
# Response: {"status": {"indicator": "none", "description": "All Systems Operational"}}
# indicator: none=ok, minor=degraded, major=partial, critical=major outageBraze Message Activity Log
Use the Braze dashboard's Message Activity Log (Analytics > Message Activity Log) to trace individual message delivery status, errors, and failure reasons for specific users or campaigns.
X/Twitter Search
Search 'Braze down' or 'Braze push not working' on X for real-time reports from other Braze customers.
Search X for 'Braze down' →Braze Support
Contact Braze support at braze.com/resources/support if the issue persists. Braze Enterprise customers have dedicated support with SLA response times.
Braze Support →Common Braze Errors and What They Mean
These are the errors and symptoms you'll see when Braze is experiencing issues:
"Push notifications not being delivered"Check status.braze.com for Push Delivery status on your cluster. If green, check your APNs/FCM credentials under App Settings. Verify the target users have push enabled and the correct push token registered. Use the Braze Message Activity Log to see the delivery status for specific users."Braze API returning 429 Too Many Requests"You've hit Braze API rate limits. Implement exponential backoff and retry logic in your API client. Consider batching /users/track calls (up to 75 events per request). Check your current rate limit tier with your Braze account manager."Email campaigns not sending / stuck in queue"Check the Email Sending component on status.braze.com. Also verify your sending IP isn't on a blocklist, your sending domain's SPF/DKIM records are correct, and the campaign's delivery schedule is configured for the right time zone."Braze dashboard shows 500 or 503 errors"Server-side Braze dashboard errors. Check status.braze.com Dashboard component status immediately. If an incident is posted, wait for Braze's resolution update. If no incident is posted, try a different browser or incognito mode and contact support."SDK events not appearing in Braze"SDK initialization failure or data ingestion backlog. Verify Braze SDK initialization in your app logs. Check the Data Ingestion component on status.braze.com. Events may be queued and appear with a delay during high-load periods."Connected Content calls failing in campaigns"Connected Content fetches happen at message send time from Braze's servers. If your Connected Content endpoint is down or returning errors, messages may fail or send without the dynamic content. Check the Webhooks & Connected Content component on status.braze.com.What to Do When Braze Is Down
Immediate Response
- Confirm on status.braze.com for your specific cluster
- Pause scheduled campaigns that would be delayed or duplicated
- Check if the outage affects all channels or just one (push vs. email)
- Notify your CRM/growth team to pause manual sends
- Document which campaigns were affected for post-incident review
Long-Term Resilience
- Subscribe to status.braze.com alerts for your cluster
- Monitor your Braze REST API endpoint independently with uptime tools
- Set APNs/FCM certificate renewal reminders (before they expire)
- Build retry logic into all Braze API integrations
- Test your fallback channel (email if push fails) in your Canvas flows
Frequently Asked Questions
Where is the official Braze status page?
Braze's official status page is at status.braze.com. It's built on Statuspage.io and shows real-time status per cluster (US-01, EU-01, etc.) and per service (push, email, API, SDK ingestion). Subscribe to your cluster's email notifications for automatic outage alerts.
Is Braze down or is it a certificate/configuration issue?
Check status.braze.com first. If green, check your push certificates (APNs/FCM) — expired certificates are the #1 cause of push failure on a healthy Braze platform. Use the Braze Message Activity Log (Analytics > Message Activity Log) to see delivery status for specific users and error codes.
How often does Braze go down?
Braze's historical uptime is typically above 99.9% for most clusters. Most incidents are component-level (e.g., push delivery delay) rather than full platform outages. Braze publishes incident history at status.braze.com.
Does Braze have an SLA for uptime?
Braze Enterprise contracts include uptime SLAs, typically 99.9%. If Braze falls below the SLA threshold, Enterprise customers may be eligible for service credits. Starter and Growth plans don't include explicit uptime SLAs. Review your contract or contact your Braze account manager for SLA details.
Why does Braze show operational but my push isn't sending?
Braze status pages reflect infrastructure health, not delivery correctness. Your push can fail while Braze infrastructure is 'green' due to: expired APNs/FCM credentials, users who haven't opted into push, incorrect campaign audience segments, or rate limiting on high-volume sends. Use the Message Activity Log and Delivery Reports to diagnose non-outage delivery failures.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Braze goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Braze + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial