Splunk Observability Cloud US2 Status

Resolved: We have confirmed the fix put in place by our engineering teams has successfully mitigated impact and functionality has been fully restored in the US2 region.

Monitoring: A fix has been implemented and we are currently monitoring the service recovery process.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics. We are currently working on identifying the root cause.

Resolved: We have confirmed the fix put in place by our engineering teams has successfully mitigated impact and functionality has been fully restored in the US2 region.

Monitoring: A fix has been implemented and we are currently monitoring the service recovery process.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics. We are currently working on identifying the root cause.

Resolved: We have confirmed the fix put in place by our engineering teams has successfully mitigated impact and functionality has been fully restored in the US2 region.

Monitoring: A fix has been implemented and we are currently monitoring the service recovery process.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics while also seeing degraded performance in charts. We continue working on identifying the root cause.

Investigating: We are currently dropping a subset of metrics. We are currently working on identifying the root cause.

Resolved: The outage impacting RUM MMS Data Drop has been resolved after internal engineering teams deployed a fix. All systems are operational and stable.

Thank you for your patience and understanding.

Identified: We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We will share an update once we have further information.

Identified: We are currently continuing to test the fix for the Real User Monitoring (RUM) metrics issue. We are thoroughly validating the mitigation to ensure it resolves the issue effectively and maintains system stability. We appreciate your ongoing patience and will provide further updates as testing progresses.

Identified: We are continuing to work on the fix. We expect to have further updates within the next hour. We appreciate your patience as we work diligently to resolve this issue and restore full service.

Investigating: The issue affecting Real User Monitoring (RUM) metrics has been identified. The fix is currently being implemented. We are actively working to restore full service and will provide further updates as progress continues.

Investigating: We are investigating an issue affecting Real User Monitoring (RUM) metrics across all realms. Customers may experience custom metric MTS quota limits being exceeded, resulting in metric data being dropped. RUM metric dimensions that were previously available may be missing.

Resolved: The issue affecting Real User Monitoring (RUM) custom charts and dashboards across multiple realms has been resolved. The fix has been deployed, and data is now flowing normally.

Monitoring: A fix for the issue affecting Real User Monitoring (RUM) charts and dashboards has been deployed and is being actively monitored across all realms; customers may now see data restored in charts and dashboards

Identified: We have identified an issue causing missing or incomplete data in Real User Monitoring (RUM) custom charts and dashboards across multiple realms. A fix is currently being rolled out and validated

Identified: A solution to address the issue causing missing or incomplete data in Real User Monitoring (RUM) charts and dashboards is currently being implemented. Our teams are actively working on deploying the fix and will continue to provide updates as progress is made

Identified: We have identified the cause of the issue resulting in missing or incomplete data in Real User Monitoring charts and dashboards. We are implementing a fix and will provide an update within 15 minutes.

Investigating: We are currently investigating an issue where RUM (Real User Monitoring) MMS data is being dropped, which may result in missing or incomplete data in charts and dashboards related to real user monitoring.

We are actively investigating and will provide updates as the situation develops.

Resolved: This incident has been resolved.

Identified: The issue has been identified as a regional cloud provider outage that is impacting our ability to maintain Synthetics testing in specific areas. Due to the uncertainty regarding the resolution timeline for this issue, we have made the decision to temporarily remove the following locations from our Synthetics testing network:

Bahrain Muscat UAE

We recommend reviewing your current test configurations and selecting alternative testing locations if necessary to ensure continued coverage.

Our engineering team is monitoring the situation closely. We will provide further updates as more information becomes available from the cloud provider. We apologize for any inconvenience this may cause and appreciate your patience as we work to maintain the reliability of our services.

Identified: The issue has been identified as an outage affecting the Bahrain region due to a Cloud Provider outage. We recommend that users temporarily run their Synthetic Monitoring tests from an alternative location while this issue is being resolved by the Cloud Provider.

Identified: The issue has been identified and is due to a Cloud Provider outage in the Bahrain region.