Grafana logo
ALL SYSTEMS OPERATIONAL

Grafana systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Feb 2026 · 127 incidents caught

Last checked: 5 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Grafana is up and running.

    Last incident resolved 12 hours ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    74

    Since Feb 2026

  • Major / Critical

    34

    34 high-impact incidents

  • Minor Incidents

    40

    Avg. 0.4 per day

  • Median Resolution

    2h 34m

    P95: 64h 33m

Grafana Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Alerting expressions pipeline failing when recovery settings
Aug 8, 2026 · 7:48 PM < 1m
Minor
Resolved
Details →
Some Cloud Test Runs Terminated
Aug 5, 2026 · 5:57 PM < 1m
None
Resolved
Details →
o11y requests too large for nods in the prod-eu-west-2 region.
Aug 5, 2026 · 11:41 AM 3m
Minor
Resolved
Details →
Some Grafana Instances Unavailable
Aug 4, 2026 · 7:11 PM 6h 20m
Critical
Resolved
Details →
Logs latency increase within prod-eu-west-3
Aug 4, 2026 · 10:34 AM 3h 14m
Minor
Resolved
Details →
K6 - Cloud test-run issues
Aug 1, 2026 · 7:25 AM 1h 5m
Minor
Resolved
Details →
Partial Read Outage for Loki in prod-us-east-4
Jul 31, 2026 · 7:30 PM < 1m
None
Resolved
Details →
Degraded Performance: Stack Provisioning Failures within certain reigons (PDC Setup)
Jul 31, 2026 · 10:51 AM 1h 22m
Minor
Resolved
Details →
PDC Authentication Issues
Jul 30, 2026 · 2:45 PM 2h 54m
Major
Resolved
Details →
Issues with Billing/Usage Dashboard Metrics and Panels.
Jul 30, 2026 · 1:15 PM 2h 1m
Major
Resolved
Details →

Get alerted the moment Grafana goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is Grafana down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Grafana go down?

    Based on our 90-day data, we've detected 74 incidents, of which 34 were major or critical. The median resolution time is 2h 34m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.