Braze · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Braze status

Braze · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
115
Retained
100
Affected retained
0
Projection scope: complete · 100 retained of 115 reported components across 17 source groups · bounded/truncated source projection.
Dashboard Group: US 01 Cluster Operational
Dashboard Group: US 02 Cluster Operational
Dashboard Group: US 03 Cluster Operational
Dashboard Group: US 04 Cluster Operational
Dashboard Group: EU 01 Cluster Operational
Dashboard Group: US 06 Cluster Operational
Dashboard Group: US 08 Cluster Operational
Dashboard Group: US 05 Cluster Operational
Dashboard Group: EU 02 Cluster Operational
Dashboard Group: US 07 Cluster Operational
Braze.com Group: Global Services Operational
Email Group: Global Messaging Channels Operational
Dashboard Group: AU 01 Cluster Operational
Dashboard Group: US 10 Cluster Operational
Dashboard Group: ID 01 Cluster Operational
Dashboard Group: JP 01 Cluster Operational
Dashboard Group: KR 01 Cluster Operational
SDK Data Collection Group: US 01 Cluster Operational
SDK Data Collection Group: US 02 Cluster Operational
SDK Data Collection Group: US 03 Cluster Operational
Showing 20 of 100 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 424.48 ms feed latency
Operational
HTTP 200 · 82.13 ms feed latency
Operational
HTTP 200 · 123.42 ms feed latency
Operational
HTTP 200 · 175.0 ms feed latency
Operational
HTTP 200 · 207.92 ms feed latency
Operational
HTTP 200 · 151.95 ms feed latency
Operational
HTTP 200 · 173.64 ms feed latency
Operational
HTTP 200 · 81.31 ms feed latency
Operational
HTTP 200 · 156.72 ms feed latency
Operational
HTTP 200 · 63.84 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
218.96 ms