Grafana Cloud status

Scheduled maintenance

• Scheduled Database Maintenance – Temporary Grafana Instance Unavailability · Oct 16, 2026, 19:15 UTC · scheduled, maintenance impact
• Scheduled Database Maintenance – Temporary Grafana Instance Unavailability · Oct 16, 2026, 19:16 UTC · scheduled, maintenance impact

Components

What a degraded performance status means, and how much downtime an SLA allows: the uptime calculator.

Recent Grafana Cloud incidents

• Elevated query errors for Grafana Cloud Metrics in prod-us-east-3 · Nov 11, 2026, 20:21 UTC · resolved, minor impact, lasted 4 h 14 min

  This incident has been resolved.

• Degraded performance for Grafana Cloud Metrics in prod-us-central-7 · Nov 11, 2026, 20:37 UTC · resolved, major impact, lasted 1 h 36 min

  Increased latency on a cloud provider database resulted in a 50m write and rule evaluation outage, starting about 2020 UTC. Metrics rule evaluations were last to recover, around 2110 UTC.

• Mimir query unexpected response with status code 500 · Nov 10, 2026, 03:38 UTC · resolved, minor impact, lasted 8 h 32 min

  From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.

• Cloud Logs writes - Elevated latency and error rates in prod-eu-central-0 · Nov 10, 2026, 08:03 UTC · resolved, lasted 17 min

  We're observing a continued period of recovery and will mark this as resolved.

• October usage report visualization issue · Nov 3, 2026, 22:00 UTC · resolved, minor impact, lasted 75 h 17 min

  This incident has been resolved.

• Synthetic Monitoring — Jakarta Public Probe Degradation · Nov 6, 2026, 10:12 UTC · resolved, lasted 0 min

  Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks: <1% failure…

• IRM Unable to Voice Call Brazil Numbers · Nov 2, 2026, 00:36 UTC · resolved, major impact, lasted 56 h 9 min

  Brazil calls recovered at about 13:00 UTC on 3 November. At this point, we are marking the incident as resolved.

• GitHub returning 403 for all Git Sync repositories · Nov 4, 2026, 03:02 UTC · resolved, minor impact, lasted 1 h 58 min

  The fix has been deployed to all production clusters and we are observing a continued period of stability. At this time, we are marking the incident as resolved.

• Increased query latency for Logs in GCP US Central (prod-us-central-0) · Nov 3, 2026, 13:54 UTC · resolved, minor impact, lasted 1 h 31 min

  This incident has been resolved. Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. Some Metrics alert and recording rule evaluations in the same region were also delayed between 12:11 and 12:44 UTC. Both issues have been…

• Elevated Request Errors for Grafana Across Multiple Regions · Nov 3, 2026, 12:40 UTC · resolved, minor impact, lasted 1 h 1 min

  Between approximately 12:10 UTC and 13:22 UTC on 3 November (about 1 hour 12 minutes), Grafana across multiple Grafana Cloud regions experienced elevated request errors, causing slow-loading or failing dashboards and Explore queries. The issue has been resolved and service has…

• Grafana Cloud: k6 timeouts · Nov 2, 2026, 16:04 UTC · resolved, lasted 0 min

  We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.

• Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1) · Nov 2, 2026, 09:20 UTC · resolved, minor impact, lasted 1 h 48 min

  Between approximately 08:00 and 09:40 UTC (about 1 hour 40 minutes), some customers in AWS Australia (prod-au-southeast-1) experienced intermittent failures when evaluating alert and recording rules, which may have caused missed or delayed alert notifications and gaps in…

• Missing Metrics for Some Synthetic Monitoring Checks using the Montreal, North Virginia, and North California public probes · Nov 2, 2026, 08:00 UTC · resolved, lasted 0 min

  Between approximately 08:09 and 09:10 UTC on 2 November (about 1 hour 11 minutes), a subset of Synthetic Monitoring checks running from the Montreal, North Virginia, and North California public probe locations experienced missing metrics, which may have appeared as gaps in…

• Degraded Cloud Integrations · Oct 27, 2026, 15:05 UTC · resolved, minor impact, lasted 4 h 42 min

  This incident has been resolved.

• Frontend Observability Outage in prod-eu-west-2 · Oct 27, 2026, 15:56 UTC · resolved, critical impact, lasted 28 min

  This incident has been resolved.

Source: Grafana Cloud, Grafana Cloud’s public status page, read Nov 15, 2026, 08:06 UTC. Uptimely is not affiliated with Grafana Cloud; incident text is Grafana Cloud’s own.

Status of similar services

• GitHub status
• Bitbucket status
• npm status
• Docker status
• Twilio status
• Datadog status
• Sentry status
• Supabase status
• PlanetScale status
• MongoDB Atlas status
• Elastic Cloud status
• Snowflake status
• CircleCI status
• Mailgun status
• Resend status
• Clerk status
• Segment status
• Cloudinary status

Every service status we track

Verified 2026-11-08 by the Uptimely team.