Skip to content

Outage tracker / Grafana Cloud

Is Grafana Cloud down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Grafana Cloud from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Grafana Cloud (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East156 msOperational
US-West565 msOperational
Europe476 msOperational
Asia-Pacific233 msOperational
US-Central426 msOperational
Canada117 msOperational
UK446 msOperational
Southeast Asia816 msOperational
Australia550 msOperational
South America688 msOperational
their status pagetheir claim, not our reading

Grafana Cloud reports: Minor incident (“Partially Degraded Service”)

from Grafana Cloud's own status page, checked Sep 4, 2026, 8:20 PM UTC
Grafana Cloud's status page reports Partially Degraded Service. Our probes are currently reaching Grafana Cloud successfully with normal latency. RealUptime's independent checks are currently succeeding from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show what we measured, not what they report: differences can mean a partial or user-specific issue that a simple reachability check won't catch. Read both before you draw a conclusion.

Grafana Cloud's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • AWS Australia - prod-ap-southeast-2Operational
  • AWS Australia - prod-ap-southeast-2Operational
  • AWS Australia - prod-ap-southeast-2Operational
  • AWS Australia - prod-ap-southeast-2: QueryingOperational
  • AWS Australia - prod-ap-southeast-2: QueryingOperational
  • AWS Australia - prod-ap-southeast-2: Rule EvaluationOperational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1Under maintenance
  • AWS Australia - prod-au-southeast-1: APIOperational
  • AWS Japan - prod-ap-northeast-0Operational
  • GCk6 AppOperational
  • Grafana.comOperational
  • AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration APIOperational
  • AWS Australia - prod-ap-southeast-2: IngestionOperational
  • AWS Australia - prod-ap-southeast-2: IngestionOperational
  • AWS Australia - prod-au-southeast-1: Public ProbesOperational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS Brazil - prod-sa-east-1Operational
  • AWS India - prod-ap-south-1Operational
  • Cloud Test RunsOperational
  • Support TicketsOperational
  • AWS Australia - prod-ap-southeast-2: AlertmanagerOperational
  • AWS Australia - prod-ap-southeast-2: Metrics GeneratorOperational
  • AWS Brazil - prod-sa-east-1: APIOperational
  • AWS Brazil - prod-sa-east-1: QueryingOperational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Singapore - prod-ap-southeast-1Operational
  • Cloud Output Test RunsOperational
  • AWS Brazil - prod-sa-east-1: IngestionOperational
  • AWS Brazil - prod-sa-east-1: Public ProbesOperational
  • AWS Brazil - prod-sa-east-1: QueryingOperational
  • AWS Brazil - prod-sa-east-1: Rule EvaluationOperational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Germany - prod-eu-west-2Operational
  • Result AnalysisOperational
  • AWS Australia - prod-ap-southeast-2Operational
  • AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIOperational
  • AWS Brazil - prod-sa-east-1: IngestionOperational
  • AWS Canada - prod-ca-east-0: APIOperational
  • AWS Canada - prod-ca-east-0: QueryingOperational
  • AWS Germany - prod-eu-west-4Operational
  • AWS Germany - prod-eu-west-4Operational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS UAE - prod-me-central-1Operational
  • Test SchedulingOperational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Brazil - prod-sa-east-1: AlertmanagerOperational
  • AWS Brazil - prod-sa-east-1: Metrics GeneratorOperational
  • AWS Canada - prod-ca-east-0: IngestionOperational
  • AWS Canada - prod-ca-east-0: Public ProbesOperational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • Private Load ZonesOperational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0: QueryingOperational
  • AWS Canada - prod-ca-east-0: Rule EvaluationOperational
  • AWS Germany - prod-eu-west-2: APIOperational
  • AWS Germany - prod-eu-west-2: QueryingOperational
  • AWS Ireland - prod-eu-west-6Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Singapore - prod-ap-southeast-1Operational
  • AWS Singapore - prod-ap-southeast-1Operational
  • AWS Singapore - prod-ap-southeast-1Operational
  • AWS Singapore - prod-ap-southeast-1Operational
  • Cloud logsOperational
  • AWS Singapore - prod-ap-southeast-1Operational

These are Grafana Cloud's components, named and scored by Grafana Cloud. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Grafana Cloud's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Grafana Cloud response time, by region

US-East
364msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 524ms2026-08-23 UTC: p95 556ms2026-08-24 UTC: p95 727ms2026-08-25 UTC: p95 759ms2026-08-26 UTC: p95 413ms2026-08-27 UTC: p95 536ms2026-08-28 UTC: p95 725ms2026-08-29 UTC: p95 728ms2026-08-30 UTC: p95 562ms2026-08-31 UTC: p95 503ms2026-09-01 UTC: p95 565ms2026-09-02 UTC: p95 664ms2026-09-03 UTC: p95 697ms2026-09-04 UTC: p95 326ms2026-09-05 UTC: p95 364ms
Aug 7Aug 21Sep 5
US-West
666msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 552ms2026-08-23 UTC: p95 559ms2026-08-24 UTC: p95 619ms2026-08-25 UTC: p95 549ms2026-08-26 UTC: p95 485ms2026-08-27 UTC: p95 689ms2026-08-28 UTC: p95 639ms2026-08-29 UTC: p95 925ms2026-08-30 UTC: p95 868ms2026-08-31 UTC: p95 800ms2026-09-01 UTC: p95 658ms2026-09-02 UTC: p95 574ms2026-09-03 UTC: p95 534ms2026-09-04 UTC: p95 490ms2026-09-05 UTC: p95 666ms
Aug 7Aug 21Sep 5
Europe
627msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 217ms2026-08-23 UTC: p95 611ms2026-08-24 UTC: p95 892ms2026-08-25 UTC: p95 797ms2026-08-26 UTC: p95 681ms2026-08-27 UTC: p95 675ms2026-08-28 UTC: p95 651ms2026-08-29 UTC: p95 633ms2026-08-30 UTC: p95 746ms2026-08-31 UTC: p95 650ms2026-09-01 UTC: p95 618ms2026-09-02 UTC: p95 697ms2026-09-03 UTC: p95 701ms2026-09-04 UTC: p95 626ms2026-09-05 UTC: p95 627ms
Aug 7Aug 21Sep 5
Asia-Pacific
554msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 600ms2026-08-23 UTC: p95 887ms2026-08-24 UTC: p95 861ms2026-08-25 UTC: p95 1.1s2026-08-26 UTC: p95 1.0s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 899ms2026-08-29 UTC: p95 911ms2026-08-30 UTC: p95 875ms2026-08-31 UTC: p95 831ms2026-09-01 UTC: p95 1.0s2026-09-02 UTC: p95 1.1s2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 813ms2026-09-05 UTC: p95 554ms
Aug 7Aug 21Sep 5
US-Central
716msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 643ms2026-09-04 UTC: p95 720ms2026-09-05 UTC: p95 716ms
Aug 7Aug 21Sep 5
Canada
332msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 512ms2026-09-04 UTC: p95 323ms2026-09-05 UTC: p95 332ms
Aug 7Aug 21Sep 5
UK
529msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 553ms2026-09-04 UTC: p95 731ms2026-09-05 UTC: p95 529ms
Aug 7Aug 21Sep 5
Southeast Asia
857msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 910ms2026-09-05 UTC: p95 857ms
Aug 7Aug 21Sep 5
Australia
754msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 999ms2026-09-05 UTC: p95 754ms
Aug 7Aug 21Sep 5
South America
815msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 815ms
Aug 7Aug 21Sep 5

Is it Grafana Cloud, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Grafana Cloud -- it cannot diagnose Grafana Cloud's own systems.

What we measured, function by function

Grafana Cloud answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 156msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Grafana Cloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 565msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Grafana Cloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 426msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Grafana Cloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 117msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Grafana Cloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 688msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Grafana Cloud normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 476msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Grafana Cloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 446msstatus code: 200checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Grafana Cloud normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 233msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Grafana Cloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 816msstatus code: 200checked: Sep 5, 2026, 1:47 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Grafana Cloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 550msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Grafana Cloud normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Grafana Cloud, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Grafana Cloud yet, which is not evidence that nothing is wrong.

Recent outages

Degradation of Hosted Grafana in US Central Region, 3h 39mdeclared on their status page2026-09-04
US Central Region Instability, 6h 15mdeclared on their status page2026-09-04
Alert rule creation, deletion, and update degradation in prod-us-east-2, 2h 56mdeclared on their status page2026-09-04
Tempo and Mimir Read and Write Failures, 2h 42mdeclared on their status page2026-09-03
High Latency in prod-ap-south-1, 3h 17mdeclared on their status page2026-09-03
Elevated Latency in Grafana Cloud Logs (prod-ap-south-1), 1mdeclared on their status page2026-09-02
Investigating issues in US Central (prod-us-central-0, prod-us-central-5), 4h 54mdeclared on their status page2026-09-01
Partial Logs Write Outage, 1h 29mdeclared on their status page2026-08-28

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Grafana Cloud since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Grafana Cloud covering any window you pick, with our measurements and Grafana Cloud's own claim at the time, side by side.

Full availability history for Grafana Cloud: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Grafana Cloud, and again when they can reach it again. That is our own measurement from ten regions, not Grafana Cloud's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Grafana Cloud uptime measured by RealUptimeLive, from this page's own readings.
[![Grafana Cloud uptime measured by RealUptime](https://realuptime.io/outages/grafana-cloud/badge.svg?days=30)](https://realuptime.io/outages/grafana-cloud)
<a href="https://realuptime.io/outages/grafana-cloud"><img src="https://realuptime.io/outages/grafana-cloud/badge.svg?days=30" alt="Grafana Cloud uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Grafana Cloud's SLA implies, from our measurement

At or above your target

We measured none of downtime for Grafana Cloud over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Grafana Cloud's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://grafana.com/api/orgs/grafana
secondary
https://grafana.com/
secondary
https://status.grafana.com/api/v2/status.json
RealUptime is not affiliated with Grafana Cloud; the name identifies what we measured, and nothing here speaks for Grafana Cloud's own team. We send a single web request to Grafana Cloud from 10 regions on our own schedule and time the response. We do not see inside Grafana Cloud's systems, do not use an account or real transaction, and are not the same signal Grafana Cloud's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Grafana Cloud is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.