SignalFx US1 Outage History

Started May 08, 2026, 01:15 AM UTC· resolved May 08, 2026, 05:20 AM UTC

1. investigating May 08, 2026, 04:21 AM UTC

   We are currently investigating this issue.

2. investigating May 08, 2026, 04:22 AM UTC

   We are continuing to investigate this issue.

3. identified May 08, 2026, 05:46 AM UTC

   The issue has been identified and a fix is being implemented.

4. resolved May 08, 2026, 05:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 06, 2026, 01:00 PM UTC· resolved May 06, 2026, 07:25 PM UTC

1. investigating May 06, 2026, 02:44 PM UTC

   Charts for all customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

2. investigating May 06, 2026, 03:07 PM UTC

   Our teams are continue working to identify the cause and implement a fix.

3. investigating May 06, 2026, 03:36 PM UTC

   Our investigation remains ongoing, and there is no change in status at this time. We are continuing to prioritize this issue and will provide the next update in thirty minutes.

4. investigating May 06, 2026, 04:14 PM UTC

   Our teams are continuing their efforts to identify the root cause of this issue. There is no change in status to report at this time, but we are dedicating all necessary resources to reach a resolution. We will provide another update shortly.

5. investigating May 06, 2026, 04:31 PM UTC

   Update (8:50 AM PST): We have observed that charts are now loading successfully. While service is recovering, our teams remain on-site to investigate the root cause and ensure full system stability. We will continue to monitor performance closely.

6. investigating May 06, 2026, 05:02 PM UTC

   We are continuing to monitor the environment. There is no change in status at this time; our teams remain focused on resolving the remaining isolated issues.

7. investigating May 06, 2026, 05:31 PM UTC

   Our teams are continuing to monitor the environment and are actively working to fully resolve the issue.

8. investigating May 06, 2026, 05:44 PM UTC

   Update 10:30 PST: We are also investigating reports of login issues. Users may experience difficulty authenticating or accessing their accounts at this time.

9. identified May 06, 2026, 05:58 PM UTC

   The issue has been identified and a fix is being implemented.

10. monitoring May 06, 2026, 06:13 PM UTC

    A fix has been implemented and we are monitoring the results.

11. monitoring May 06, 2026, 07:08 PM UTC

    We are continuing to monitor the environment to ensure full remediation.

12. resolved May 06, 2026, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Apr 25, 2026, 05:01 PM UTC· resolved Apr 26, 2026, 12:55 AM UTC

1. investigating Apr 25, 2026, 05:01 PM UTC

   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.

2. identified Apr 25, 2026, 05:02 PM UTC

   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.

3. identified Apr 25, 2026, 06:37 PM UTC

   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.

4. identified Apr 25, 2026, 10:26 PM UTC

   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.

5. identified Apr 25, 2026, 11:48 PM UTC

   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.

6. resolved Apr 26, 2026, 12:55 AM UTC

   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.

Read the full incident report →

Started Apr 17, 2026, 04:20 PM UTC· resolved Apr 18, 2026, 04:02 AM UTC

1. investigating Apr 17, 2026, 05:52 PM UTC

   Charts, dashboards and detectors may load slowly. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

2. identified Apr 17, 2026, 06:07 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Apr 17, 2026, 06:07 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Apr 17, 2026, 06:07 PM UTC

   We have identified the issue. The performance is improving. We will continue to monitor

5. identified Apr 17, 2026, 06:15 PM UTC

   The issue has been identified and a fix is being implemented.

6. monitoring Apr 17, 2026, 06:44 PM UTC

   A fix has been implement and we are currently monitoring the environment.

7. monitoring Apr 17, 2026, 07:49 PM UTC

   We are continuing to monitor the environment.

8. identified Apr 17, 2026, 08:11 PM UTC

   We are moving the updates to an "Identified" status as we continue to address persistent performance issues affecting charts, dashboards, and detectors. While we are actively monitoring the environment and have implemented mitigation measures, some customers may still experience slow load times or intermittent failures. We are actively working to stabilize the environment and we will continue to provide updates as we make progress toward a full resolution.

9. monitoring Apr 17, 2026, 09:10 PM UTC

   A fix has been implemented and we are currently monitoring the results to ensure system stability. We expect this monitoring period to last up to 4 hours. During this time, performance for charts, dashboards, and detectors should continue to improve. We will provide another update once we have confirmed that the environment has fully recovered.

