Performance degradation with apm code profiling
Last updateresolvedOct 27 · 21:52 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
checked Oct 30, 2026 2:27 AM UTC · Splunk Observability Cloud US1's official status page
Splunk Observability Cloud US1 is up and running.
Splunk Observability Cloud US1 is currently operational with all systems functioning normally.
All components operational
Be the first to know
Statusfield watches Splunk Observability Cloud US1 alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
Splunk Observability Cloud US1 incident history
10 reports published by Splunk Observability Cloud US1 in the last 30 days
When Splunk Observability Cloud US1 breaks, it is typically resolved in 2h 35m — median across 4 resolved incidents over 30 days.
October 27, 2026
Performance degradation with apm code profiling
Last updateResolvedOct 27 · 21:52 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
October 23, 2026
Degraded AWS CloudWatch Metadata Integration
Last updateresolvedOct 23 · 21:12 UTC
Splunk has confirmed that the degraded AWS CloudWatch integration in the me-central-1 (UAE) region is caused by an ongoing AWS regional disruption outside of Splunk's control. AWS has not provided a recovery timeline and recommends migrating affected resources to another region. Metric ingestion is not impacted. We are identifying affected customers and will reach out individually to discuss next steps. If you have immediate concerns, please contact your account team.
Reported by Splunk Observability Cloud US1 on their status page.
Degraded AWS CloudWatch Metadata Integration
Last updateResolvedOct 23 · 21:12 UTC
Splunk has confirmed that the degraded AWS CloudWatch integration in the me-central-1 (UAE) region is caused by an ongoing AWS regional disruption outside of Splunk's control. AWS has not provided a recovery timeline and recommends migrating affected resources to another region. Metric ingestion is not impacted. We are identifying affected customers and will reach out individually to discuss next steps. If you have immediate concerns, please contact your account team.
Reported by Splunk Observability Cloud US1 on their status page.
October 22, 2026
Splunk APM Trace Data Ingestion Delayed
Last updateresolvedOct 22 · 22:05 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
October 15, 2026
Splunk Observability Cloud Web Interface Degradation
Last updateresolvedOct 15 · 21:20 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
Splunk Observability Cloud Web Interface Degradation
Last updateResolvedOct 15 · 21:20 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
October 11, 2026
Charts not Loading for Some Customers
Last updateresolvedOct 11 · 05:34 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
October 3, 2026
Splunk Observability Synthetic Metric may be missing
Last updateresolvedOct 3 · 03:18 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.
Splunk Observability Synthetic Metric may be missing
Last updateResolvedOct 3 · 03:18 UTC
This incident has been resolved.
Reported by Splunk Observability Cloud US1 on their status page.