All Systems Operational

Uptime over the past 90 days. View historical uptime.
Console Operational
90 days ago
99.98 % uptime
Today
Config Delivery API Operational
90 days ago
99.91 % uptime
Today
US West 1 Operational
90 days ago
99.92 % uptime
Today
US East 1 Operational
90 days ago
99.91 % uptime
Today
US East 5 Operational
90 days ago
99.92 % uptime
Today
Europe West 1 Operational
90 days ago
99.92 % uptime
Today
Asia Southeast 1 Operational
90 days ago
99.9 % uptime
Today
Log Event API Operational
90 days ago
100.0 % uptime
Today
Console API Operational
90 days ago
99.96 % uptime
Today
Experiment Results (Cloud) Operational
90 days ago
100.0 % uptime
Today
Experiment Results (Warehouse Native) Operational
90 days ago
99.93 % uptime
Today
Event Forwarding Pipeline (Warehouse Native) Operational
90 days ago
99.93 % uptime
Today
Marketing Site Operational
90 days ago
100.0 % uptime
Today
Docs Operational
90 days ago
99.98 % 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.

Jul 9, 2026

No incidents reported today.

Jul 8, 2026
Feature Flag Evaluation Errors (Statsig)
Resolved - Between approximately 20:56 UTC on July 8 and 01:40 UTC on July 9, customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. During this window, launched Gates could return false instead of their expected default. V1 consumers were not affected.

We identified the root cause as a recent change to config-spec generation. We rolled back the affected services across all regions and regenerated config payloads. We have verified that launched Gates are again returning their expected defaults, and all Config Delivery API components are now operational.

No action is required to restore correct evaluation going forward. However, if your systems persisted data or took actions based on evaluations returned by the V2 Config Delivery API during the impact window, we recommend reviewing and reconciling that downstream data, as affected launched Gates may have returned false during that time.
Jul 8, 19:36 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 8, 19:15 PDT
Update - We are continuing to work on a fix for this issue.
Jul 8, 18:39 PDT
Update - We are continuing to work on a fix for this issue.
Jul 8, 18:35 PDT
Update - We are continuing to work on a fix for this issue.
Jul 8, 18:29 PDT
Identified - Since approximately 1:56 PM PT on July 8 (20:56 UTC on July 8), customers using the V2 Config Delivery API may have experienced incorrect evaluation of launched Feature Gates. Specifically, launched Gates may have returned false instead of their expected default value.

Our team identified the root cause as a recent code change and started a rollback of the affected services. We were actively working to confirm that evaluations returned by the V2 Config Delivery API were again showing expected defaults for launched Gates.

V1 consumers were not affected. At the time of this update, no immediate customer action was required.

We would provide the next update as more information became available.
Jul 8, 18:28 PDT
Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026

No incidents reported.

Jul 1, 2026

No incidents reported.

Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage