TraceQL queries with "= nil" in Explore Traces and part of Drilldown Traces are failing with 400 Bad Request errors. The issue has been identified, and a fix is currently being rolled out.
Posted Dec 12, 2025 - 14:17 UTC
This incident affected: Grafana Cloud: Tempo (AWS Australia - prod-ap-southeast-2: Querying, AWS Brazil - prod-sa-east-1: Querying, AWS Canada - prod-ca-east-0: Querying, AWS Germany - prod-eu-west-2: Querying, AWS India - prod-ap-south-1: Querying, AWS Japan - prod-ap-northeast-0: Querying, AWS Singapore - prod-ap-southeast-1: Querying, AWS Sweden - prod-eu-north-0: Querying, AWS US East - prod-us-east-0: Querying, AWS US West - prod-us-west-0: Querying, Azure Germany - prod-eu-west-1: Querying, Azure Netherlands - prod-eu-west-3: Querying, Azure US Central - us-central2: Querying, GCP Australia - prod-au-southeast-0: Querying, GCP Belgium - prod-eu-west-0: Querying, GCP Brazil - prod-sa-east-0: Querying, GCP India - prod-ap-south-0: Querying, GCP Singapore - prod-ap-southeast-0: Querying, GCP UK - prod-gb-south-0: Querying, GCP US Central - prod-us-central-0: Querying, AWS US East - prod-us-east-2: Querying, GCP US Central - prod-us-central-5: Querying).