Skip to content

Outage tracker / Grafana Cloud

Is Grafana Cloud down?

I'm having a problem

Vendor reports an incidentWhat Grafana Cloud reports

Grafana Cloud reports an incident on its status page: October usage report visualization issue.

Impact: minor. Since 2026-11-03 22:00 UTC.

Latest update, 2026-11-04 22:11 UTC: We are still working to backfill the correct data. Note that this did not affect billing, and is only a visualization issue.

Grafana Cloud's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Grafana Cloud pass from all 10 regions we check.

As of Nov 5, 2026, 3:03 PM UTC, RealUptime's checks of Grafana Cloud passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:03 PM UTC
US-East132 msChecks passing
US-West1000 msChecks passing
Europe590 msChecks passing
Asia-Pacific1110 msChecks passing
US-Central319 msChecks passing
Canada463 msChecks passing
UK891 msChecks passing
Southeast Asia310 msChecks passing
Australia1832 msChecks passing
South America1022 msChecks passing
their status pagetheir claim, not our reading

Grafana Cloud reports: Minor incident (“Minor Service Outage”)

from Grafana Cloud's own status page, checked Nov 5, 2026, 1:57 PM UTC

Grafana Cloud reports an active incident: October usage report visualization issue (minor incident, since Nov 3, 2026, 10:00 PM UTC)

