AWS Australia - prod-ap-southeast-2: QueryingAWS Australia - prod-ap-southeast-2: IngestionAWS Brazil - prod-sa-east-1: QueryingAWS Brazil - prod-sa-east-1: IngestionAWS Canada - prod-ca-east-0: QueryingAWS Canada - prod-ca-east-0: IngestionAWS Germany - prod-eu-west-2: QueryingAWS Germany - prod-eu-west-2: IngestionAWS UAE - prod-me-central-1: QueryingAWS UAE - prod-me-central-1: IngestionAWS India - prod-ap-south-1: QueryingAWS India - prod-ap-south-1: IngestionAWS Japan - prod-ap-northeast-0: QueryingAWS Japan - prod-ap-northeast-0: IngestionAWS Singapore - prod-ap-southeast-1: QueryingAWS Singapore - prod-ap-southeast-1: IngestionAWS Sweden - prod-eu-north-0: QueryingAWS Sweden - prod-eu-north-0: IngestionAWS US East - prod-us-east-0: QueryingAWS US East - prod-us-east-0: IngestionAWS US West - prod-us-west-0: QueryingAWS US West - prod-us-west-0: IngestionAzure Netherlands - prod-eu-west-3: QueryingAzure Netherlands - prod-eu-west-3: IngestionAWS Ireland - prod-eu-west-6AWS Switzerland - prod-eu-central-0Azure US Central - us-central2: QueryingAzure US Central - us-central2: IngestionAzure US Central - us-central7: IngestionGCP Australia - prod-au-southeast-0: QueryingGCP Australia - prod-au-southeast-0: IngestionGCP Belgium - prod-eu-west-0: QueryingGCP Belgium - prod-eu-west-0: IngestionGCP Brazil - prod-sa-east-0: QueryingGCP Brazil - prod-sa-east-0: IngestionGCP India - prod-ap-south-0: QueryingGCP India - prod-ap-south-0: IngestionGCP Singapore - prod-ap-southeast-0: QueryingGCP Singapore - prod-ap-southeast-0: IngestionGCP UK - prod-gb-south-0: QueryingGCP UK - prod-gb-south-0: IngestionGCP US Central - prod-us-central-0: QueryingGCP US Central - prod-us-central-0: IngestionGCP US Central - prod-us-central-5: QueryingGCP US Central - prod-us-central-5: IngestionGCS US - cortex-prod-04: IngestionGCS US - cortex-prod-04: QueryingFederal Cloud - AWS US Gov West
Update timeline
investigatingApr 20, 2026, 02:09 PM UTC
We are currently experiencing a major incident causing elevated 429 (rate limit) errors across multiple regions, primarily impacting metrics querying. This is a high-priority issue, and our engineering team is actively engaged and working urgently to identify the root cause and restore full service as quickly as possible. Customers may experience widespread failures or delays when querying metrics during this time. We understand the significant impact this may have and will continue to provide updates as more information becomes available.
investigatingApr 20, 2026, 02:21 PM UTC
The issue is now confirmed to be widespread, affecting Prometheus across all regions. Customers may continue to experience elevated 429 (rate limit) errors, particularly when querying metrics, with failures or inconsistent responses possible. Our engineering team remains fully engaged and is actively working on mitigation and resolution efforts with the highest priority.
resolvedApr 20, 2026, 02:30 PM UTC
This incident has been resolved. Thank you for your patience.
Looking to track Grafana downtime and outages?
Pingoru polls Grafana's status page every 5 minutes
and alerts you the moment it reports an issue — before your
customers do.
Real-time alerts when Grafana reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Grafana alongside 5,000+ providers in one dashboard
