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.
Posted Oct 23, 2026 - 14:12 PDT
Identified
We have identified that the degraded AWS CloudWatch integration is caused by an ongoing AWS disruption in the me-central-1 (UAE) region, including AWS CloudWatch and the Resource Groups Tagging API. Customers with AWS resources in this region may see missing or outdated resource tags on AWS metrics, and metric stream configuration changes may not be applied. Metric ingestion is not impacted. AWS has not provided a recovery timeline and recommends migrating to another region.
Posted Oct 23, 2026 - 02:15 PDT
Investigating
We are investigating an issue with the AWS CloudWatch integration. Some customers may see missing or outdated resource tags on AWS metrics, and metric stream configuration changes may not be applied. Metric ingestion is not impacted. We will provide an update as soon as more information is available.
Posted Oct 22, 2026 - 22:49 PDT
This incident affected: Splunk Cloud Integrations (Splunk CloudWatch Metric Streams).