We’ve implemented a fix and can confirm the issue is fully resolved as of 20:25 UTC.
Thank you for your patience.
Posted Jul 01, 2026 - 22:00 UTC
Investigating
We are investigating an issue where some customers may see higher Loki query byte usage reported than was actually consumed. This affects usage reporting only; there is no impact to query execution or service availability.
The issue began at approximately 13:20 UTC and is ongoing. We expect the issue to be resolved soon and will provide another update as more information becomes available.
Posted Jul 01, 2026 - 19:43 UTC
This incident affected: Logs (AWS Australia - prod-ap-southeast-2, AWS Brazil - prod-sa-east-1, AWS Canada - prod-ca-east-0, AWS Germany - prod-eu-west-2, AWS UAE - prod-me-central-1, AWS India - prod-ap-south-1, AWS Japan - prod-ap-northeast-0, AWS Singapore - prod-ap-southeast-1, AWS Sweden - prod-eu-north-0, AWS US West - prod-us-west-0, AWS US East - prod-us-east-0, AWS Ireland - prod-eu-west-6, AWS Switzerland - prod-eu-central-0, Azure Netherlands - prod-eu-west-3, Azure US Central - us-central2, Azure US Central - us-central7, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Singapore - prod-ap-southeast-0, GCP UK - prod-gb-south-0, GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-5, Federal Cloud - AWS US Gov West).