10. monitoring Apr 18, 2026, 01:40 AM UTC

    We are still under monitoring following the implementation of the fix to ensure stability. We will continue to track performance improvements for charts, dashboards, and detectors and will keep you updated as we confirm the environment has fully recovered.

11. resolved Apr 18, 2026, 04:02 AM UTC

    This issue has been resolved. We have confirmed that system stability has been restored, and performance for charts, dashboards, and detectors has returned to normal levels. Thank you.

Read the full incident report →

Started Mar 26, 2026, 02:18 AM UTC· resolved Mar 26, 2026, 04:46 AM UTC

1. investigating Mar 26, 2026, 02:18 AM UTC

   A degradation in the performance of the Splunk APM metrics processing pipeline is causing Monitoring MetricSets to be delayed by more than five minutes. Trace data ingest is not impacted, but service, endpoint and workflow dashboards, and other charts and detectors built from Monitoring MetricSets are impacted.

2. investigating Mar 26, 2026, 02:20 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 26, 2026, 02:21 AM UTC

   We are continuing to investigate this issue.

4. investigating Mar 26, 2026, 02:45 AM UTC

   We are continuing to investigate the performance degradation affecting Splunk APM Monitoring MetricSets. While trace data ingestion remains fully operational, users may experience delays of more than five minutes in dashboard, chart, and detector data. Our team is actively working to restore normal processing speeds, and we will provide further updates as more information becomes available

5. investigating Mar 26, 2026, 03:18 AM UTC

   We are actively working to resolve the delay affecting trace monitoring metrics. While trace data ingestion remains unaffected, please note that dashboards, charts, and detectors may experience delays of over five minutes. We are working to restore normal latency and will provide further updates as they become available.

6. monitoring Mar 26, 2026, 03:56 AM UTC

   Recovery efforts for trace monitoring metrics in the US1 region are progressing, with system lag steadily decreasing. We continue to monitor the service closely as it returns to normal performance levels. No data loss has occurred.

7. monitoring Mar 26, 2026, 04:26 AM UTC

   We are continuing our recovery efforts for trace monitoring metrics in the US1 region. As system lag steadily decreases, we remain engaged in our standard monitoring procedures to ensure a full return to service. No data loss has occurred.

8. resolved Mar 26, 2026, 04:46 AM UTC

   The issue impacting trace monitoring metrics in the US1 region is now resolved. All the APM monitoring sets are now fully operational and performing as expected. We confirm that no data was lost. Thank you for your patience.

Read the full incident report →

Started Mar 24, 2026, 01:54 AM UTC· resolved Mar 24, 2026, 03:02 AM UTC

1. investigating Mar 24, 2026, 01:54 AM UTC

   We are currently investigating the issue. New APM Data is delayed by approximately 20 minutes. There is no data loss.

2. investigating Mar 24, 2026, 02:37 AM UTC

   Investigation is in progress. Our team is working on mitigation steps and will provide further update as soon as possible

3. investigating Mar 24, 2026, 02:50 AM UTC

   Mitigation steps are in progress, and the situation is improving. We are continuing to monitor and will provide further updates as soon as possible

4. resolved Mar 24, 2026, 03:02 AM UTC

   The issue has been resolved and services have returned to normal operation. Thank you for your patience.

Read the full incident report →

Started Mar 23, 2026, 11:28 PM UTC· resolved Apr 25, 2026, 02:55 AM UTC

1. identified Mar 23, 2026, 11:28 PM UTC

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

2. identified Mar 24, 2026, 12:57 AM UTC

   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.

3. identified Mar 24, 2026, 06:19 PM UTC

   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.

4. resolved Apr 25, 2026, 02:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 08:32 AM UTC· resolved Mar 05, 2026, 07:24 PM UTC

1. investigating Mar 02, 2026, 08:32 AM UTC

   Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

2. monitoring Mar 02, 2026, 08:33 AM UTC

   Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

3. monitoring Mar 02, 2026, 08:22 PM UTC

   Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

4. monitoring Mar 03, 2026, 05:15 PM UTC

   Cisco is aware of an ongoing cloud service provider outage in the Middle East affecting multiple cloud offers and services. As a result, O11y customers ingesting metrics and/or metadata from impacted regions may experience significant delays and/or interruptions in data delivery. Customers who do not rely on metrics or metadata from these regions are not affected. We will continue to closely monitor this issue as it unfolds.

