Trace querying issue in all Tempo clusters
Affected: AWS Australia - prod-ap-southeast-2: QueryingAWS Brazil - prod-sa-east-1: QueryingAWS Canada - prod-ca-east-0: QueryingAWS Germany - prod-eu-west-2: QueryingAWS India - prod-ap-south-1: QueryingAWS Japan - prod-ap-northeast-0: QueryingAWS Singapore - prod-ap-southeast-1: QueryingAWS Sweden - prod-eu-north-0: QueryingAWS US East - prod-us-east-0: QueryingAWS US West - prod-us-west-0: QueryingAzure Germany - prod-eu-west-1: QueryingAzure Netherlands - prod-eu-west-3: QueryingAzure US Central - us-central2: QueryingGCP Australia - prod-au-southeast-0: QueryingGCP Belgium - prod-eu-west-0: QueryingGCP Brazil - prod-sa-east-0: QueryingGCP India - prod-ap-south-0: QueryingGCP Singapore - prod-ap-southeast-0: QueryingGCP UK - prod-gb-south-0: QueryingGCP US Central - prod-us-central-0: QueryingAWS US East - prod-us-east-2: QueryingGCP US Central - prod-us-central-5: QueryingAWS Ireland - prod-eu-west-6: Querying
Timeline · 3 updates
- investigating Feb 27, 2026, 01:46 PM UTC
We're currently working on an issue where portions of data may be temporarily unretrievable, affecting a small percentage of tenants in all Tempo clusters.
- identified Feb 27, 2026, 07:27 PM UTC
Our team has identified the issue, and are in the process of testing a fix.
- resolved Feb 27, 2026, 11:38 PM UTC
This incident has been resolved.