Skip to content

Outage tracker / Grafana Cloud

Is Grafana Cloud down?

Short linkrlup.io/down/grafana-cloud

I'm having a problem

Operationalchecked moments ago

We reached Grafana Cloud from all 10 regions we check.

As of Oct 6, 2026, 11:13 PM UTC, Grafana Cloud answered RealUptime's probes in all 10 regions that returned a reading.

Grafana Cloud is reporting an open incident: "IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers" since Oct 5, 2026, 4:17 PM UTC. their claim, not our reading

Functional endpoints verified

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

our independent probeslive · checked Oct 6, 2026, 11:13 PM UTC
US-East708 msOperational
US-West265 msOperational
Europe115 msOperational
Asia-Pacific290 msOperational
US-Central195 msOperational
Canada198 msOperational
UK655 msOperational
Southeast Asia638 msOperational
Australia321 msOperational
South America269 msOperational
their status pagetheir claim, not our reading

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

from Grafana Cloud's own status page, checked Oct 6, 2026, 10:58 PM UTC

Grafana Cloud reports an active incident: IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers (minor incident, since Oct 5, 2026, 4:17 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

  • 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-1Operational
  • 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 published 16 incidents in the last 30 days. Our probes recorded 0 outages seen from more than one region in that time.

Grafana Cloud response time, by region

US-East
506msp95 · 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-09-07 UTC: p95 552ms2026-09-08 UTC: p95 641ms2026-09-09 UTC: p95 666ms2026-09-10 UTC: p95 456ms2026-09-11 UTC: p95 427ms2026-09-12 UTC: p95 511ms2026-09-13 UTC: p95 480ms2026-09-14 UTC: p95 564ms2026-09-15 UTC: p95 532ms2026-09-16 UTC: p95 535ms2026-09-17 UTC: p95 614ms2026-09-18 UTC: p95 571ms2026-09-19 UTC: p95 676ms2026-09-20 UTC: p95 710ms2026-09-21 UTC: p95 612ms2026-09-22 UTC: p95 687ms2026-09-23 UTC: p95 551ms2026-09-24 UTC: p95 408ms2026-09-25 UTC: p95 451ms2026-09-26 UTC: p95 404ms2026-09-27 UTC: p95 396ms2026-09-28 UTC: p95 627ms2026-09-29 UTC: p95 657ms2026-09-30 UTC: p95 702ms2026-10-01 UTC: p95 494ms2026-10-02 UTC: p95 451ms2026-10-03 UTC: p95 580ms2026-10-04 UTC: p95 463ms2026-10-05 UTC: p95 367ms2026-10-06 UTC: p95 506ms
Sep 7Sep 21Oct 6
US-West
458msp95 · 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-09-07 UTC: p95 583ms2026-09-08 UTC: p95 669ms2026-09-09 UTC: p95 581ms2026-09-10 UTC: p95 648ms2026-09-11 UTC: p95 398ms2026-09-12 UTC: p95 490ms2026-09-13 UTC: p95 536ms2026-09-14 UTC: p95 658ms2026-09-15 UTC: p95 503ms2026-09-16 UTC: p95 329ms2026-09-17 UTC: p95 336ms2026-09-18 UTC: p95 361ms2026-09-19 UTC: p95 364ms2026-09-20 UTC: p95 431ms2026-09-21 UTC: p95 392ms2026-09-22 UTC: p95 650ms2026-09-23 UTC: p95 596ms2026-09-24 UTC: p95 670ms2026-09-25 UTC: p95 862ms2026-09-26 UTC: p95 578ms2026-09-27 UTC: p95 676ms2026-09-28 UTC: p95 606ms2026-09-29 UTC: p95 444ms2026-09-30 UTC: p95 677ms2026-10-01 UTC: p95 703ms2026-10-02 UTC: p95 479ms2026-10-03 UTC: p95 615ms2026-10-04 UTC: p95 530ms2026-10-05 UTC: p95 318ms2026-10-06 UTC: p95 458ms
Sep 7Sep 21Oct 6
Europe
524msp95 · 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-09-07 UTC: p95 683ms2026-09-08 UTC: p95 703ms2026-09-09 UTC: p95 526ms2026-09-10 UTC: p95 499ms2026-09-11 UTC: p95 467ms2026-09-12 UTC: p95 534ms2026-09-13 UTC: p95 446ms2026-09-14 UTC: p95 452ms2026-09-15 UTC: p95 652ms2026-09-16 UTC: p95 616ms2026-09-17 UTC: p95 470ms2026-09-18 UTC: p95 534ms2026-09-19 UTC: p95 440ms2026-09-20 UTC: p95 475ms2026-09-21 UTC: p95 534ms2026-09-22 UTC: p95 582ms2026-09-23 UTC: p95 704ms2026-09-24 UTC: p95 704ms2026-09-25 UTC: p95 513ms2026-09-26 UTC: p95 395ms2026-09-27 UTC: p95 520ms2026-09-28 UTC: p95 565ms2026-09-29 UTC: p95 948ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 719ms2026-10-02 UTC: p95 542ms2026-10-03 UTC: p95 521ms2026-10-04 UTC: p95 495ms2026-10-05 UTC: p95 608ms2026-10-06 UTC: p95 524ms
Sep 7Sep 21Oct 6
Asia-Pacific
645msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 816ms2026-09-08 UTC: p95 699ms2026-09-09 UTC: p95 702ms2026-09-10 UTC: p95 699ms2026-09-11 UTC: p95 573ms2026-09-12 UTC: p95 565ms2026-09-13 UTC: p95 612ms2026-09-14 UTC: p95 692ms2026-09-15 UTC: p95 580ms2026-09-16 UTC: p95 601ms2026-09-17 UTC: p95 637ms2026-09-18 UTC: p95 601ms2026-09-19 UTC: p95 654ms2026-09-20 UTC: p95 692ms2026-09-21 UTC: p95 673ms2026-09-22 UTC: p95 793ms2026-09-23 UTC: p95 950ms2026-09-24 UTC: p95 763ms2026-09-25 UTC: p95 899ms2026-09-26 UTC: p95 713ms2026-09-27 UTC: p95 767ms2026-09-28 UTC: p95 682ms2026-09-29 UTC: p95 652ms2026-09-30 UTC: p95 852ms2026-10-01 UTC: p95 664ms2026-10-02 UTC: p95 719ms2026-10-03 UTC: p95 852ms2026-10-04 UTC: p95 622ms2026-10-05 UTC: p95 504ms2026-10-06 UTC: p95 645ms
Sep 7Sep 21Oct 6
US-Central
365msp95 · 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-09-07 UTC: p95 619ms2026-09-08 UTC: p95 562ms2026-09-09 UTC: p95 690ms2026-09-10 UTC: p95 679ms2026-09-11 UTC: p95 683ms2026-09-12 UTC: p95 738ms2026-09-13 UTC: p95 794ms2026-09-14 UTC: p95 774ms2026-09-15 UTC: p95 759ms2026-09-16 UTC: p95 295ms2026-09-17 UTC: p95 294ms2026-09-18 UTC: p95 303ms2026-09-19 UTC: p95 402ms2026-09-20 UTC: p95 491ms2026-09-21 UTC: p95 479ms2026-09-22 UTC: p95 584ms2026-09-23 UTC: p95 470ms2026-09-24 UTC: p95 426ms2026-09-25 UTC: p95 470ms2026-09-26 UTC: p95 411ms2026-09-27 UTC: p95 493ms2026-09-28 UTC: p95 813ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 514ms2026-10-03 UTC: p95 689ms2026-10-04 UTC: p95 476ms2026-10-05 UTC: p95 311ms2026-10-06 UTC: p95 365ms
Sep 7Sep 21Oct 6
Canada
249msp95 · 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-07 UTC: p95 756ms2026-09-08 UTC: p95 637ms2026-09-09 UTC: p95 553ms2026-09-10 UTC: p95 532ms2026-09-11 UTC: p95 433ms2026-09-12 UTC: p95 326ms2026-09-13 UTC: p95 353ms2026-09-14 UTC: p95 559ms2026-09-15 UTC: p95 480ms2026-09-16 UTC: p95 335ms2026-09-17 UTC: p95 288ms2026-09-18 UTC: p95 233ms2026-09-19 UTC: p95 407ms2026-09-20 UTC: p95 367ms2026-09-21 UTC: p95 358ms2026-09-22 UTC: p95 479ms2026-09-23 UTC: p95 630ms2026-09-24 UTC: p95 581ms2026-09-25 UTC: p95 696ms2026-09-26 UTC: p95 547ms2026-09-27 UTC: p95 396ms2026-09-28 UTC: p95 503ms2026-09-29 UTC: p95 398ms2026-09-30 UTC: p95 412ms2026-10-01 UTC: p95 1s2026-10-02 UTC: p95 659ms2026-10-03 UTC: p95 755ms2026-10-04 UTC: p95 556ms2026-10-05 UTC: p95 656ms2026-10-06 UTC: p95 249ms
Sep 7Sep 21Oct 6
UK
562msp95 · 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-09-07 UTC: p95 534ms2026-09-08 UTC: p95 654ms2026-09-09 UTC: p95 610ms2026-09-10 UTC: p95 533ms2026-09-11 UTC: p95 494ms2026-09-12 UTC: p95 524ms2026-09-13 UTC: p95 498ms2026-09-14 UTC: p95 483ms2026-09-15 UTC: p95 553ms2026-09-16 UTC: p95 530ms2026-09-17 UTC: p95 600ms2026-09-18 UTC: p95 551ms2026-09-19 UTC: p95 506ms2026-09-20 UTC: p95 470ms2026-09-21 UTC: p95 536ms2026-09-22 UTC: p95 432ms2026-09-23 UTC: p95 534ms2026-09-24 UTC: p95 521ms2026-09-25 UTC: p95 514ms2026-09-26 UTC: p95 362ms2026-09-27 UTC: p95 277ms2026-09-28 UTC: p95 558ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 591ms2026-10-03 UTC: p95 528ms2026-10-04 UTC: p95 560ms2026-10-05 UTC: p95 518ms2026-10-06 UTC: p95 562ms
Sep 7Sep 21Oct 6
Southeast Asia
1.1sp95 · 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-07 UTC: p95 1.2s2026-09-08 UTC: p95 999ms2026-09-09 UTC: p95 803ms2026-09-10 UTC: p95 848ms2026-09-11 UTC: p95 833ms2026-09-12 UTC: p95 937ms2026-09-13 UTC: p95 947ms2026-09-14 UTC: p95 932ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.7s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 647ms2026-09-30 UTC: p95 644ms2026-10-01 UTC: p95 544ms2026-10-02 UTC: p95 847ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 889ms2026-10-06 UTC: p95 1.1s
Sep 7Sep 21Oct 6
Australia
475msp95 · 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-07 UTC: p95 1.0s2026-09-08 UTC: p95 776ms2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 896ms2026-09-12 UTC: p95 943ms2026-09-13 UTC: p95 981ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 936ms2026-09-16 UTC: p95 714ms2026-09-17 UTC: p95 754ms2026-09-18 UTC: p95 740ms2026-09-19 UTC: p95 849ms2026-09-20 UTC: p95 787ms2026-09-21 UTC: p95 894ms2026-09-22 UTC: p95 760ms2026-09-23 UTC: p95 995ms2026-09-24 UTC: p95 979ms2026-09-25 UTC: p95 973ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 579ms2026-09-30 UTC: p95 859ms2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 826ms2026-10-04 UTC: p95 811ms2026-10-05 UTC: p95 498ms2026-10-06 UTC: p95 475ms
Sep 7Sep 21Oct 6
South America
897msp95 · 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-07 UTC: p95 702ms2026-09-08 UTC: p95 921ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 950ms2026-09-14 UTC: p95 899ms2026-09-15 UTC: p95 862ms2026-09-16 UTC: p95 810ms2026-09-17 UTC: p95 876ms2026-09-18 UTC: p95 946ms2026-09-19 UTC: p95 915ms2026-09-20 UTC: p95 949ms2026-09-21 UTC: p95 956ms2026-09-22 UTC: p95 806ms2026-09-23 UTC: p95 896ms2026-09-24 UTC: p95 674ms2026-09-25 UTC: p95 756ms2026-09-26 UTC: p95 738ms2026-09-27 UTC: p95 686ms2026-09-28 UTC: p95 755ms2026-09-29 UTC: p95 643ms2026-09-30 UTC: p95 791ms2026-10-01 UTC: p95 570ms2026-10-02 UTC: p95 735ms2026-10-03 UTC: p95 952ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 897ms
Sep 7Sep 21Oct 6

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

Get an email when we see Grafana Cloud go down, and when it is back

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.

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: 708msstatus code: 200checked: Oct 6, 2026, 11:05 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
      Operationallatency: 265msstatus code: 200checked: Oct 6, 2026, 11:12 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
      Operationallatency: 195msstatus code: 200checked: Oct 6, 2026, 11:12 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
      Operationallatency: 198msstatus code: 200checked: Oct 6, 2026, 11:12 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
    Operationallatency: 269msstatus code: 200checked: Oct 6, 2026, 11:11 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 115msstatus code: 200checked: Oct 6, 2026, 11:13 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
      Operationallatency: 655msstatus code: 200checked: Oct 6, 2026, 11:12 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 290msstatus code: 200checked: Oct 6, 2026, 11:05 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
      Operationallatency: 638msstatus code: 200checked: Oct 6, 2026, 11:12 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
      Operationallatency: 321msstatus code: 200checked: Oct 6, 2026, 11:12 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 outages

IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbersdeclared on their status page2026-10-05
Degraded data source queries, 14mdeclared on their status page2026-10-04
Elevated Write Latency and Errors for Grafana Cloud in GCP Saudi Arabia, 5h 50mdeclared on their status page2026-10-03
Elevated Write Latency and Errors for Grafana Cloud Logs in Azure Netherlands, 4hdeclared on their status page2026-10-02
Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA), 2h 59mdeclared on their status page2026-09-30
Grafana Access Issues, 1h 49mdeclared on their status page2026-09-28
Elevated Log Ingestion Errors for Grafana Cloud Logs in Azure Netherlands (EU), 1mdeclared on their status page2026-09-28
Cloud Provider Observability - Hosted Azure metrics issues, 49mdeclared on their status page2026-09-26

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.

Related services

AWS (Amazon Web Services)AkamaiAmplitudeAnthropicAuth0