Grafana Cloud Outage History

This incident has been resolved.

Things are no longer degraded. We are currently monitoring the issue

We are continuing to investigate this issue.

We are currently investigating an issue impacting Cloud Integrations in prod-eu-west-3. We will provide another update when we have more to share.

This incident has been resolved.

A fix as been implemented and Hosted Grafana instances are back to normal levels. We will continue to monitor the issue.

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

Starting at approximately 12:37 UTC, a some Hosted Grafana instances across multiple regions have been experiencing availability issues. Our team has identified the root cause and a fix is currently in progress. Affected instances will recover automatically once the fix has been applied. No action is required on your end. We will provide further updates as they become available and apologize for any disruption this may cause.

This incident has been resolved.

Remediation measures have been applied, and we are monitoring the recovery.

The root cause of the issue has been indentified and we are working on the remediation steps.

Since approximately 20:30 UTC on October 20, we have observed an increase in alert rule evaluation errors affecting rules that query Grafana Cloud Prometheus (Mimir) data sources in Cluster AWS Germany. Our engineering team is actively investigating and working on remediation.

This incident has been resolved.

We are seeing errors in Frontend o11y again. We are continuing to investigate and monitor the impacted services.

Between 06:15 and 12:15 UTC, Grafana Cloud Frontend Observability in GCP UK (prod-gb-south-0) experienced errors accepting incoming telemetry data. This has been resolved and Frontend Observability is operating normally in this region. We are continuing to investigate and monitor the remaining impacted services.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

As of  06:30 UTC, we became aware of to an issue with Grafana Cloud unavailibity in the prod-gb-south-0 region. Engineering is actively engaged and assessing the issue. We will provide updates accordingly.

Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.

SMS delivery to Bangladesh has been restored. SMS delivery to Thailand is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.

SMS delivery to Austrian numbers has been restored. SMS delivery to Thailand and Bangladesh is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.

We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.

We are continuing working on a resolution, and will provide another update as soon as we have more information to share. In the meantime we recommend, affected users to configure mobile push or phone calls as notifications.

This issue is also impacting numbers from Thailand and Bangladesh. The title of this status page has been updated to reflect this. Users should configure mobile push or phone calls as notifications. We are working on a resolution, and we will provide another update as soon as we have more information to share.

The issue has been identified. We are working on a resolution, but do not have an ETA at this time. We will provide another update as soon as we have more information to share. Users should configure mobile push or phone calls as notifications.

We are currently investigating an issue impacting all SMS attempts to Austria for IRM. All SMS attempts to Austria for IRM are currently blocked. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or phone calls as notifications.

Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.

Phone call notifications to numbers in Russia and Kazakhstan are still blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

Phone call notifications to numbers in Russia and Kazakhstan are currently blocked. We are working to resolve the issue. As SMS support is limited in these countries, we recommend using mobile push notifications as an alternative. We do not currently have an estimated resolution time. We will provide further updates as more information becomes available.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We’re currently investigating an issue affecting metrics reads and rule evaluations in mimir-prod-66. Our team is actively working to identify the cause. Thank you for your patience.

This incident has been resolved.

Things are starting to stabilize as we continue to work on a mitigation.

We are continuing to work on a fix for this issue. Next update by 16:30 UTC

We observed some spikes in latency starting at approximately 12:50 UTC. We are working on a resolution. Next update by 15:30 UTC

This incident has been resolved.

The fix has been implemented, and we are monitoring the results.

We have noticed improvements across services. We will now be applying a more permanent fix. Impacted users may experience a disruption in the auth-api service of up to 15min while we apply a DB patch that will improve performance.

The issue has been identified, and we have applied mitigations on our end. We are currently observing the progress.

We are investigating increased authentication errors affecting Grafana Cloud in the prod-us-west-0 region. Customers may experience intermittent failures for requests that require authentication. Our engineering team has identified database performance degradation affecting the authentication service and is investigating the underlying cause. We will provide another update as more information becomes available.

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

We have put some mitigations in place which seem to have helped with the errors. We continue to monitor the results.

We are continuing to investigate this issue.

A small number of customers with stacks in prod-us-central-4 are receiving "forbidden" errors when querying Prometheus data sources. We are investigating and will provide an update soon.

Incident started around 15:51 UTC, resolved around 18:11 UTC. After investigation, we found that no customer queries were affected; only our internal metrics systems were impacted.

We are investigating reduced query throughput for some data source plugins in multiple regions. Some queries may fail or be slow.

Between 10:03 and 12:37 UTC, Grafana Cloud Logs in Azure Netherlands experienced elevated write latency and intermittent errors due to a cloud provider dependency issue. Service has fully recovered and is operating normally. Thank you for your patience.

We have identified the issue as related to a cloud provider dependency affecting the write path for Grafana Cloud Logs in Azure Netherlands. Latency has recovered to normal levels. We are continuing to monitor before fully closing this incident.

We are continuing to investigate this issue. Next update by 11:30 UTC.

We are investigating elevated write latency and intermittent errors affecting Grafana Cloud Logs in Azure Netherlands. Customers may see delayed log ingestion and some failed write requests. Next update by 11:30 UTC.

Between 12:09 and 15:39 UTC on September 30, Grafana Cloud Logs in AWS US East (VA) experienced intermittent elevated latency and a small number of failed requests. Impact has returned to normal levels and all services are operating as expected. Thank you for your patience.

An additional brief recurrence affected a small number of requests after our mitigation was deployed, though impact was smaller than earlier today. We continue to monitor and investigate a related, longer-running pattern. Next update by 15:40 UTC.

We have identified a contributing factor to the elevated latency and are rolling out a mitigation to increase write capacity in AWS US East (VA). We continue to investigate a related, longer-running pattern. Next update by 14:40 UTC.

We are continuing to investigate this issue.

We are investigating elevated latency and a small number of failed requests for Grafana Cloud Logs in AWS US East (VA). Some customers writing logs to this region may see delayed ingestion or occasional write errors. We are actively investigating and will share more as we learn it. Next update by 13:38 UTC.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Since approximately 00:19Z there has been an increase in errors returning metrics from Azure's germanywestcentral. We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Some customers may see a sudden spike in reported Kubernetes Observability usage even if they haven't activated the product. We are investigating the root cause, and will ensure the amount is corrected before any usage is invoiced.

Between September 9 and September 15, 2026, some browser checks in Synthetic Monitoring experienced longer than usual execution times, with impact varying by location. This has been resolved and check execution times have returned to baseline. Thank you for your patience.

A fix has been deployed and CPU throttling is returning to normal. Check execution times should return to baseline shortly. We will continue monitoring recovery. Next update by 11:56 UTC.

A fix has been merged and is now being rolled out across affected locations. We are monitoring deployment progress. Next update by 11:49 UTC.

Since September 9, 2026, some browser checks in Synthetic Monitoring may take longer to complete than usual, with impact varying by location. We have identified the cause and are actively working on a fix. Next update by 10:49 UTC.

Between 15:31 and 20:43 UTC on September 14, 2026 (approximately 5 hours 12 minutes), some customers in GCP US Central (prod-us-central-0) may have experienced intermittent errors or delays when writing metrics. This has been fully resolved and all services are operating normally.

Between 03:30 UTC on September 14, 2026 and 10:50 UTC on September 17, 2026 (approximately 3 days), customers managing cloud provider integrations in GCP US Central may have experienced elevated latency when creating, viewing, or removing integrations. This has been fully resolved and all services are operating normally.

Between approximately 23:00 UTC on September 12, 2026 and 09:12 UTC on September 14, 2026, some Grafana Cloud Logs customers in AWS Sweden (prod-eu-north-0) may have intermittently experienced errors when submitting configuration changes through the Cloud Portal. This has been resolved, and configuration change requests are being accepted normally.

This incident has been resolved.

A fix has been implemented and we have been seeing recovery to the affected region. We will continue to monitor.

We are investigating elevated database load affecting infrastructure supporting a subset of Grafana Cloud instances in the AWS Germany region (prod-eu-west-4). Affected users may experience slow responses when accessing Grafana. We will provide an update as more information becomes available.

This incident has been resolved.

Some geomap tiles are displaying the “api key required". The issue has been identified, and our team is working on a fix. As a workaround, you can open the Geomap panel, navigate to the Map layers section, and change the Basemap layer from CARTO, or "Default base layer," to OpenStreetMap. The watermark should disappear immediately. Alternatively, if you would prefer to retain a dark-styled map similar to the current CARTO appearance, you can select MapLibre as the basemap and configure the URL as: https://tiles.openfreemap.org/styles/dark This option also renders without the watermark, does not require an API key, and provides a visual style similar to the dark CARTO basemap.

This incident has been resolved.

We have observed latency return to normal levels, and we will continue to monitor this incident.

We are currently investigating an issue causing high latency for deployments in the prod-us-east-2 cluster.

The US Central region is fully recovered now and the issue is now resolved.

The underlying cloud provider issue is not yet fully resolved, but our systems have recovered and affected Grafana Cloud stacks are loading normally again. Some customers may still see brief intermittent slowness. We are continuing to monitor until our provider confirms resolution.

We’re currently investigating an issue affecting the us central region due to ongoing cloud provider incident. Multiple components impacted. Our team is actively working on this. Thank you for your patience.

The issue has been mitigated and there's a code fix pending.

We’re currently investigating an issue affecting alert rule creation, deletion, and updates in prod-us-east-2. Our team is actively working to identify the cause. Thank you for your patience.

This incident has been resolved.

Tempo recovered.

Cluster Metrics are healthy for the last 15 minutes

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