Observability
28 providers, each with the state its own status page reports.
Providers
0 with open incidents
- AxiomOperational
- Better StackOperational
- BugsnagOperational
- ChecklyOperational
- CoralogixOperational
- DatadogOperational
- DynatraceOperational
- Elastic ObservabilityOperational
- FullStoryOperational
- Grafana CloudOperational
- Grafana IRMOperational
- HoneycombOperational
- HotjarOperational
- incident.ioOperational
- InstatusOperational
- ServiceNow Cloud ObservabilityOperational
- LogglyOperational
- LogRocketOperational
- Logz.ioOperational
- New RelicOperational
- OpsgenieOperational
- RollbarOperational
- RootlyOperational
- SentryOperational
- SigNoz CloudOperational
- StatusCakeOperational
- Atlassian StatuspageOperational
- Sumo LogicOperational
Recent incidents
Last 14 days, newest first, open ones on top.
- Connectivity disruption for AWS Bahrain (me-south-1)
- SentryDegradedEU region replay ingestion latency
- CoralogixOperationalLog threshold alerts not evaluating on EU2 region
- Sumo LogicDegradedProblem with Cloud SIEM Processing in North America 2 (US2)
- Grafana CloudOperationalCloud Logs writes - Elevated latency and error rates in prod-eu-central-0
- Grafana CloudDegradedMimir query unexpected response with status code 500
Grafana Cloud says Mimir queries were returning an unexpected response with status code 500 when querying older data. The provider says a fix has been implemented and it is monitoring the results, with the incident in a monitoring state.
- Sumo LogicDegradedProblem with Cloud SIEM Processing in North America 2 (US2)
- DatadogDegradedDelayed Traces in APM
- Grafana CloudOperationalSynthetic Monitoring — Jakarta Public Probe Degradation
Grafana Cloud says a network issue at its Jakarta public probe raised DNS check failures from ~0.3% to ~15% between 08:31 and 09:17 UTC on 6 November 2026. The incident is resolved, and TCP checks and other probe locations were not affected.
- Grafana CloudDegradedOctober usage report visualization issue
Grafana Cloud says an issue with its billing metrics exporter caused October usage to show as 0 in its cost management app. The provider says billing was not affected, and the incident is now marked resolved after work to backfill the missing data.