Tüm hizmetler / Geliştirici araçları
Grafana Cloud
- Güncel değerlendirme
- Çalışıyor (sağlayıcıya göre)
- Güven
- Orta güven
- Kapsam
- Sağlayıcı geneli
- Son doğrulama
- 19 Kas 01:21 GMT+3
- Kaynaklar
- 1 kaynak: Resmî
Resmî olay geçmişi
- ÇözüldüBaşlangıç: · Süre: 0 dk
Grafana Cloud: erişim sorunu / kesinti
Sağlayıcının özgün başlığı: Data Source Permission Errors
Sağlayıcı güncellemeleri (1)
- Çözüldü “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 …”
- ÇözüldüBaşlangıç: · Süre: 254 dk
Grafana Cloud: performans düşüklüğü
Sağlayıcının özgün başlığı: Elevated query errors for Grafana Cloud Metrics in prod-us-east-3
Sağlayıcı güncellemeleri (2)
- İzleniyor “Between 17:21 and 17:41 UTC, a small percentage of metrics queries for some Grafana Cloud Metrics customers in the prod-us-east-3 region failed. Ingestion was not affected. Query errors have stopped, and we are monitoring the service to confirm it stays stable.”
- Çözüldü “This incident has been resolved.”
- ÇözüldüBaşlangıç: · Süre: 96 dk
Grafana Cloud: Azure US Central - us-central7, Azure US Central - us-central7: Ingestion, performans düşüklüğü
Sağlayıcının özgün başlığı: Degraded performance for Grafana Cloud Metrics in prod-us-central-7
Sağlayıcı güncellemeleri (3)
- İnceleniyor “We are investigating an issue affecting Grafana Cloud Metrics, Logs, and Traces in the prod-us-central-7 region. Some customers may see failed or delayed writes, query errors, and failed alerting and recording rule evaluations.”
- İzleniyor “Traffic has recovered and we are monitoring the results.”
- Çözüldü “Increased latency on a cloud provider database resulted in a 50m write and rule evaluation outage, starting about 2020 UTC. Metrics rule evaluations were last to recover, around 2110 UTC.”
- ÇözüldüBaşlangıç: · Süre: 512 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: Mimir query unexpected response with status code 500
Sağlayıcı güncellemeleri (3)
- Neden bulundu “We’ve identified an issue querying older data, and are already seeing recovery”
- İzleniyor “A fix has been implemented and we are monitoring the results.”
- Çözüldü “From approximately 03:20 UTC on 10 November, some Grafana Cloud Metrics customers in AWS US East (OH) and GCP US Central saw errors, or failed queries, when reading older data. Service has fully recovered and this incident is now resolved.”
- ÇözüldüBaşlangıç: · Süre: 17 dk
Grafana Cloud: AWS Switzerland - prod-eu-central-0, gecikme artışı
Sağlayıcının özgün başlığı: Cloud Logs writes - Elevated latency and error rates in prod-eu-central-0
Sağlayıcı güncellemeleri (2)
- İzleniyor “Cloud Logs writes have experienced elevated latency and error rates in prod-eu-central-0 from 07:05 UTC to 07:08 UTC, and 07:25 UTC to 07:45 UTC. The latency has been mitigated and we are currently monitoring.”
- Çözüldü “We're observing a continued period of recovery and will mark this as resolved.”
- ÇözüldüBaşlangıç: · Süre: 4517 dk
Grafana Cloud: kullanım/fatura raporu görüntüleme sorunu
Kullanıma etkisi yok; yalnız rapor ekranı.
Sağlayıcının özgün başlığı: October usage report visualization issue
Sağlayıcı güncellemeleri (2)
- Neden bulundu “There was an issue with our billing metrics exporter that caused us to mis-report usage for October at month-end. This is causing October usage to be reported as 0 in our cost management app. We are working to backfill the correct data. Note that this did not affect billing, and is only a visualization issue.”
- Çözüldü “This incident has been resolved.”
- ÇözüldüBaşlangıç: · Süre: 0 dk
Grafana Cloud: AWS Indonesia - prod-ap-southeast-2: Public Probes, performans düşüklüğü
Sağlayıcının özgün başlığı: Synthetic Monitoring — Jakarta Public Probe Degradation
Sağlayıcı güncellemeleri (1)
- Çözüldü “Between 08:31 and 09:17 UTC on 6 November 2026, a network issue at the Jakarta public probe caused elevated check failures for monitors running from that location. - DNS checks: failure rate increased from ~0.3% to ~15% - HTTP, ping, traceroute, and browser checks: <1% failure rate - Browser checks: some delays and retries observed - TCP checks: not affected - All other probe locations: not affe…”
- ÇözüldüBaşlangıç: · Süre: 3369 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: IRM Unable to Voice Call Brazil Numbers
Sağlayıcı güncellemeleri (2)
- İnceleniyor “We are currently investigating an issue impacting Voice calls to Brazil for IRM. We are working on a resolution, and an update will follow as soon as we have more info. Users should configure mobile push or SMS as notifications.”
- Çözüldü “Brazil calls recovered at about 13:00 UTC on 3 November. At this point, we are marking the incident as resolved.”
- ÇözüldüBaşlangıç: · Süre: 118 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: GitHub returning 403 for all Git Sync repositories
Sağlayıcı güncellemeleri (3)
- Neden bulundu “Since ~21:40 UTC on Nov 3, GitHub started rejecting the default User-Agent our Git Sync client sends (nanogit/0), so nearly every GitHub-backed repo shows as unhealthy ("not authorized") and syncs are being skipped. Our Engineering team has rolled out a fix to development and validated that the fix works. We will roll out the fix to production shortly and will provide another update.”
- İzleniyor “The fix has landed in 60% of production. We are currently monitoring as it lands in the remaining clusters.”
- Çözüldü “The fix has been deployed to all production clusters and we are observing a continued period of stability. At this time, we are marking the incident as resolved.”
- ÇözüldüBaşlangıç: · Süre: 0 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: Grafana Cloud: k6 timeouts
Sağlayıcı güncellemeleri (1)
- Çözüldü “We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.”
- ÇözüldüBaşlangıç: · Süre: 91 dk
Grafana Cloud: GCP US Central - prod-us-central-0, GCP US Central - prod-us-central-0: Rule Evaluation, gecikme artışı
Sağlayıcının özgün başlığı: Increased query latency for Logs in GCP US Central (prod-us-central-0)
Sağlayıcı güncellemeleri (2)
- İzleniyor “Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. The issue is believed to be mitigated, and the team is monitoring while the cause is investigated.”
- Çözüldü “This incident has been resolved. Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. Some Metrics alert and recording rule evaluations in the same region were also delayed between 12:11 and 12:44 UTC. Both issues have been mitigated.”
- ÇözüldüBaşlangıç: · Süre: 61 dk
Grafana Cloud: AWS Australia - prod-au-southeast-1, AWS Australia - prod-au-southeast-2, performans düşüklüğü
Sağlayıcının özgün başlığı: Elevated Request Errors for Grafana Across Multiple Regions
Sağlayıcı güncellemeleri (4)
- İnceleniyor “We are investigating some failed requests affecting Grafana across multiple Grafana Cloud regions, beginning at approximately 12:10 UTC. Customers may see slow-loading or failing dashboards and Explore queries, and some requests may time out or be cancelled. Our engineers are actively investigating. Next update by 13:30 UTC.”
- Neden bulundu “We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and are applying mitigation. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.”
- İzleniyor “We have identified the cause of the elevated request errors affecting Grafana across multiple Grafana Cloud regions and have applied a mitigation. We are seeing early signs of recovery and are monitoring closely. Customers may still see slow-loading or failing dashboards and Explore queries while recovery continues. Next update by 13:30 UTC.”
- Çözüldü “Between approximately 12:10 UTC and 13:22 UTC on 3 November (about 1 hour 12 minutes), Grafana across multiple Grafana Cloud regions experienced elevated request errors, causing slow-loading or failing dashboards and Explore queries. The issue has been resolved and service has been fully restored.”
- ÇözüldüBaşlangıç: · Süre: 0 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: Missing Metrics for Some Synthetic Monitoring Checks using the Montreal, North Virginia, and North California public probes
Sağlayıcı güncellemeleri (1)
- Çözüldü “Between approximately 08:09 and 09:10 UTC on 2 November (about 1 hour 11 minutes), a subset of Synthetic Monitoring checks running from the Montreal, North Virginia, and North California public probe locations experienced missing metrics, which may have appeared as gaps in dashboards. Specifically this affected: Checks with the Montreal Public Probe from 08:09-09:00 UTC Checks with the North Vir…”
- ÇözüldüBaşlangıç: · Süre: 108 dk
Grafana Cloud: AWS Australia - prod-au-southeast-1: Rule Evaluation, erişim sorunu / kesinti
Sağlayıcının özgün başlığı: Metrics Alert Rule Evaluation Failures in AWS Australia (prod-au-southeast-1)
Sağlayıcı güncellemeleri (2)
- İnceleniyor “We are investigating an elevated rate of failures when evaluating Metrics alert and recording rules in AWS Australia (prod-au-southeast-1). Some customers may see rules missed or delayed rule evaluations, which can result in missed or delayed alert notifications and gaps in recorded series. Next update by 10:20 UTC.”
- Çözüldü “Between approximately 08:00 and 09:40 UTC (about 1 hour 40 minutes), some customers in AWS Australia (prod-au-southeast-1) experienced intermittent failures when evaluating alert and recording rules, which may have caused missed or delayed alert notifications and gaps in recorded series. This has been fully resolved and rule evaluation is operating normally.”
- ÇözüldüBaşlangıç: · Süre: 282 dk
Grafana Cloud: Integrations, performans düşüklüğü
Sağlayıcının özgün başlığı: Degraded Cloud Integrations
Sağlayıcı güncellemeleri (3)
- İnceleniyor “We are currently investigating an issue impacting Cloud Integrations in prod-eu-west-3. We will provide another update when we have more to share.”
- İzleniyor “Things are no longer degraded. We are currently monitoring the issue”
- Çözüldü “This incident has been resolved.”
- ÇözüldüBaşlangıç: · Süre: 28 dk
Grafana Cloud: AWS Germany - prod-eu-west-2, erişim sorunu / kesinti
Sağlayıcının özgün başlığı: Frontend Observability Outage in prod-eu-west-2
Sağlayıcı güncellemeleri (2)
- İnceleniyor “We are currently investigating an issue impacting Frontend Observability since 15:20 UTC. We will provide another update as soon as we have more to share.”
- Çözüldü “This incident has been resolved.”
- ÇözüldüBaşlangıç: · Süre: 60 dk
Grafana Cloud: AWS US East (VA) - prod-us-east-3, erişim sorunu / kesinti
Sağlayıcının özgün başlığı: ingestion errors in mimir-prod-66
Sağlayıcı güncellemeleri (2)
- Neden bulundu “The issue has been identified, we are working on a fix”
- Çözüldü “the issue is resolved now, we're watching the cell”
- ÇözüldüBaşlangıç: · Süre: 283 dk
Grafana Cloud: sağlayıcı bildirimi
Sağlayıcının özgün başlığı: Some Grafana Instances Experiencing Issues Coming Online after Restart
Sağlayıcı güncellemeleri (3)
- Neden bulundu “Starting at approximately 12:37 UTC, a some Hosted Grafana instances across multiple regions have been experiencing availability issues. Our team has identified the root cause and a fix is currently in progress. Affected instances will recover automatically once the fix has been applied. No action is required on your end. We will provide further updates as they become available and apologize for …”
- İzleniyor “A fix as been implemented and Hosted Grafana instances are back to normal levels. We will continue to monitor the issue.”
- Çözüldü “This incident has been resolved.”
- ÇözüldüBaşlangıç: · Süre: 45 dk
Grafana Cloud: AWS Germany - prod-eu-west-2, AWS Germany - prod-eu-west-2: Ingestion, gecikme artışı
Sağlayıcının özgün başlığı: Elevated Trace Ingestion Latency and Errors for Grafana Cloud Traces in AWS Germany
Sağlayıcı güncellemeleri (2)
- İnceleniyor “We are investigating elevated latency and intermittent errors when ingesting traces for Grafana Cloud Traces in AWS Germany. Customers may see delayed trace ingestion and failed trace writes. Next update by 10:30 UTC.”
- Çözüldü “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.”
- ÇözüldüBaşlangıç: · Süre: 128 dk
Grafana Cloud: GCk6 App, erişim sorunu / kesinti
Sağlayıcının özgün başlığı: Some GCK6 App Project Pages are Failing to Load
Sağlayıcı güncellemeleri (2)
- Neden bulundu “We are currently investigating this issue impacting some GCK6 app project pages. We are in the process of providing a fix for this.”
- Çözüldü “This incident has been resolved.”
Sağlayıcının bu servis hakkında yayımladıkları ve kendi güncellemeleri (ifadeler yayımlandığı gibi tırnak içinde).
Kanıt
- Resmî
- Grafana Cloud Status ↗ ·
All Systems Operational· 19 Kas 01:21 GMT+3
Bu değerlendirme neden
- Sağlayıcı aktif olay bildirmiyor.
Kural seti assess-1. Aynı kanıt her zaman aynı sonucu verir.
Kanıt ve güncellik
Her kaynak ayrı ayrı: kim söylüyor, en son ne zaman gözlendi ve kullanılacak kadar yeni mi.
| Kaynak | Son gözlem | Yaş | Değerlendirmede kullanıldı |
|---|---|---|---|
| Resmî | 0 dk önce | Evet, güncel |
Teknik ayrıntılar
Etkilenen bileşenler (sağlayıcı)
Sağlayıcı sorunlu bileşen listelemiyor.