Grafana Cloud's status page reports Minor Service Outage. Our checks of Grafana Cloud currently pass with normal latency. Our checks currently pass 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 the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Grafana Cloud's own component breakdown, as they publish it

  • AWS Australia - prod-ap-southeast-2: QueryingOperational
  • AWS Australia - prod-ap-southeast-2: QueryingOperational
  • 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-1Operational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1Operational
  • AWS Australia - prod-au-southeast-1: APIOperational
  • AWS Australia - prod-au-southeast-1: Rule EvaluationOperational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • GCk6 AppOperational
  • Grafana.comOperational
  • AWS Australia - prod-ap-southeast-2: IngestionOperational
  • AWS Australia - prod-ap-southeast-2: IngestionOperational
  • AWS Australia - prod-au-southeast-1: Alertmanager and Rules Configuration APIOperational
  • AWS Australia - prod-au-southeast-1: Public ProbesOperational
  • AWS Australia - prod-au-southeast-2Operational
  • 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: Metrics GeneratorOperational
  • AWS Australia - prod-au-southeast-1: AlertmanagerOperational
  • AWS Brazil - prod-sa-east-1Operational
  • 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 Singapore - prod-ap-southeast-1Operational
  • Cloud Output Test RunsOperational
  • AWS Australia - prod-ap-southeast-2Operational
  • 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 Canada prod-ca-central-1Operational
  • 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-au-southeast-1Operational
  • AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIOperational
  • AWS Brazil - prod-sa-east-1: IngestionOperational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0: APIOperational
  • AWS Canada - prod-ca-east-0: QueryingOperational
  • 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 India - prod-ap-south-1Operational
  • AWS India - prod-ap-south-1Operational
  • Test SchedulingOperational
  • AWS Brazil - prod-sa-east-1: AlertmanagerOperational
  • AWS Brazil - prod-sa-east-1: Metrics GeneratorOperational
  • AWS Canada - prod-ca-east-0Operational
  • AWS Canada - prod-ca-east-0: IngestionOperational
  • AWS Canada - prod-ca-east-0: Public ProbesOperational
  • AWS Germany - prod-eu-west-2Operational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Indonesia - prod-ap-southeast-2Operational
  • AWS Ireland - prod-eu-west-6Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • AWS Japan - prod-ap-northeast-0Operational
  • Private Load ZonesOperational
  • 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 Germany - prod-eu-west-4Operational
  • AWS Ireland - prod-eu-west-6Operational
  • AWS Ireland - prod-eu-west-6Operational
  • AWS Ireland - prod-eu-west-6Operational
  • 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 Switzerland - prod-eu-central-0Operational
  • Cloud logsOperational

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
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 542ms2026-10-08 UTC: p95 465ms2026-10-09 UTC: p95 531ms2026-10-10 UTC: p95 648ms2026-10-11 UTC: p95 570ms2026-10-12 UTC: p95 531ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 652ms2026-10-15 UTC: p95 739ms2026-10-16 UTC: p95 562ms2026-10-17 UTC: p95 936ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 949ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 287ms2026-10-25 UTC: p95 435ms2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.2s2026-10-28 UTC: p95 869ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
1.7sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 498ms2026-10-08 UTC: p95 511ms2026-10-09 UTC: p95 586ms2026-10-10 UTC: p95 604ms2026-10-11 UTC: p95 623ms2026-10-12 UTC: p95 695ms2026-10-13 UTC: p95 496ms2026-10-14 UTC: p95 615ms2026-10-15 UTC: p95 695ms2026-10-16 UTC: p95 588ms2026-10-17 UTC: p95 842ms2026-10-18 UTC: p95 960ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 616ms2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 969ms2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Europe
1.1sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 590ms2026-10-08 UTC: p95 511ms2026-10-09 UTC: p95 451ms2026-10-10 UTC: p95 387ms2026-10-11 UTC: p95 351ms2026-10-12 UTC: p95 538ms2026-10-13 UTC: p95 597ms2026-10-14 UTC: p95 392ms2026-10-15 UTC: p95 588ms2026-10-16 UTC: p95 404ms2026-10-17 UTC: p95 528ms2026-10-18 UTC: p95 800ms2026-10-19 UTC: p95 954ms2026-10-20 UTC: p95 660ms2026-10-21 UTC: p95 629ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 961ms2026-10-24 UTC: p95 919ms2026-10-25 UTC: p95 991ms2026-10-26 UTC: p95 704ms2026-10-27 UTC: p95 802ms2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 840ms2026-10-31 UTC: p95 974ms2026-11-01 UTC: p95 918ms2026-11-02 UTC: p95 853ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Asia-Pacific
1.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 718ms2026-10-08 UTC: p95 773ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 981ms2026-10-11 UTC: p95 909ms2026-10-12 UTC: p95 915ms2026-10-13 UTC: p95 652ms2026-10-14 UTC: p95 788ms2026-10-15 UTC: p95 788ms2026-10-16 UTC: p95 709ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 943ms2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 3.2s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-Central
1.4sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 400ms2026-10-08 UTC: p95 385ms2026-10-09 UTC: p95 522ms2026-10-10 UTC: p95 487ms2026-10-11 UTC: p95 488ms2026-10-12 UTC: p95 520ms2026-10-13 UTC: p95 524ms2026-10-14 UTC: p95 720ms2026-10-15 UTC: p95 675ms2026-10-16 UTC: p95 539ms2026-10-17 UTC: p95 645ms2026-10-18 UTC: p95 513ms2026-10-19 UTC: p95 518ms2026-10-20 UTC: p95 915ms2026-10-21 UTC: p95 849ms2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 286ms2026-10-25 UTC: p95 521ms2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 535ms2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 863ms2026-11-03 UTC: p95 932ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Canada
1.1sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 245ms2026-10-08 UTC: p95 274ms2026-10-09 UTC: p95 571ms2026-10-10 UTC: p95 670ms2026-10-11 UTC: p95 578ms2026-10-12 UTC: p95 491ms2026-10-13 UTC: p95 551ms2026-10-14 UTC: p95 649ms2026-10-15 UTC: p95 337ms2026-10-16 UTC: p95 454ms2026-10-17 UTC: p95 680ms2026-10-18 UTC: p95 680ms2026-10-19 UTC: p95 821ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 546ms2026-10-22 UTC: p95 648ms2026-10-23 UTC: p95 695ms2026-10-24 UTC: p95 394ms2026-10-25 UTC: p95 578ms2026-10-26 UTC: p95 543ms2026-10-27 UTC: p95 730ms2026-10-28 UTC: p95 992ms2026-10-29 UTC: p95 568ms2026-10-30 UTC: p95 960ms2026-10-31 UTC: p95 957ms2026-11-01 UTC: p95 1.0s2026-11-02 UTC: p95 725ms2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 944ms2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
UK
985msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 695ms2026-10-08 UTC: p95 659ms2026-10-09 UTC: p95 519ms2026-10-10 UTC: p95 469ms2026-10-11 UTC: p95 401ms2026-10-12 UTC: p95 446ms2026-10-13 UTC: p95 343ms2026-10-14 UTC: p95 401ms2026-10-15 UTC: p95 465ms2026-10-16 UTC: p95 496ms2026-10-17 UTC: p95 417ms2026-10-18 UTC: p95 623ms2026-10-19 UTC: p95 793ms2026-10-20 UTC: p95 546ms2026-10-21 UTC: p95 637ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 827ms2026-10-24 UTC: p95 467ms2026-10-25 UTC: p95 474ms2026-10-26 UTC: p95 448ms2026-10-27 UTC: p95 465ms2026-10-28 UTC: p95 671ms2026-10-29 UTC: p95 884ms2026-10-30 UTC: p95 864ms2026-10-31 UTC: p95 690ms2026-11-01 UTC: p95 731ms2026-11-02 UTC: p95 691ms2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 890ms2026-11-05 UTC: p95 985ms
Oct 7Oct 21Nov 5
Southeast Asia
1.3sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 743ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 941ms2026-10-13 UTC: p95 755ms2026-10-14 UTC: p95 850ms2026-10-15 UTC: p95 956ms2026-10-16 UTC: p95 681ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 553ms2026-10-08 UTC: p95 919ms2026-10-09 UTC: p95 720ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 948ms2026-10-12 UTC: p95 956ms2026-10-13 UTC: p95 668ms2026-10-14 UTC: p95 708ms2026-10-15 UTC: p95 683ms2026-10-16 UTC: p95 814ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 874ms2026-10-22 UTC: p95 847ms2026-10-23 UTC: p95 2.5s2026-10-24 UTC: p95 2.9s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 631ms2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
1.2sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 855ms2026-10-08 UTC: p95 853ms2026-10-09 UTC: p95 917ms2026-10-10 UTC: p95 880ms2026-10-11 UTC: p95 834ms2026-10-12 UTC: p95 776ms2026-10-13 UTC: p95 815ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 840ms2026-10-16 UTC: p95 624ms2026-10-17 UTC: p95 2.0s2026-10-18 UTC: p95 2.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 7.9s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 1.6s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 885ms2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on Grafana Cloud

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Dashboards catalogUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • DocumentationUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Grafana Cloud reports an incident on its status page, and again when it reports it resolved.

Get an email when Grafana Cloud reports an incident

Email me when Grafana Cloud reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Grafana Cloud's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 132msstatus code: 200checked: Nov 5, 2026, 2:54 PM 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
      Checks passinglatency: 1000msstatus code: 200checked: Nov 5, 2026, 3:03 PM 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
      Checks passinglatency: 319msstatus code: 200checked: Nov 5, 2026, 2:52 PM 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
      Checks passinglatency: 463msstatus code: 200checked: Nov 5, 2026, 2:52 PM 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
    Checks passinglatency: 1022msstatus code: 200checked: Nov 5, 2026, 2:54 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 590msstatus code: 200checked: Nov 5, 2026, 2:55 PM 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
      Checks passinglatency: 891msstatus code: 200checked: Nov 5, 2026, 2:53 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1110msstatus code: 200checked: Nov 5, 2026, 3:00 PM 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
      Checks passinglatency: 310msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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
      Checks passinglatency: 1832msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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 probe events

GitHub returning 403 for all Git Sync repositories, 1h 58mdeclared on their status page2026-11-04
October usage report visualization issuedeclared on their status page2026-11-03
Increased query latency for Logs in GCP US Central (prod-us-central-0), 1h 31mdeclared on their status page2026-11-03
Elevated Request Errors for Grafana Across Multiple Regions, 1h 1mdeclared on their status page2026-11-03
Grafana Cloud: k6 timeouts, 1mdeclared on their status page2026-11-02
Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1), 1h 48mdeclared on their status page2026-11-02
Missing Metrics for Some Synthetic Monitoring Checks using the Montreal, North Virginia, and North California public probes, 1mdeclared on their status page2026-11-02
IRM Unable to Voice Call Brazil Numbers, 56h 9mdeclared on their status page2026-11-02

check 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 check readings and Grafana Cloud's own claim at the time, side by side.

Full check history for Grafana Cloud: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Grafana Cloud uptime by RealUptime's checksLive, from this page's own readings.
[![Grafana Cloud uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Grafana Cloud down?", https://realuptime.io/outages/grafana-cloud. The readings change with every check, so give the date you read them.

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
secondary
https://grafana.com/auth/sign-in
secondary
https://grafana.com/api/dashboards?pageSize=1
secondary
https://grafana.com/docs/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: grafana.com

RealUptime is not affiliated with Grafana Cloud; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.