Investigating Querying Issues

All affected systems have fully recovered.

We are beginning to see recovery across our systems. We will continue to monitor the situation in case of any regressions.

We are currently experiencing degraded performance. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes trace queries. SLO and Trigger alerts may be missed or delayed. Queries may return results, but those results may not be saved, meaning that loading queries that other people have run may fail. After the problem resolves, queries may need to be rerun.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.

We are currently experiencing degraded performance for queries. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs, Triggers, and Traces.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.

We are currently experiencing degraded performance for queries that access older data stored in cold storage. Due to an ongoing issue with AWS, some queries over historical data may fail to complete successfully or take longer than usual. This includes queries for SLOs and Triggers.

Queries over recent or “hot” data are not impacted.

Our team is closely monitoring the situation. We’ll provide updates here as more information becomes available.