Degraded / minor incident Grafana Cloud status
grafana.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Grafana Cloud's status page shows “Degraded / minor incident” in AWS Australia - prod-au-southeast-1 and AWS Australia - prod-au-southeast-2; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.
confidence: low Vendor: minor issue · users: normal · routing: no data · upstream providers: major.
- Vendor status page Degraded / minor incident · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, AWS Brazil - prod-sa-east-1
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 40 h 24 min | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 2 h 17 min |
Evidence
- Official page: Degraded / minor incident (“Partially Degraded Service”). evidence confidence: high
- Vendor stage: resolved on “Data Source Permission Errors”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Grafana Cloud may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Grafana Cloud's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
Grafana Cloud may run on Amazon Web Services, Google Cloud, Microsoft Azure (inferred). We don't map other services that depend on Grafana Cloud. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Grafana Cloud or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Grafana Cloud. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Data Source Permission Errors
minor resolved · started · resolved
1 updates
- resolved
Between November 9 and November 18, 2026, some Grafana Cloud users with Edit or Admin permissions on a data source may have experienced “permission denied” (403) errors when configuring or querying a newly created data source. A change to how data source permissions are stored caused these permissions to be incorrectly evaluated. We rolled back that change on November 18 at 17:27 UTC, preventing newly created permissions from being affected. However, access issues caused by permissions stored before the rollback may persist until an additional fix is deployed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.