5. resolved Mar 05, 2026, 07:24 PM UTC

   Monitoring over the past several days has not identified any impact to Splunk Observability Cloud services related to the previously reported cloud service provider disruption in the Middle East. Splunk Observability Cloud services continue to operate normally. We will continue to monitor the situation and will notify customers if conditions change.

Read the full incident report →

Started Feb 26, 2026, 03:00 PM UTC· resolved Feb 26, 2026, 08:25 PM UTC

1. investigating Feb 26, 2026, 03:00 PM UTC

   We are currently investigating this issue.

2. investigating Feb 26, 2026, 04:05 PM UTC

   We are currently investigating an issue causing failures in analytics jobs and impacting chart and detector functionality in the UI. Customers may experience degraded performance or data loading issues. Team is actively working to identify mitigation to restore full functionality. We will provide further updates as more information becomes available.

3. identified Feb 26, 2026, 05:00 PM UTC

   We have identified the cause of the issue impacting analytics job processing and UI functionality. Issue was triggered following a ZooKeeper master node restart during scheduled maintenance, which led to service instability and job failures. Recovery actions are in progress, including restarting affected services and stabilizing the environment. Customers may continue to experience degraded performance or data loading issues while mitigation steps are being completed. We will provide further updates as restoration progresses.

4. identified Feb 26, 2026, 06:13 PM UTC

   We are continuing to make progress restoring analytics job processing and UI functionality. Affected services have been restarted. While recovery is progressing, customers may still experience data delays due to backlog processing. Team is actively working on expediting recovery progress.

5. identified Feb 26, 2026, 07:01 PM UTC

   We are continuing restoring analytics job processing and overall UI functionality. The majority of affected services have been successfully restarted, and rolling restarts for remaining components are currently underway. Customers may continue to experience data delays as analytics and detector services process backlogs. We will provide additional updates as stability and performance are fully restored.

6. monitoring Feb 26, 2026, 07:44 PM UTC

   Recovery is complete. Charts and detectors are now loading with 100% successful displayed data. The team are actively monitoring the situation to ensure of no further issues.

7. monitoring Feb 26, 2026, 08:25 PM UTC

   We are continuing to monitor for any further issues.

8. resolved Feb 26, 2026, 08:25 PM UTC

   We have completed the remediation actions and have successfully resolved the incident. At this time, no further action is required of you.

Read the full incident report →

Started Feb 17, 2026, 06:25 PM UTC· resolved Feb 17, 2026, 09:56 PM UTC

1. investigating Feb 17, 2026, 06:25 PM UTC

   Customers may be experiencing errors while loading Data Management Page.

2. identified Feb 17, 2026, 06:50 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Feb 17, 2026, 07:28 PM UTC

   Our teams are actively working to restore services. Some customers may be seeing improvement at this time. We are committed to resolving the issue as quickly as possible and will provide updates as progress is made.

4. identified Feb 17, 2026, 08:05 PM UTC

   Restoration is still in progress. Retrying to load the Data Management Page should yield positive results for some customers. Our teams continue to work diligently to resolve the issue and will provide further updates as progress is made.

5. identified Feb 17, 2026, 08:41 PM UTC

   Restoration is mostly complete. Most customer attempts to load the Data Management Page should be successful. Our teams continue to monitor the situation and appreciate your patience as we finalize the resolution. Further updates will be provided if necessary.

6. monitoring Feb 17, 2026, 09:50 PM UTC

   A fix has been implemented and we are monitoring the results.

7. resolved Feb 17, 2026, 09:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 28, 2026, 09:32 PM UTC· resolved Jan 29, 2026, 04:18 AM UTC

1. investigating Jan 28, 2026, 09:32 PM UTC

   We are investigating a major outage of the Splunk APM web application, detected starting at 12:40pm PT. We will provide an update as soon as possible.

2. investigating Jan 28, 2026, 09:33 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 28, 2026, 10:05 PM UTC

   We are investigating an issue affecting the Splunk APM interface, first detected at approximately 12:40 PM PT. Users may see APM dashboards and service views not loading. Our teams are actively working to resolve the issue. We will share updates as more information becomes available.

