Vendor record
Grafana Cloud
Checked
Front door check counts and Grafana Cloud’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Grafana Cloud endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- grafana.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Grafana Cloud product, region or your app worked.
How we count front door checksGrafana Cloud says
Incident posts from Grafana Cloud’s status page, with its titles, impact levels and times. They say what Grafana Cloud chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
6
incidents Grafana Cloud posted, last 7 days
Median recorded duration: 2h 52m. From 5 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Tempo Write Failures in prod-us-central-0
MajorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(5h 50m)
Tempo: High Latency in prod-eu-west-2
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(2h 25m)
Authentication errors in prod-us-west-0
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(2h 52m)
Errors when querying Prometheus datasource
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(54m)
Phone call notifications to numbers in Russia and Kazakhstan are blocked
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Latest status Grafana Cloud postedInvestigating. No resolution posted.
15 older records
Elevated Errors Ingesting Metrics in AWS US East (VA)
MajorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(7h 4m)
Degraded Performance with Increased Latency for Grafana Cloud Metrics and Traces in GCP US Central
MajorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(11h 34m)
Intermittent Errors and Latency for Grafana Cloud Metrics, Logs and Traces in GCP US Central (prod-us-central-0 and prod-us-central-5)
MajorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(21m)
IRM Unable to Send SMS to Thailand Numbers
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Latest status Grafana Cloud postedIdentified. No resolution posted.
Degraded data source queries
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(14m)
Elevated Write Latency and Errors for Grafana Cloud in GCP Saudi Arabia
Not specifiedGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(5h 51m)
Elevated Write Latency and Errors for Grafana Cloud Logs in Azure Netherlands
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(4h 6m)
Elevated Latency and Errors for Grafana Cloud Logs in AWS US East (VA)
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(5h 29m)
Grafana Access Issues
CriticalGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(3h 37m)
Cloud Provider Observability - Hosted Azure metrics issues
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(58m)
Azure Monitor increased timeouts and errors in prod-eu-west-5
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(44m)
Kubernetes Observability Billing & Usage Incorrect
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(16h 42m)
IRM Access Issues for a Small Group of Users
MajorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(20h 12m)
Increased Execution Time for Browser Checks in Synthetic Monitoring
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(1h 19m)
Investigating elevated database load in AWS Germany
MinorGrafana Cloud’s postStarted, per Grafana Cloud
Closed in our record(2h 42m)
Your code, your dependencies
See which of your code paths call Grafana Cloud
Connect GitHub or GitLab to find where your public or private repository uses Grafana Cloud. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Grafana Cloud status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Grafana Cloud currently down?
Grafana Cloud's latest recorded status is Degraded. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Grafana Cloud last have an outage?
The most recent closed incident record began 1 day ago and spans 5h 50m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Grafana Cloud?
No. CheckUpstream checks Grafana Cloud’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Grafana Cloud in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Grafana Cloud?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.