Mimir query unexpected response with status code 500

Final update

From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.

1. Resolved · Nov 10, 12:09 UTC
   From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.
2. Monitoring · Nov 10, 11:18 UTC
   Our mitigation remains in place and query behavior in AWS US East (OH) and GCP US Central continues to improve. Some customers may still see occasional, brief query errors in the meantime.
3. Monitoring · Nov 10, 09:53 UTC
   Our mitigation remains in place and query behavior in AWS US East (OH) and GCP US Central continues to improve. Some customers may still see occasional, brief query errors in the meantime.
4. Monitoring · Nov 10, 04:42 UTC
   A fix has been implemented and we are monitoring the results.
5. Identified · Nov 10, 03:39 UTC
   We’ve identified an issue querying older data, and are already seeing recovery.
6. Identified · Nov 10, 03:38 UTC
   We’ve identified an issue querying older data, and are already seeing recovery