IRM Unable to Send SMS to Thailand Numbers
Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.
The latest update from Grafana Cloud.
State
Resolved
Started
27 d ago
2026-10-05 16:17 UTC
Lasted
14 days
until 2026-10-19 11:40 UTC
Worst impact
Degraded
Timeline
8 updatesInvestigating
5 h 29 min 2%
Identified
14 days 98%
Updates
Times in UTCAs posted by Grafana Cloud
Following further investigation, we've confirmed that SMS delivery to certain destinations is not currently supported. We've updated our documentation to clarify the supported destinations and available notification options. We recommend using mobile push notifications or phone calls as alternatives where SMS delivery is unavailable.
SMS delivery to Bangladesh has been restored. SMS delivery to Thailand is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.
SMS delivery to Austrian numbers has been restored. SMS delivery to Thailand and Bangladesh is still affected, and we are continuing to work on a resolution. We will provide another update as soon as we have more information to share. In the meantime, we recommend that affected users configure mobile push or phone calls as notifications.
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.
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.
This issue is also impacting numbers from Thailand and Bangladesh. The title of this status page has been updated to reflect this. Users should configure mobile push or phone calls as notifications. We are working on a resolution, and we will provide another update as soon as we have more information to share.
The issue has been identified. We are working on a resolution, but do not have an ETA at this time. We will provide another update as soon as we have more information to share. Users should configure mobile push or phone calls as notifications.
We are currently investigating an issue impacting all SMS attempts to Austria for IRM. All SMS attempts to Austria for IRM are currently blocked. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or phone calls as notifications.
Affected components
1Grafana Cloud in the last 90 days
Full historyIncidents in 90 days
44
Days with an incident
36
Median duration
2 h 53 min
This incident
115× the median
Other Grafana Cloud incidents
All incidentsGrafana Cloud·Frontend Observability Outage in prod-eu-west-2
This incident has been resolved.
Grafana Cloud·Degraded Cloud Integrations
This incident has been resolved.
Grafana Cloud·ingestion errors in mimir-prod-66
the issue is resolved now, we're watching the cell
Grafana Cloud·Some Grafana Instances Experiencing Issues Coming Online after Restart
This incident has been resolved.
Grafana Cloud·Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany
Between 09:31 and 10:13 UTC on 23 October 2026 (42 minutes), Grafana Cloud Traces in AWS Germany experienced elevated ingestion latency and intermittent trace write failures, affecting both direct trace ingestion and ingestion via the OpenTelemetry endpoint. All services are now operating normally.
Follow Grafana Cloud
Your coding agent knows when Grafana Cloud is down, and tells you when a failure is theirs, not yours. You can also get Grafana Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "grafana" and tell me if Grafana Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=grafana/feed subscribe https://outages.cc/feed.xml?providers=grafanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane