Is Grafana down?

Last checked 9m ago
Current status
Grafana is down

Active incident: Complete outage in prod-me-central-1

Official status page: https://status.grafana.com · Polled every 5 minutes · 462 components tracked

Grafana is reporting a major outage right now (last checked 9m ago). 1 active incident on the official status page.

Real-time Grafana status, recent outages, and incident history — pulled directly from Grafana's official status page at https://status.grafana.com every 5 minutes. Pingoru tracks 462 Grafana services and has captured 63 incidents in the last 90 days (96.86% uptime). Get email, Slack, Discord, or webhook alerts the moment Grafana reports a new incident — free for 5 monitors, no credit card.

Users who monitor Grafana also follow these Analytics services: New Relic Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch FullStory View all 6,000+ providers
Grafana uptime 96.86% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incident 1

  1. Ongoing ● 103d 13h
    Started Mar 02, 2026, 06:43 AM UTC
    AWS UAE - prod-me-central-1AWS UAE - prod-me-central-1AWS UAE - prod-me-central-1: QueryingAWS UAE - prod-me-central-1: IngestionAWS UAE - prod-me-central-1AWS UAE - prod-me-central-1: APIAWS UAE - prod-me-central-1: Public ProbesAWS UAE - prod-me-central-1: QueryingAWS UAE - prod-me-central-1: IngestionAWS UAE - prod-me-central-1: Metrics Generator
    Timeline · 14 updates
    • investigating · Mar 02, 2026, 06:43 AM UTC

      We are seeing elevated write and read path errors in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.

    • investigating · Mar 02, 2026, 08:14 AM UTC

      We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.

    • investigating · Mar 02, 2026, 08:21 AM UTC

      We are observing write and read outage errors across all databases (metrics, logs, traces) in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.

    • investigating · Mar 02, 2026, 08:36 AM UTC

      We are updating this incident to reflect a complete outage in prod-me-central-1, due to an on-going AWS UAE data center issue. We will provide further updates accordingly.

    • investigating · Mar 02, 2026, 10:04 AM UTC

      Customers are recommended to configure a new blank stack in an alternative Grafana Cloud region and to reconfigure their clients (such as Grafana Alloy) to send telemetry to that region, Fleet Management can be used for this purpose https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/

    • investigating · Mar 02, 2026, 10:31 AM UTC

      AWS are recommending that affected customers move workloads to alternate regions https://health.aws.amazon.com/health/status and we are recommending the same. Customers who are impacted and who cannot wait for a restoration of service are asked to: 1. Create a Grafana Cloud stack in an alternate region 2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ 3. If your instance remains available and you have not configured your dashboards as code, then you may be able to use `grafanactl` to migrate dashboards https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanacli-workflows/ https://grafana.github.io/grafanactl/ We will provide updates when we have them, but we do not have an expected resolution time at this point.

    • investigating · Mar 02, 2026, 10:18 PM UTC

      Please continue to refer to the AWS status page for more detailed updates specific to AWS. https://health.aws.amazon.com/health/status AWS are recommending that affected customers move workloads to alternate regions, and we are recommending the same. Customers who are impacted and who cannot wait for a restoration of service are asked to: 1. Create a Grafana Cloud stack in an alternate region 2. Update clients to send telemetry to the new region, if using Grafana Alloy then you can use Fleet Management https://grafana.com/docs/grafana-cloud/send-data/fleet-management/introduction/ 3. If your instance remains available and you have not configured your dashboards as code, then you may be able to use `grafanactl` to migrate dashboards https://grafana.com/docs/grafana/latest/as-code/observability-as-code/grafana-cli/grafanacli-workflows/ https://grafana.github.io/grafanactl/ We are continuing to work with our CSP at this time, and will provide updates as they are available.

    • investigating · Mar 04, 2026, 10:28 AM UTC

      We are continuing to investigate this issue.

    • investigating · Mar 04, 2026, 10:22 PM UTC

      We are actively monitoring the situation, but at this time there are no new updates to share. The next update will be provided once we have more information to share. Please reach out to our Support team if you have any questions.

    • investigating · Mar 19, 2026, 12:13 PM UTC

      We have not received any further updates from AWS at this time. However, we are actively monitoring the outage and will provide additional information as it becomes available. Also, please continue to refer to the AWS status page for more detailed updates. https://health.aws.amazon.com/health/status All the guidance previously included about stack migration is still relevant. Please reach out to our Support team if you have any questions.

    • investigating · Apr 20, 2026, 03:11 PM UTC

      We are continuing to investigate this issue.

    • investigating · May 13, 2026, 09:59 PM UTC

      We do not have any additional updates to share at this time. Our team is actively monitoring the situation and will provide further information as it becomes available. In the meantime, please continue to refer to the AWS Status Page for the most detailed and up-to-date information.

    • investigating · May 21, 2026, 11:41 AM UTC

      AWS UAE - prod-me-central-1: Public Probe checks might suffer degraded experience. We recommend migrating checks from the UAE probe to the next nearest probe suitable for your use case.

    • investigating · May 27, 2026, 05:10 PM UTC

      The TLS certificates serving prod-me-central-1 endpoints expire on May 30, 2026. Replacement certificates have been imported, but the ongoing AWS regional incident is preventing them from propagating to all load balancer nodes, so customers may see certificate errors after that date until AWS restores normal operation. We do not have any additional updates to share at this time. Our team is actively monitoring the situation and will provide further information as it becomes available. In the meantime, please continue to refer to the AWS Status Page for the most detailed and up-to-date information.

    Latest: The TLS certificates serving prod-me-central-1 endpoints expire on May 30, 2026. Replacement certificates have been imported, but the ongoing AWS regional incident is preventing th…

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 12, 2026, 09:54 PM UTC · Resolved Jun 12, 2026, 06:30 PM UTC
    Timeline · 1 update
    • resolved · Jun 12, 2026, 09:54 PM UTC

      Our team had discovered a read issue around 19:35-20:08 UTC. Impact at the time would have provided errors similar to context deadline exceeded (DatasourceError response). This has since been resolved, and should not have caused any data loss, only a short query disruption.

    Latest: Our team had discovered a read issue around 19:35-20:08 UTC. Impact at the time would have provided errors similar to context deadline exceeded (DatasourceError response). This has…

  2. Resolved 18h 46m
    Started Jun 10, 2026, 10:49 AM UTC · Resolved Jun 11, 2026, 05:36 AM UTC
    AWS Australia - prod-ap-southeast-2AWS Brazil - prod-sa-east-1AWS Canada - prod-ca-east-0AWS Germany - prod-eu-west-2AWS Germany - prod-eu-west-4AWS India - prod-ap-south-1AWS Japan - prod-ap-northeast-0AWS UAE - prod-me-central-1AWS Singapore - prod-ap-southeast-1AWS Sweden - prod-eu-north-0
    Timeline · 2 updates
    • investigating · Jun 10, 2026, 10:49 AM UTC

      We’re currently investigating an issue affecting The Grafana Dashboards page. When set to view by folders, is currently experiencing an issue where no dashboards are shown. Our team is working on fixing the problem. In the meantime, switching to ‘View as list’ allows access to dashboards as usual”.

    • resolved · Jun 11, 2026, 05:36 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 14h
    Started Jun 09, 2026, 11:11 PM UTC · Resolved Jun 10, 2026, 01:11 PM UTC
    AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration APIAWS Australia - prod-ap-southeast-2: AlertmanagerAWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIAWS Brazil - prod-sa-east-1: AlertmanagerAWS Canada - prod-ca-east-0: Alertmanager and Rules Configuration APIAWS Canada - prod-ca-east-0: AlertmanagerAWS Germany - prod-eu-west-2: Alertmanager and Rules Configuration APIAWS Germany - prod-eu-west-2: AlertmanagerAWS UAE - prod-me-central-1: Alertmanager and Rules Configuration APIAWS UAE - prod-me-central-1: Alertmanager
    Timeline · 3 updates
    • investigating · Jun 09, 2026, 11:11 PM UTC

      We are currently investigating an issue affecting data source-managed alerting management functionality in Grafana Cloud. Customers may experience problems viewing, creating, updating, or managing alerts through Grafana when using data source-managed alerting. This issue is limited to alert management functionality within Grafana. Alert evaluation and backend alerting services continue to operate normally. Direct alerting APIs for Mimir and Loki remain fully operational and are unaffected. Grafana-managed alerting is not impacted. We identified this issue at approximately 20:45 UTC and are actively working on a resolution. We will provide additional updates as more information becomes available. Workaround: Customers can continue to use the direct Mimir and Loki alerting APIs while we work to restore normal functionality.

    • monitoring · Jun 10, 2026, 10:57 AM UTC

      Our team has implemented a fix and we are currently monitoring the results of this.

    • resolved · Jun 10, 2026, 01:11 PM UTC

      We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

    Latest: We continue to observe a continued period of recovery. At this time, we are considering this issue resolved. No further updates.

  4. Resolved 9h 44m
    Started Jun 08, 2026, 10:45 AM UTC · Resolved Jun 08, 2026, 08:30 PM UTC
    GCP Belgium - prod-eu-west-0: Alertmanager and Rules Configuration APIGCP US Central - prod-us-central-0: Alertmanager and Rules Configuration API
    Timeline · 8 updates
    • investigating · Jun 08, 2026, 10:45 AM UTC

      We are experiencing access issues in IRM as there are elevated 500 API responses in prod-us-central-0.

    • investigating · Jun 08, 2026, 10:47 AM UTC

      We are continuing to investigate this issue.

    • identified · Jun 08, 2026, 11:15 AM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Jun 08, 2026, 12:26 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Jun 08, 2026, 01:14 PM UTC

      The degraded performance is about labels, and we have seen this degradation in more regions.

    • identified · Jun 08, 2026, 03:21 PM UTC

      We are continuing to work on a fix for this. To further clarify, this issue is not about accessing IRM or alert ingestion/notification/delivery, but rather with handling labels.

    • monitoring · Jun 08, 2026, 05:11 PM UTC

      We've released a fix to the IRM app that should restore service for affected customers with issues related to labels. Thanks for your patience while investigating. We're continuing to monitor as we confirm the resolution in place.

    • resolved · Jun 08, 2026, 08:30 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 5d 18h
    Started Jun 07, 2026, 01:39 AM UTC · Resolved Jun 12, 2026, 07:52 PM UTC
    Azure Netherlands - prod-eu-west-3: Ingestion
    Timeline · 7 updates
    • investigating · Jun 07, 2026, 01:39 AM UTC

      From 00:20:00 to 00:27:00 and again 00:32:00 to 00:38:00 there were brief spikes in rule evaluation failures. Engineers are investigating.

    • investigating · Jun 07, 2026, 02:46 AM UTC

      Intermittent spikes in rule evaluations continuing.

    • investigating · Jun 07, 2026, 03:50 AM UTC

      We are continuing to investigate this issue.

    • investigating · Jun 07, 2026, 06:00 AM UTC

      We’re making ongoing progress on the investigation alongside our upstream provider.

    • monitoring · Jun 07, 2026, 11:00 AM UTC

      The incident has been mitigated, and services are operating normally. We are currently monitor the service to ensure full stability.

    • monitoring · Jun 08, 2026, 09:36 PM UTC

      The incident has been mitigated, and services are operating normally. We continue to monitor the service to ensure full stability.

    • resolved · Jun 12, 2026, 07:52 PM UTC

      This incident has been resolved. Thank you for your patience.

    Latest: This incident has been resolved. Thank you for your patience.

See the full Grafana outage history

57 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Grafana outage history →

Or sign up free to get alerts when Grafana breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 61 incidents View full outage history →