4. investigating Jan 28, 2026, 10:41 PM UTC

   We are continuing to investigate an ongoing issue impacting Splunk APM metrics visibility, where customers may experience missing or incomplete APM data, including Overview dashboards, service-level metrics, Success Rate and Success Rate SLI graphs, and custom dashboards showing no data.

5. identified Jan 28, 2026, 11:05 PM UTC

   We have identified an issue impacting Splunk APM metrics visibility, where customers may experience missing or incomplete APM data, including Overview dashboards, service-level metrics, Success Rate and Success Rate SLI graphs, and custom dashboards showing no data. Our engineering teams are actively implementing the fix.

6. identified Jan 28, 2026, 11:41 PM UTC

   We are actively implementing a fix to restore Splunk APM metrics by rolling back recent changes in a controlled manner. The rollback is being closely monitored to ensure stability as each component is completed. We will provide the next update once the rollback is complete.

7. identified Jan 29, 2026, 12:18 AM UTC

   We are actively implementing a fix to restore Splunk APM metrics and dashboards by rolling back recent changes in a controlled manner. The rollback is being closely monitored to ensure stability as each component is completed. We will provide the next update once the rollback is complete.

8. identified Jan 29, 2026, 01:32 AM UTC

   We are actively implementing a fix to restore Splunk APM metrics and dashboards by rolling back recent changes in a controlled manner. The rollback is being closely monitored to ensure stability as each component is completed. We will provide the next update once the rollback is complete.

9. identified Jan 29, 2026, 02:45 AM UTC

   We are continuing to work on implementing a fix to restore Splunk APM metrics and dashboards up to date. The rollback is being closely monitored. We will provide the next update once the rollback is completed.

10. resolved Jan 29, 2026, 04:18 AM UTC

    We have completed the rollback of the recent change affecting Splunk APM metrics and dashboards successfully. After closely monitoring the environment to verify a full recovery, our teams have confirmed that all services are functioning as expected. This incident has been Resolved.

Read the full incident report →

Started Jan 23, 2026, 11:30 AM UTC· resolved Jan 23, 2026, 11:30 AM UTC

1. resolved Jan 29, 2026, 05:40 PM UTC

   Between 2026-01-23 at 3:30 AM PT and 2026-01-26 at 1:00 AM PT, metrics fetching from AWS Cloudwatch was degraded.

Read the full incident report →

Started Jan 21, 2026, 12:24 PM UTC· resolved Jan 22, 2026, 02:01 PM UTC

1. investigating Jan 21, 2026, 12:24 PM UTC

   Starting at 03:12 AM Pacific Time, customers using Azure Entra ID for Single Sign-On (SSO) may be unable to log in to Splunk Observability. We are actively investigating now.

2. investigating Jan 21, 2026, 01:50 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 21, 2026, 02:26 PM UTC

   We are continuing to investigate this issue.

4. identified Jan 21, 2026, 03:49 PM UTC

   We have identified a workaround that can help restore access while we continue investigating the root cause. Workaround Organizations with SSO enabled have a local administrator account that can sign in without SSO. Administrators can use this account to: 1. Sign in to Splunk Observability using email and password (local login) 2. Invite affected users to the organization 3. Enable invited users to sign in using email and password (local login) as a temporary alternative We have validated this process internally and confirmed it is working as expected. Next step * If you need assistance applying this workaround, please contact Splunk Customer Support. We will continue to monitor the situation and provide updates as additional information becomes available.

5. identified Jan 21, 2026, 06:18 PM UTC

   Our engineering teams continue investigating this service disruption in search of a permanent solution for the SSO Authentication issues. The workaround mentioned in our previous update remains as the best course of action to mitigate immediate impact.

6. identified Jan 21, 2026, 07:17 PM UTC

   We are continuing to investigate this issue.

7. identified Jan 21, 2026, 10:39 PM UTC

   We are continuing to investigate this issue.

8. identified Jan 21, 2026, 11:41 PM UTC

   We are continuing to investigate this issue. Please refer to the Workaround posted in our update from 15:50 UTC.

9. resolved Jan 22, 2026, 02:01 PM UTC

   The issue has been identified and resolved.

Read the full incident report →

Started Jan 19, 2026, 06:47 PM UTC· resolved Jan 19, 2026, 08:10 PM UTC

1. investigating Jan 19, 2026, 06:47 PM UTC

   We are currently investigating an issue that may result in the Hosts Infra Navigator View from loading.

