Snapshot 15001
Normalized text
Scripts and page chrome removed; this is what change detection compares.
{
"pages": [
{
"end_time": "2026-09-30T23:59:59-04:00",
"months": [
{
"incidents": [
{
"code": "pg8vz543zy64",
"impact": "critical",
"message": "This issue has been resolved. Our Global Support Service is operating normally, and customers can raise cases via the Braze Support Portal and the Braze AI Operator as usual.\n\nWe have confirmed stable service following remediation of the underlying Salesforce Service Cloud issue.",
"name": "Braze Support Services Outage",
"timestamp": "Sep \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e05:17\u003c/var\u003e - \u003cvar data-var='time'\u003e12:09\u003c/var\u003e EDT"
},
{
"code": "fk65n5lvy0js",
"impact": "minor",
"message": "This was a recurrence of an earlier issue impacting the Dashboard. A permanent fix has been implemented and the Dashboard has remained stable since. We are confident the issue is now fully resolved. We apologize for any impact.",
"name": "Dashboard Latency and Errors on US07",
"timestamp": "Sep \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e07:30\u003c/var\u003e - \u003cvar data-var='time'\u003e07:58\u003c/var\u003e EDT"
},
{
"code": "mj5q87q28pw3",
"impact": "minor",
"message": "The Dashboard has continue to remain stable and the issue is now resolved.",
"name": "Latency and Errors on US07",
"timestamp": "Sep \u003cvar data-var='date'\u003e2\u003c/var\u003e, \u003cvar data-var='time'\u003e03:43\u003c/var\u003e - \u003cvar data-var='time'\u003e06:09\u003c/var\u003e EDT"
}
],
"name": "September",
"year": 2026
},
{
"incidents": [
{
"code": "py2lt7v0358t",
"impact": "minor",
"message": "Between 11:30 ET and 12:55 ET, some customers experienced elevated error rates. Braze engineers identified the issue and resolved it by rolling back a recent change and applying database optimizations.\n\nError rates returned to normal shortly after each fix was applied, and they have remained stable for the past hour. This incident is now resolved.",
"name": "Issue Impacting US 01 and US 03",
"timestamp": "Aug \u003cvar data-var='date'\u003e5\u003c/var\u003e, \u003cvar data-var='time'\u003e12:13\u003c/var\u003e - \u003cvar data-var='time'\u003e13:54\u003c/var\u003e EDT"
},
{
"code": "lj49g8hrpwhd",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] US 05 Database Maintenance",
"timestamp": "Aug \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e03:00\u003c/var\u003e - \u003cvar data-var='time'\u003e04:00\u003c/var\u003e EDT"
},
{
"code": "3qkg01kg7sjd",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] US 02 Database Maintenance",
"timestamp": "Aug \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e03:00\u003c/var\u003e - \u003cvar data-var='time'\u003e04:00\u003c/var\u003e EDT"
}
],
"name": "August",
"year": 2026
},
{
"incidents": [
{
"code": "zvbd3ndgw82g",
"impact": "minor",
"message": "This incident is resolved. As of 15:18 ET / 19:18 UTC, we have fully processed the backlog of jobs, and our EU02 Currents connectors are all again processing within normal latency ranges. No data was lost, and all Currents events have been sent to their destinations.",
"name": "EU02 Currents Data Latency",
"timestamp": "Jul \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e10:09\u003c/var\u003e - \u003cvar data-var='time'\u003e15:25\u003c/var\u003e EDT"
},
{
"code": "1nt3f10mxrlc",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] JP 01 Database Maintenance",
"timestamp": "Jul \u003cvar data-var='date'\u003e31\u003c/var\u003e, \u003cvar data-var='time'\u003e11:00\u003c/var\u003e - \u003cvar data-var='time'\u003e12:00\u003c/var\u003e EDT"
},
{
"code": "zffh11rqskxq",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] EU 01 Database Maintenance",
"timestamp": "Jul \u003cvar data-var='date'\u003e30\u003c/var\u003e, \u003cvar data-var='time'\u003e19:00\u003c/var\u003e - \u003cvar data-var='time'\u003e20:00\u003c/var\u003e EDT"
},
{
"code": "dn437cy6sr7q",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] US 07 Database Maintenance",
"timestamp": "Jul \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e14:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e EDT"
},
{
"code": "cnbw8grczr99",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] US 06 Database Maintenance",
"timestamp": "Jul \u003cvar data-var='date'\u003e27\u003c/var\u003e, \u003cvar data-var='time'\u003e23:00\u003c/var\u003e - Jul \u003cvar data-var='date'\u003e28\u003c/var\u003e, \u003cvar data-var='time'\u003e00:00\u003c/var\u003e EDT"
},
{
"code": "4nhzyh2gvbtt",
"impact": "none",
"message": "At approximately 7:30 AM ET, we became aware of an AWS networking outage in the US-WEST-2 region affecting network connectivity between 6:55 AM ET and 8:00 AM ET. AWS has since resolved the underlying issue. During the impact window, some customers may have experienced intermittent delays and latency in email delivery.\n\nMail is now being delivered normally. As queue depth increased, some customers may have experienced residual delays in message delivery. These delays have been resolved as of 2:40 PM ET today.\n\nThis disruption originated within AWS infrastructure and was not caused by any component of the Braze platform. \n\nFor further details on the AWS incident, please refer to the AWS status page: https://health.aws.amazon.com/health/status",
"name": "AWS Networking Disruption in US-WEST-2 (Resolved)",
"timestamp": "Jul \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e EDT"
},
{
"code": "ppp90dtwc25s",
"impact": "none",
"message": "The issue impacting the Braze AI Operator, where users were seeing the error message: \"Connection unstable - Check your Wi-Fi or internet signal and try again,\" has been fully resolved. The fix has been deployed and error rates have returned to normal levels.",
"name": "Braze AI Operator Errors",
"timestamp": "Jul \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e14:43\u003c/var\u003e - \u003cvar data-var='time'\u003e17:31\u003c/var\u003e EDT"
}
],
"name": "July",
"year": 2026
}
],
"start_time": "2026-07-01T00:00:00-04:00",
"time_zone": "Eastern Time (US \u0026 Canada)"
},
{
"end_time": "2026-06-30T23:59:59-04:00",
"months": [
{
"incidents": [
{
"code": "b23ylk1h3qgx",
"impact": "minor",
"message": "Meta has recovered from the earlier issue impacting WhatsApp services, and full service has now been restored. WhatsApp message delivery, Campaign and Canvas creation or modification using WhatsApp templates, and Audience sync to Facebook are all operating normally.",
"name": "WhatsApp Degraded Performance",
"timestamp": "Jun \u003cvar data-var='date'\u003e12\u003c/var\u003e, \u003cvar data-var='time'\u003e10:58\u003c/var\u003e - \u003cvar data-var='time'\u003e14:13\u003c/var\u003e EDT"
}
],
"name": "June",
"year": 2026
},
{
"incidents": [
{
"code": "c37y5p7kq87w",
"impact": "minor",
"message": "Latency and error rates have remained at normal levels across all services following the implementation of our fix. This incident is resolved.",
"name": "US01 and EU01 Processing Latency",
"timestamp": "May \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e13:45\u003c/var\u003e - \u003cvar data-var='time'\u003e14:41\u003c/var\u003e EDT"
},
{
"code": "klqfbypwzdxy",
"impact": "minor",
"message": "Latency has returned to normal operational bounds and this incident is now resolved. \n\nTwilio's Statuspage will continue to provide updates on the remaining impact to Romania, Serbia, Poland, Bosnia and Herzegovina, and Cabo Verde: https://status.twilio.com/incidents/shhrhbqxflt1",
"name": "SMS Delivery Delays to Multiple Countries in Europe",
"timestamp": "May \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e09:19\u003c/var\u003e - May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e08:36\u003c/var\u003e EDT"
},
{
"code": "g3hb7gy7ngyw",
"impact": "minor",
"message": "Latency and error rates have remained at normal levels for all services, post-implementation of our fix, and this incident is resolved. \n\nWe will continue to monitor the overall system health until AWS reports full recovery. \n\nPlease see https://health.aws.amazon.com/health/status for more details.",
"name": "US05 Processing Latency",
"timestamp": "May \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e00:35\u003c/var\u003e - \u003cvar data-var='time'\u003e01:47\u003c/var\u003e EDT"
},
{
"code": "xd76x24wy2nm",
"impact": "minor",
"message": "Following continued monitoring by our engineers, Agent Console auto models have remained stable. This incident is now resolved.",
"name": "Agent Console auto model errors",
"timestamp": "May \u003cvar data-var='date'\u003e7\u003c/var\u003e, \u003cvar data-var='time'\u003e12:38\u003c/var\u003e - \u003cvar data-var='time'\u003e13:19\u003c/var\u003e EDT"
}
],
"name": "May",
"year": 2026
},
{
"incidents": [
{
"code": "9x52j85jcbng",
"impact": "major",
"message": "The message backlog has been cleared, and data processing has returned to normal operational bounds. All services continue to remain stable, and this incident is considered resolved.",
"name": "Issue impacting EU01",
"timestamp": "Apr \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e12:18\u003c/var\u003e - \u003cvar data-var='time'\u003e15:24\u003c/var\u003e EDT"
},
{
"code": "vytkjcghwgys",
"impact": "none",
"message": "Between 16:00 and 18:14 ET, Braze Engineers identified and resolved an issue causing intermittent SDK errors on the US01 cluster. As of 18:19 ET, services remain stable, and any failed SDK requests during the impact window were automatically retried.",
"name": "US01 SDK errors",
"timestamp": "Apr \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:00\u003c/var\u003e EDT"
},
{
"code": "b0y0lgvnf8xg",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:20\u003c/var\u003e EDT"
},
{
"code": "zw2kyb6nr1yt",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e16\u003c/var\u003e, \u003cvar data-var='time'\u003e07:15\u003c/var\u003e - \u003cvar data-var='time'\u003e07:40\u003c/var\u003e EDT"
},
{
"code": "zyzxjq6xy1br",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e15:30\u003c/var\u003e - \u003cvar data-var='time'\u003e15:50\u003c/var\u003e EDT"
},
{
"code": "7cr56x6grd8r",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e15\u003c/var\u003e, \u003cvar data-var='time'\u003e15:00\u003c/var\u003e - \u003cvar data-var='time'\u003e15:20\u003c/var\u003e EDT"
},
{
"code": "nf39psbpf18l",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e14\u003c/var\u003e, \u003cvar data-var='time'\u003e15:15\u003c/var\u003e - \u003cvar data-var='time'\u003e15:40\u003c/var\u003e EDT"
},
{
"code": "1ry2m6gddhx7",
"impact": "maintenance",
"message": "The scheduled maintenance has been completed.",
"name": "[Scheduled] Scheduled maintenance for Braze CDI",
"timestamp": "Apr \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e14:15\u003c/var\u003e - \u003cvar data-var='time'\u003e14:40\u003c/var\u003e EDT"
},
{
"code": "r94vq8sh1jbm",
"impact": "major",
"message": "The issue affecting email processing for support cases has been resolved.\n\nNew cases sent to support@braze.com and replies to existing cases are now being processed as expected. Our Support team is actively working through the backlog of requests created during the disruption.\n\nThank you for your patience while we worked through this.",
"name": "Delays in Support Case Creation via Email",
"timestamp": "Apr \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e15:05\u003c/var\u003e - \u003cvar data-var='time'\u003e17:49\u003c/var\u003e EDT"
},
{
"code": "k9zy9x60f6g5",
"impact": "none",
"message": "Between 17:00 and 18:35 EST, Braze Engineers identified and resolved an issue causing intermittent SDK errors on the US01 cluster. As of 18:40 EST, services remain stable, and any failed SDK requests during the impact window were automatically retried.",
"name": "US01 SDK errors",
"timestamp": "Apr \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e17:00\u003c/var\u003e - \u003cvar data-var='time'\u003e17:00\u003c/var\u003e EDT"
}
],
"name": "April",
"year": 2026
}
],
"start_time": "2026-04-01T00:00:00-04:00",
"time_zone": "Eastern Time (US \u0026 Canada)"
},
{
"end_time": "2026-03-31T23:59:59-04:00",
"months": [
{
"incidents": [
{
"code": "l750zstxqlz2",
"impact": "minor",
"message": "No further issues have been experienced, and all services are operating normally. The incident is now resolved.",
"name": "EU02 customer unsubscribe errors",
"timestamp": "Mar \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e13:45\u003c/var\u003e - \u003cvar data-var='time'\u003e13:58\u003c/var\u003e EDT"
},
{
"code": "d7d7d7jxnhs7",
"impact": "minor",
"message": "No further issues have been experienced, and all services are operating normally. The incident is now resolved.",
"name": "US07 Dashboard latency and errors",
"timestamp": "Mar \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e14:25\u003c/var\u003e - \u003cvar data-var='time'\u003e15:29\u003c/var\u003e EDT"
},
{
"code": "2g71jlh6rzmz",
"impact": "major",
"message": "No further issues have been experienced, and all services are operating normally. The incident is now resolved.",
"name": "US05 Dashboard latency",
"timestamp": "Mar \u003cvar data-var='date'\u003e17\u003c/var\u003e, \u003cvar data-var='time'\u003e16:49\u003c/var\u003e - \u003cvar data-var='time'\u003e17:04\u003c/var\u003e EDT"
}
],
"name": "March",
"year": 2026
},
{
"incidents": [
{
"code": "2t0vhpd1tjtq",
"impact": "minor",
"message": "As of 14:41 ET, Sparkpost has declared this incident resolved after implementing a fix. Braze Engineers have confirmed that real time outbound email latency has returned within normal operational bounds as of 14:34 ET. Any messages that failed during this window, were automatically retried.\n\nThis incident is considered resolved.",
"name": "Outbound email latency for non-EU Bird (Sparkpost) customers",
"timestamp": "Feb \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e14:34\u003c/var\u003e - \u003cvar data-var='time'\u003e15:00\u003c/var\u003e EST"
},
{
"code": "y2wcd3t4856v",
"impact": "minor",
"message": "We can confirm services have continued to remain stable and the issue is now considered resolved.",
"name": "EU01 \u0026 EU02 Dashboard Errors",
"timestamp": "Feb \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e07:07\u003c/var\u003e - \u003cvar data-var='time'\u003e14:22\u003c/var\u003e EST"
},
{
"code": "8h9jjpn799vn",
"impact": "critical",
"message": "We can confirm service have continued to remain stable and the issue is now considered resolved.\n\nImpact:\nSDK: Engineers observed an increase in SDK errors between 10:25 ET and 10:36 ET. The SDK will automatically retry failed requests and no action is required.\nDashboard: Engineers observed an increased in Dashboard errors between 10:26 ET and 10:43 ET. Dashboard users may have experienced timeouts and dashboard errors during this window.\n\nMessage sending and the REST API were not impacted by this issue.",
"name": "US02 Dashboard and SDK increased errors",
"timestamp": "Feb \u003cvar data-var='date'\u003e3\u003c/var\u003e, \u003cvar data-var='time'\u003e10:41\u003c/var\u003e - \u003cvar data-var='time'\u003e11:02\u003c/var\u003e EST"
}
],
"name": "February",
"year": 2026
},
{
"incidents": [
{
"code": "qp3dq7pgqfmx",
"impact": "none",
"message": "As of 8:28 PM EST, Google has resolved the issue. We recommend continuing to monitor Gmail’s status page for Google’s final incident analysis and to use Braze’s Deliverability Center while following email-sending best practices.",
"name": "Gmail consumers experiencing banners indicating missing spam checks",
"timestamp": "Jan \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e13:27\u003c/var\u003e - \u003cvar data-var='time'\u003e20:59\u003c/var\u003e EST"
},
{
"code": "5x31z2wykxz2",
"impact": "minor",
"message": "We have not seen any instances of the specific error code in an hour, since 9:42 PM ET. \n\nThis incident is considered resolved.",
"name": "Email delivery issues",
"timestamp": "Jan \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e19:47\u003c/var\u003e - \u003cvar data-var='time'\u003e22:42\u003c/var\u003e EST"
},
{
"code": "gz1ltyvf558y",
"impact": "none",
"message": "Between 4:05 PM and 4:58 PM ET, some SMS messages experienced a temporary delivery delay. The issue has been fully resolved. All delayed messages were safely queued and are now being delivered. No messages were lost. \n\nOur systems are operating normally, and our team is monitoring to ensure continued stability.",
"name": "SMS outbound sending delays",
"timestamp": "Jan \u003cvar data-var='date'\u003e13\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:00\u003c/var\u003e EST"
},
{
"code": "19bm1v6gngbk",
"impact": "critical",
"message": "No further issues have been experienced and all services are operating normally. The incident is now resolved.",
"name": "US05 Dashboard Errors",
"timestamp": "Jan \u003cvar data-var='date'\u003e6\u003c/var\u003e, \u003cvar data-var='time'\u003e10:41\u003c/var\u003e - \u003cvar data-var='time'\u003e11:29\u003c/var\u003e EST"
}
],
"name": "January",
"year": 2026
}
],
"start_time": "2026-01-01T00:00:00-05:00",
"time_zone": "Eastern Time (US \u0026 Canada)"
},
{
"end_time": "2025-12-31T23:59:59-05:00",
"months": [
{
"incidents": [],
"name": "December",
"year": 2025
},
{
"incidents": [
{
"code": "hhntcjbjmh21",
"impact": "major",
"message": "The REST API and SDK Data Collection have continued to remain stable and this incident is considered resolved.",
"name": "EU01 REST API and SDK Data Collection Errors",
"timestamp": "Nov \u003cvar data-var='date'\u003e24\u003c/var\u003e, \u003cvar data-var='time'\u003e06:26\u003c/var\u003e - \u003cvar data-var='time'\u003e07:09\u003c/var\u003e EST"
},
{
"code": "4hft05t1403n",
"impact": "major",
"message": "US01 and US03 Dashboard and SDK services have remained stabled. The incident is now resolved.",
"name": "US01 and US03 Dashboard and SDK Errors",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e19:34\u003c/var\u003e - \u003cvar data-var='time'\u003e20:33\u003c/var\u003e EST"
},
{
"code": "rws5trsng255",
"impact": "none",
"message": "The US02 Dashboard and SDK have remained stable since 17:18 ET. We can confirm the incident is resolved.",
"name": "US02 Dashboard and SDK Errors",
"timestamp": "Nov \u003cvar data-var='date'\u003e18\u003c/var\u003e, \u003cvar data-var='time'\u003e17:24\u003c/var\u003e - \u003cvar data-var='time'\u003e17:35\u003c/var\u003e EST"
},
{
"code": "r5kw51f45hkz",
"impact": "none",
"message": "Braze Engineers identified a Dashboard configuration error that was deployed at 15:50 ET, preventing navigation and logins on EU02. At 16:04 ET, the errant configuration change was reverted, and a redeploy was executed.\n\nDuring this window, EU02 customers experienced issues navigating and accessing the Dashboard. All other services remained functional, all REST and SDK API requests were processed, campaign and canvas execution continued to function. No messages were dropped.",
"name": "EU02 Dashboard errors",
"timestamp": "Nov \u003cvar data-var='date'\u003e4\u003c/var\u003e, \u003cvar data-var='time'\u003e16:00\u003c/var\u003e - \u003cvar data-var='time'\u003e16:00\u003c/var\u003e EST"
}
],
"name": "November",
"year": 2025
},
{
"incidents": [
{
"code": "9q46v63b8j41",
"impact": "minor",
"message": "Braze Engineers have confirmed outbound message latency and service performance is now operating normally and within normal operational bounds. Engineers will continue to monitor service health across all clusters.\n\nThis incident has been resolved.",
"name": "Increased latency in Outbound Messaging for all clusters",
"timestamp": "Oct \u003cvar data-var='date'\u003e22\u003c/var\u003e, \u003cvar data-var='time'\u003e19:19\u003c/var\u003e - \u003cvar data-var='time'\u003e19:48\u003c/var\u003e EDT"
},
{
"code": "r0kkkj9pvd81",
"impact": "major",
"message": "This incident has been resolved. Twilio services have recovered from the AWS US East 1 outage. Customers can now login to the Braze dashboard via SMS authentication, send SMS messages through the Braze platform, and receive SMS responses from end users without issues. \n\nAll Braze systems are operating normally. Our engineering teams will continue standard monitoring.",
"name": "AWS US East 1 outage",
"timestamp": "Oct \u003cvar data-var='date'\u003e20\u003c/var\u003e, \u003cvar data-var='time'\u003e05:52\u003c/var\u003e - \u003cvar data-var='time'\u003e19:41\u003c/var\u003e EDT"
},
{
"code": "16x8458h312v",
"impact": "none",
"message": "Between 11:00 AM and 12:43 PM ET on October 8, 2025, Dashboard users on the US-10 cluster experienced errors accessing the Braze Dashboard. This service disruption occurred during remediation work for a misconfiguration issue, whereby Braze Engineering teams restarted services to implement the fix.\n\nDashboard access was fully restored as of 12:43 PM ET.",
"name": "US-10 Dashboard Outage - October 8, 2025",
"timestamp": "Oct \u003cvar data-var='date'\u003e8\u003c/var\u003e, \u003cvar data-var='time'\u003e06:00\u003c/var\u003e - \u003cvar data-var='time'\u003e06:00\u003c/var\u003e EDT"
}
],
"name": "October",
"year": 2025
}
],
"start_time": "2025-10-01T00:00:00-04:00",
"time_zone": "Eastern Time (US \u0026 Canada)"
}
]
}