Is Grafana Cloud down right now?

Partly. As of 2026-10-10 07:17 UTC, Grafana Cloud is having issues, with an open incident: "IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers". This page reads the status again every 3 minutes.

How long do Grafana Cloud outages usually last?

Of the 8 incidents Grafana Cloud reported in the last 90 days, half were resolved within 2 h 59 min and nine in ten within 11 h 33 min; the longest took 11 h 33 min. These are the provider's own start and end times.

Where does this status come from?

From Grafana Cloud's own status page API at https://status.grafana.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Grafana Cloud's words.

Can I get an alert when Grafana Cloud goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Grafana Cloud reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/grafana/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Grafana Cloud status?

Fetch https://upbutler.com/status/grafana/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"grafana"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Grafana Cloud's?

Add "grafana" to the dependencies of your UpButler workspace. When one of your monitors fails while Grafana Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Grafana Cloud down?

Grafana Cloud is having issues

Right now

Partly. IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers.

Last checked 3 min ago (2026-10-10 07:17 UTC) from status.grafana.com · every 180s

For agents

proceed

Proceed, expect slow or flaky responses.

GET upbutler.com/status/grafana/status.agent.json

MCP: upstream_status {"service":"grafana"}

Hosted Grafana, Prometheus metrics, Loki logs and Tempo traces per region.

What Grafana Cloud says

Degraded· 1 open incident

Taken as is from Grafana Cloud's own status page API. Incident titles and component names below are theirs.

Open status.grafana.com

What UpButler measured

There is no keyless endpoint of Grafana Cloud that says anything useful, so UpButler does not probe it. To check your own Grafana Cloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Grafana Cloud

IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbersidentified · impact minor
Since 2026-10-05 16:17 UTC · Incident Management and Response (IRM)
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.
Scheduled Database Maintenancescheduled maintenance
Starts 2026-10-14 14:00 UTC · Azure Netherlands - prod-eu-west-3, GCP Australia - prod-au-southeast-0, GCP Belgium - prod-eu-west-0, GCP Brazil - prod-sa-east-0, GCP India - prod-ap-south-0, GCP Singapore - prod-ap-southeast-0 +5
We will be performing scheduled database maintenance during this window. Your Grafana instance will keep running normally throughout. Dashboards, alerting, data ingestion and querying are not affected. During a short period within the window you may be unable to create or delete a stack, change your plan, or apply version and configuration changes in that region. Any such operation can be retried once the window closes.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailabilityscheduled maintenance
Starts 2026-10-14 08:00 UTC · GCP US East - prod-us-east-1
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.
Scheduled Database Maintenance – Temporary Grafana Instance Unavailabilityscheduled maintenance
Starts 2026-10-13 08:00 UTC · GCP US East - prod-us-east-1
Your Grafana instance will be temporarily unavailable due to scheduled maintenance. Downtime is expected to last between 5 to 15 minutes depending on your instance size. Alerts and scheduled reports may be impacted during this period. No action is required — your instance will return to its normal working state automatically once maintenance is complete. We apologize for the inconvenience.

Text written by Grafana Cloud, shown unchanged.

Which part of Grafana Cloud?

Incident Management and Response (IRM)Degraded

Grafana Cloud components

1 of 80 not operational

Website and Support

Grafana.comOperational
Support TicketsOperational

Profiles

AWS Australia - prod-au-southeast-1Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS India - prod-ap-south-1Operational
AWS Japan - prod-ap-northeast-0Operational

Grafana

AWS Australia - prod-ap-southeast-2Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS Germany - prod-eu-west-4Operational
AWS India - prod-ap-south-1Operational

Metrics

AWS Australia - prod-ap-southeast-2: QueryingOperational
AWS Australia - prod-ap-southeast-2: IngestionOperational
AWS Brazil - prod-sa-east-1: QueryingOperational
AWS Brazil - prod-sa-east-1: IngestionOperational
AWS Canada - prod-ca-east-0: QueryingOperational
AWS Canada - prod-ca-east-0: IngestionOperational

Alerting and SLO

AWS Australia - prod-ap-southeast-2: Rule EvaluationOperational
AWS Australia - prod-ap-southeast-2: Alertmanager and Rules Configuration APIOperational
AWS Australia - prod-ap-southeast-2: AlertmanagerOperational
AWS Brazil - prod-sa-east-1: Rule EvaluationOperational
AWS Brazil - prod-sa-east-1: Alertmanager and Rules Configuration APIOperational
AWS Brazil - prod-sa-east-1: AlertmanagerOperational

Logs

AWS Australia - prod-ap-southeast-2Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS UAE - prod-me-central-1Operational
AWS India - prod-ap-south-1Operational

Traces

AWS Australia - prod-ap-southeast-2: QueryingOperational
AWS Australia - prod-ap-southeast-2: IngestionOperational
AWS Australia - prod-ap-southeast-2: Metrics GeneratorOperational
AWS Brazil - prod-sa-east-1: QueryingOperational
AWS Brazil - prod-sa-east-1: IngestionOperational

AI and Machine Learning

AWS Australia - prod-au-southeast-1Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS India - prod-ap-south-1Operational
AWS Japan - prod-ap-northeast-0Operational

Synthetic Monitoring

AWS Australia - prod-au-southeast-1: APIOperational
AWS Australia - prod-au-southeast-1: Public ProbesOperational
AWS Brazil - prod-sa-east-1: APIOperational
AWS Brazil - prod-sa-east-1: Public ProbesOperational
AWS Canada - prod-ca-east-0: APIOperational
AWS Canada - prod-ca-east-0: Public ProbesOperational

OpenTelemetry Ingest Endpoint

AWS Australia - prod-au-southeast-1Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS India - prod-ap-south-1Operational
AWS Japan - prod-ap-northeast-0Operational

Frontend Observability

AWS Australia - prod-au-southeast-1Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS India - prod-ap-south-1Operational

Private Datasource Connect (PDC)

AWS Australia - prod-au-southeast-1Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS India - prod-ap-south-1Operational

Performance and Load Testing

GCk6 AppOperational
Cloud Test RunsOperational
Cloud Output Test RunsOperational
Result AnalysisOperational
Test SchedulingOperational

Grafana Assistant

AWS Australia - prod-ap-southeast-2Operational
AWS Brazil - prod-sa-east-1Operational
AWS Canada - prod-ca-east-0Operational
AWS Germany - prod-eu-west-2Operational
AWS Germany - prod-eu-west-4Operational

Knowledge Graph

AWS Japan - prod-ap-northeast-0Operational
AWS India - prod-ap-south-1Operational
AWS Singapore - prod-ap-southeast-1Operational
AWS Australia - prod-ap-southeast-2Operational

Incident Management and Response (IRM)Degraded

Grafana Cloud incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: no record
2026-09-28: critical incident
2026-09-29: no incident reported
2026-09-30: minor incident
2026-10-01: no incident reported
2026-10-02: minor incident
2026-10-03: no incident reported
2026-10-04: minor incident
2026-10-05: minor incident
2026-10-06: minor incident
2026-10-07: minor incident
2026-10-08: minor incident
2026-10-09: minor incident
2026-10-10: minor incident

2026-07-1310 of 13 days with an incidenttoday

Each bar is a day, coloured by the worst incident Grafana Cloud reported. It is their incident record, not a measurement of uptime.

Incidents: 8; 1 major or critical
Typical time to resolve: 2 h 59 min; median
Nine in ten within: 11 h 33 min; 90th percentile
Longest: 11 h 33 min; record since 2026-09-28

Started (UTC)	Incident	Impact	Lasted
2026-10-08 13:06	Degraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Central	none	11 h 33 min
2026-10-07 08:40	Grafana Cloud k6 – Brief metrics unavailability	none	under a minute
2026-10-04 18:20	Degraded data source queries	minor	14 min
2026-10-03 13:53	Elevated Write Latency and Errors for Grafana Cloud in GCP Saudi Arabia	none	5 h 50 min
2026-10-02 10:03	Elevated Write Latency and Errors for Grafana Cloud Logs in Azure Netherlands	minor	4 h
2026-09-30 12:40	Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)	minor	2 h 59 min
2026-09-28 17:32	Grafana Access Issues	critical	1 h 49 min
2026-09-28 12:02	Elevated Log Ingestion Errors for Grafana Cloud Logs in Azure Netherlands (EU)	none	under a minute

Get alerted when Grafana Cloud goes down

No account. One email when Grafana Cloud reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Grafana Cloud as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Grafana Cloud's current status in a README or an internal wiki. It updates by itself.

[![Grafana Cloud status](https://upbutler.com/status/grafana/badge.svg)](https://upbutler.com/status/grafana)

Tell your outage from Grafana Cloud's

Declare that your project depends on Grafana Cloud. When one of your monitors fails while Grafana Cloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - grafana

Ask before you retry

curl -s https://upbutler.com/status/grafana/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "grafana",
  "verdict": "proceed",
  "status": "degraded",
  "reason": "IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers",
  "retryAfterSec": null,
  "incident": {
    "title": "IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers",
    "url": "https://status.grafana.com/incidents/6x77ccl9shpy"
  },
  "probe": null
}

Questions

Is Grafana Cloud down right now?: Partly. As of 2026-10-10 07:17 UTC, Grafana Cloud is having issues, with an open incident: "IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian Numbers". This page reads the status again every 3 minutes.
How long do Grafana Cloud outages usually last?: Of the 8 incidents Grafana Cloud reported in the last 90 days, half were resolved within 2 h 59 min and nine in ten within 11 h 33 min; the longest took 11 h 33 min. These are the provider's own start and end times.
Where does this status come from?: From Grafana Cloud's own status page API at https://status.grafana.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Grafana Cloud's words.
Can I get an alert when Grafana Cloud goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Grafana Cloud reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/grafana/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Grafana Cloud status?: Fetch https://upbutler.com/status/grafana/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"grafana"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Grafana Cloud's?: Add "grafana" to the dependencies of your UpButler workspace. When one of your monitors fails while Grafana Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Grafana Cloud. Status and incident text belong to Grafana Cloud and are read from their public status source; the probe result is UpButler's own measurement.