2. investigating Jan 19, 2026, 07:26 PM UTC

   We are continuing to investigate this issue. We have confirmed that the issue does not impact Datapoint Ingest at this time.

3. resolved Jan 19, 2026, 08:10 PM UTC

   Engineering teams have identified the root cause and completed recovery actions that caused a degradation of service to the Hosts Infra Navigator View.

Read the full incident report →

Started Jan 16, 2026, 06:30 AM UTC· resolved Jan 16, 2026, 06:05 PM UTC

1. investigating Jan 16, 2026, 04:27 PM UTC

   The issue started from 10:30 PM PST on January 15, 2026. The root cause is identified and a fix is in development. Only monitoring metric sets and org metrics data ingestion is delayed, there is no data being dropped.

2. identified Jan 16, 2026, 04:27 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Jan 16, 2026, 06:05 PM UTC

   This incident has been resolved. On further investigation, the ingestion delay for monitoring metric sets and org metrics was only 2 minutes during the incident.

Read the full incident report →

Started Jan 14, 2026, 03:22 PM UTC· resolved Jan 14, 2026, 06:45 PM UTC

1. investigating Jan 14, 2026, 03:22 PM UTC

   Users login with Splunk Unified Identity may have issues accessing Splunk Observability and Log Observer.

2. investigating Jan 14, 2026, 04:04 PM UTC

   We are continuing to investigate this issue.

3. identified Jan 14, 2026, 04:45 PM UTC

   Splunk Unified Identity issue has been identified. This will only affect new login session using Splunk Unified Identity, existing login sessions are unaffected. A fix is in progress.

4. identified Jan 14, 2026, 05:26 PM UTC

   Teams are continuing to work diligently, and progress is being made in applying the fix.

5. monitoring Jan 14, 2026, 06:28 PM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Jan 14, 2026, 06:45 PM UTC

   The incident has been resolved; however, customers may need to clear their browser cache in order to successfully log in.

Read the full incident report →

Started Dec 13, 2025, 03:33 AM UTC· resolved Dec 13, 2025, 03:38 AM UTC

1. monitoring Dec 13, 2025, 03:33 AM UTC

   0.4% of datapoints dropped overall at peak mostly affecting new MTS creations. The issue is no longer occurring and we are monitoring.

2. resolved Dec 13, 2025, 03:38 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 04:00 AM UTC· resolved Nov 24, 2025, 04:00 AM UTC

1. resolved Nov 24, 2025, 05:39 AM UTC

   From 9:08 PT – 9:12 PT we were unable to create some MTS datapoints. We were able to quickly resolve the issue and are monitoring our systems closely.

Read the full incident report →

Started Nov 19, 2025, 09:12 PM UTC· resolved Nov 19, 2025, 09:35 PM UTC

1. investigating Nov 19, 2025, 09:12 PM UTC

   We are currently investigating the issue.

2. investigating Nov 19, 2025, 09:14 PM UTC

   Metrics are now loading intermittently. We are working to resolve the issue.

3. monitoring Nov 19, 2025, 09:25 PM UTC

   We have identified the cause and fixed it. We are now closely monitoring the issue and ensuring there was no impact to ingestion.

4. resolved Nov 19, 2025, 09:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 10:37 PM UTC· resolved Nov 08, 2025, 02:41 AM UTC

1. investigating Nov 07, 2025, 10:37 PM UTC

   We are investigating a reported issue indicating slowness and degraded performance within the US1 region. As a result, some customers may experience degraded UI performance when using charts, detectors, and running searches. Ingestion is not impacted.

2. investigating Nov 07, 2025, 11:13 PM UTC

   We are still investigating the reported issue of slowness and degraded performance in the US1 region. Customers will continue experiencing degraded UI performance with charts, detectors, and searches. Please note that ingestion is not affected.

3. investigating Nov 07, 2025, 11:51 PM UTC

   We continue investigating the reported issue of slowness and degraded performance in the US1 region. Our engineering team is taking appropriate actions to mitigate impact as quickly as possible. Customers will continue experiencing degraded UI performance with charts, detectors, and searches. Please note that ingestion is not affected.

4. investigating Nov 08, 2025, 12:37 AM UTC

   We continue investigating the reported issue of slowness and degraded performance in the US1 region. Our engineering team is taking appropriate actions to mitigate impact as quickly as possible. Customers will continue experiencing degraded UI performance with charts, detectors, and searches. Please note that ingestion is not affected.

5. investigating Nov 08, 2025, 01:08 AM UTC

   We are still investigating the reported issue of slowness and degraded performance in the US1 region. Customers will continue experiencing degraded UI performance with charts, detectors, and searches. Please note that ingestion is not affected.

6. investigating Nov 08, 2025, 01:47 AM UTC

   We are still investigating the reported issue of slowness and degraded performance in the US1 region. Customers will continue experiencing degraded UI performance with charts, detectors, and searches. Please note that ingestion is not affected.

7. monitoring Nov 08, 2025, 01:58 AM UTC

   Service restoration is underway following the identification and mitigation of a high-consumption process. You may experience temporary issues while we fully restore functionality. Thank you for your patience.

8. resolved Nov 08, 2025, 02:41 AM UTC

   The Observability services in US1 region have been fully restored and are now operational. We apologize for any inconvenience caused during the outage. Thank you for your patience.

Read the full incident report →

Started Nov 05, 2025, 02:14 PM UTC· resolved Nov 05, 2025, 05:54 PM UTC

1. investigating Nov 05, 2025, 02:14 PM UTC

   We are investigating a partial outage of the Splunk Observability Cloud web application on the US1 realm. Customers may experience slowness or errors loading various UI components, including APM, Alerts, and Detectors. Trace data ingest is not impacted at this time. We will provide an update as soon as possible.

2. identified Nov 05, 2025, 04:39 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Nov 05, 2025, 04:49 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 05, 2025, 05:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 08:29 AM UTC· resolved Oct 20, 2025, 11:46 PM UTC

1. investigating Oct 20, 2025, 08:29 AM UTC

   Multiple Splunk Observability cloud services are impacted due to an ongoing AWS outage in the region. https://health.aws.amazon.com/health/status?path=open-issues

2. investigating Oct 20, 2025, 02:42 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 20, 2025, 03:44 PM UTC

   We are continuing to see degraded performance across all services due to ongoing AWS outage. We are not receiving Datapoints from us-east-1 AWS intermittently due the same ongoing AWS outage.

4. investigating Oct 20, 2025, 04:15 PM UTC

   We are continuing to investigate this issue.

5. investigating Oct 20, 2025, 05:05 PM UTC

   Due to ongoing AWS outage, we are continuing to see degraded performance Splunk Cloud Integration services. We are not receiving Datapoints from AWS us-east-1 intermittently.

6. investigating Oct 20, 2025, 06:15 PM UTC

   Due to ongoing AWS outage, we are continuing to see degraded performance for Splunk Cloud Integration services. We are not receiving Datapoints from AWS us-east-1 intermittently.

7. identified Oct 20, 2025, 07:29 PM UTC

   Due to ongoing AWS outage, we are continuing to see degraded performance for Splunk Cloud Integration services. We are not receiving Datapoints from AWS us-east-1 intermittently.

8. identified Oct 20, 2025, 08:35 PM UTC

   As AWS continues its recovery efforts in the US-EAST-1 region, users in this region may still experience intermittent issues. We are closely monitoring AWS updates and will provide additional status information as it becomes available.

9. monitoring Oct 20, 2025, 10:13 PM UTC

   As AWS continues its recovery efforts in the US-EAST-1 region, users in this region may still experience intermittent issues. We are closely monitoring AWS updates and will provide additional status information as it becomes available.

10. resolved Oct 20, 2025, 11:46 PM UTC

    AWS has reported that the earlier issues impacting services in the US-EAST-1 (N. Virginia) region have been fully resolved as of 3:01 PM PDT. All impacted services have returned to normal operations. Users may continue to observe minor latency or delays as AWS and dependent services complete backlog processing and return to standard performance levels. We understand the criticality of your services and appreciate your patience.

Read the full incident report →

Started Oct 17, 2025, 06:28 PM UTC· resolved Oct 18, 2025, 05:14 AM UTC

1. investigating Oct 17, 2025, 06:28 PM UTC

   Chart and Dashboard Save operations are running into intermittent errors on UI.

2. identified Oct 17, 2025, 10:13 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Oct 18, 2025, 03:33 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Oct 18, 2025, 05:14 AM UTC

   This incident has been resolved.

Read the full incident report →