Tempo and Mimir Read and Write Failures
Sep 3, 22:13 UTCSep 4, 00:55 UTC
Duration
2h 42m
Impact
Minor
Root cause
Not disclosed
Grafana Labs, 90 days
66 incidents
Affected
AWS US West - prod-us-west-0: QueryingAWS US West - prod-us-west-0: IngestionMetrics - AWS US West - prod-us-west-0: QueryingMetrics - AWS US West - prod-us-west-0: IngestionTraces - AWS US West - prod-us-west-0: QueryingTraces - AWS US West - prod-us-west-0: Ingestion
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 4, 00:55 UTC
This incident has been resolved.
- Monitoring · Sep 3, 22:48 UTC
Tempo recovered.
- Identified · Sep 3, 22:31 UTC
Cluster Metrics are healthy for the last 15 minutes
- Identified · Sep 3, 22:13 UTC
The issue has been identified and a fix is being implemented.
More from Grafana Labs
Full historySynthetic Monitoring , Jakarta Public Probe Degradationlasted 0mGitHub returning 403 for all Git Sync repositorieslasted 1h 58mOctober usage report visualization issuelasted 3d 3hIncreased query latency for Logs in GCP US Central (prod-us-central-0)lasted 1h 31mElevated Request Errors for Grafana Across Multiple Regionslasted 1h 1mGrafana Cloud: k6 timeoutslasted 0m