Skip to main content

Is Braze Down?

No — Braze is up

Reachable from all 8 checked regions

Average response time: 151ms

Last checked · checks run every 6 hours

Official status page: https://braze.statuspage.io

Braze uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
135ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 18 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

18-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: 100.00% uptime, 16 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 39 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
130ms
DNS 0ms TCP 2ms TLS 14ms TTFB 111ms
arn
122ms
DNS 0ms TCP 1ms TLS 12ms TTFB 98ms
bom
128ms
DNS 0ms TCP 3ms TLS 13ms TTFB 103ms
cdg
112ms
DNS 0ms TCP 2ms TLS 12ms TTFB 89ms
dfw
136ms
DNS 0ms TCP 1ms TLS 13ms TTFB 117ms
ewr
338ms
DNS 0ms TCP 2ms TLS 12ms TTFB 319ms
syd
132ms
DNS 0ms TCP 1ms TLS 11ms TTFB 113ms
yyz
112ms
DNS 0ms TCP 1ms TLS 14ms TTFB 99ms

What Braze does

Braze is a customer engagement platform that sends push notifications, email, SMS, WhatsApp messages, in-app messages and content cards using data collected through its SDKs. Marketing teams build campaigns in the dashboard and the platform decides who receives what and when. It runs on numbered regional clusters, and each customer's data and sending sit on exactly one of them.

What an outage looks like

Campaigns show as launched while recipients get nothing, because the dashboard and outbound messaging are separate components. Push stops while email still sends, or one channel lags by hours. When SDK data collection fails, new attributes and events never arrive, so segments quietly go stale and triggered campaigns do not fire. REST API calls return errors and Currents exports stop mid-stream.

What to do about it

Find your cluster, then read braze.statuspage.io. Braze reports US 01 to 08 and 10, EU 01 and 02, AU 01, ID 01, JP 01 and KR 01 separately, each with its own Dashboard, SDK Data Collection, Data Processing, REST APIs, Outbound Messaging, Currents and Cloud Data-Ingestion components. Global channel components for email, SMS, WhatsApp, push and content cards are listed above the clusters.

Is it down for everyone, or just you?

If this page says Braze is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

K
Klaviyo
A
ActiveCampaign
HubSpot
HubSpot
SendGrid (Twilio)
SendGrid (Twilio)

Braze outage FAQ

Which Braze cluster am I on?
It is usually visible in the dashboard address your team signs in to and in the REST endpoint your engineers call, and it decides which part of the status page applies to you. Braze runs numbered clusters in the US, EU, Australia, Indonesia, Japan and Korea, and an incident on US 03 says nothing about US 06. Reading the page without knowing your cluster is the most common way to misread an incident.
Did my campaign send twice?
It can if you relaunched during an incident. The dashboard and Outbound Messaging are separate components, so a campaign that appears not to have sent may be queued rather than failed, and relaunching it produces a second delivery once the queue drains. Wait for the component to return to operational and read the delivery reporting before resending anything to a live audience.
Do triggered campaigns fire later once the outage ends?
Not reliably, and this is the part worth auditing afterwards. Triggered sends depend on SDK Data Collection and Data Processing, which are separate components from Outbound Messaging: if the events never arrived, the trigger never fired and there is nothing queued to release later. Compare entry counts for the incident window against a normal day before assuming delivery caught up.
Is a failed email send Braze or my email provider?
Braze lists Email as a global channel component separate from the clusters, so start there. If Braze reports Email operational and sends still fail, the cause is more likely the sending domain, the provider relationship behind it, or a suppression rule on your side. In-app messages and content cards are rendered by the SDK and can keep working while email is stopped.
Does the dashboard being down stop live campaigns?
No. Dashboard and Outbound Messaging are separate components on every cluster, so sends already scheduled generally continue while the dashboard is unreachable. What you lose is the ability to read reporting, edit a campaign or stop a send, which matters most when something is going out wrongly. Plan for that case rather than treating a dashboard outage as cosmetic.

How we measure this

  • We request Braze's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Braze publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Braze goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required