All Systems Operational

Uptime over the past 90 days. View historical uptime.
Platform Operational
90 days ago
100.0 % uptime
Today
Advertising Operational
90 days ago
100.0 % uptime
Today
Personalization Operational
90 days ago
100.0 % uptime
Today
Email Marketing Operational
90 days ago
100.0 % uptime
Today
Analytics Operational
90 days ago
100.0 % uptime
Today
Tracking Status (Web SDK) Operational
90 days ago
100.0 % uptime
Today
Data Collection Operational
90 days ago
100.0 % uptime
Today
Data Pipeline Operational
90 days ago
100.0 % uptime
Today
CDP Operational
90 days ago
99.92 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Aug 16, 2026

No incidents reported today.

Aug 15, 2026

No incidents reported.

Aug 14, 2026

Lattice Database Partial Outage
Resolved - The issue is now fully resolved, and monitoring has shown all operations has gone back to normal.

Normal database maintenance and optimization operations in the background combined with a node reboot caused some replica nodes to enter a long, blocking startup phase that required cleanup of the incomplete processes as well as normal startup operations. During this time, the node would still accept queries but not have the capacity to execute them, causing connections and queries to hang. These queries would persist, queued, and cause the node to fail performance-wise following startup, causing another reboot. This then triggered the process all over again.

Once the affected nodes were quarantined, query operations resumed normally on healthy nodes. We also paused the running of schema and ingestion tasks, which queued instead. This allowed the nodes to complete the startup and optimization processes without impedance.

Once the nodes were operational they could rejoin the cluster and resume accepting queries. Once the cluster was fully healed, all operations could resume. The ingestion + schema changes ran into no roadblocks and query performance continued to perform normally.

Alerts and quarantine automation have been created to handle this situation in the future with much faster resolution times and little to no noticeable changes to performance and capabilities in the Platform.
Aug 14, 20:49 PDT
Monitoring - All nodes are now functional and operating normally. There is no inconsistent behavior anymore, and all queued schema changes and data ingestion are running normally.

We'll continue to monitor to verify that the nodes remain healthy and that everything wraps up accordingly.
Aug 14, 19:57 PDT
Update - 50% of the affected replication nodes are now healthy; we are continuing to work on getting the remaining nodes back into an operational state. Querying data continues to not be affected.
Aug 14, 18:00 PDT
Identified - We have identified degraded performance in a portion of our customer data warehouse system, causing the nodes to fall behind in their replication process. We've isolated the affected nodes and are working on getting them back up-and-running.

At this time, customers can read their data using Data Studio and the associated Record views. Ingesting new data and changing schemas for native objects are queued but not being processed at this time.

We'll provide another update as soon as we get the affected nodes back up-and-running.
Aug 14, 15:59 PDT

Aug 13, 2026

No incidents reported.

Aug 12, 2026

No incidents reported.

Aug 11, 2026

No incidents reported.

Aug 10, 2026

No incidents reported.

Aug 9, 2026

No incidents reported.

Aug 8, 2026

No incidents reported.

Aug 7, 2026

No incidents reported.

Aug 6, 2026

No incidents reported.

Aug 5, 2026

No incidents reported.

Aug 4, 2026

No incidents reported.

Aug 3, 2026

No incidents reported.

Aug 2, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage