Signalfx Eu0 中断历史

1. 2026年8月14日 UTC 07:49investigating

   A degradation in the performance of the Splunk APM data ingestion pipeline is causing the processing and storage of raw trace data to be delayed by more than five minutes. No data is being lost at this time and MetricSets are not impacted but the most recent data may not be available in trace search results.

2. 2026年8月14日 UTC 08:11monitoring

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

3. 2026年8月14日 UTC 08:17resolved

   The incident has been resolved.

1. 2026年8月7日 UTC 08:30investigating

   A degradation in the performance of the Splunk APM data ingestion pipeline is causing the processing and storage of raw trace data to be delayed by more than five minutes. No data is being lost at this time and MetricSets are not impacted but the most recent data may not be available in trace search results.

2. 2026年8月7日 UTC 09:07resolved

   The degradation in the Splunk APM data ingestion pipeline has been mitigated and is now resolved. Processing and storage of raw trace data has recovered, and recent data is available in trace search results. No data was lost, and MetricSets were not impacted.

1. 2026年7月8日 UTC 10:45resolved

   1a PDT至2:50a PDT之间,任何具有"全部(动态)上市项目"设置的GCP集成,都有部分来自GCP的云监测数据被放弃. 这个问题已经得到解决。 客户可能会看到使用受影响全球氯化石蜡云监测测量仪的图表和探测器存在漏洞。 AWS Cloud Watch和Azure Monitor的度量衡没有受到影响.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 15:02resolved

   我们确认,影响Tag Spotlight的问题已经得到解决。 从6月30日4:30 PM PT开始,客户在Tag Spotlight内部的功能可能有限. 全功能于7月1日7:20AM PT恢复.

自动翻译自官方事件更新。

1. 2026年6月26日 UTC 07:28resolved

   由于最近一期的回放,用户从APM TraceView页面上的日志相关内容浏览到Log Observation,转回APM TraceView. 这影响了除美国3号和政府外所有领域的客户的日志关联经验。 这一变化已经恢复,以恢复预期的导航经验。 APM和Log Observer的产品可得性没有受到影响;这个问题仅限于TraceView的Logs相关工作流程。 事发时间:05:09 PDT,2026年6月25日 事件结束时间:22:15 PDT,2026年6月25日

自动翻译自官方事件更新。

1. 2026年6月2日 UTC 12:39investigating

   We are investigating delays in processing Splunk Observability Synthetic Monitoring test results for a small subset of customers. Tests are still running, but metrics may be delayed until the issue is resolved.

2. 2026年6月2日 UTC 16:39resolved

   We have identified and remediated an issue affecting synthetic test result ingestion for a subset of customers. We apologize for any inconvenience this may have caused and thank you for your patience. Time range of impact: June 1 20:00 UTC - June 2 15:30 UTC

1. 2026年5月20日 UTC 05:10investigating

   Customers may be experiencing delays in some charts and detectors. We are investigating and will provide an update shortly.

2. 2026年5月20日 UTC 05:46investigating

   We are continuing to investigate this issue and will provide another update shortly.

3. 2026年5月20日 UTC 07:25investigating

   We are continuing to investigate this issue. We will provide an update shortly, or as soon as there is a change in progress.

4. 2026年5月20日 UTC 07:48investigating

   We are continuing to monitor this issue.

5. 2026年5月20日 UTC 07:49investigating

   The charts are up and working now but we will continue to monitor

6. 2026年5月20日 UTC 08:03monitoring

   The charts are up and working now but we will continue to monitor.

7. 2026年5月20日 UTC 16:41resolved

   After monitoring the status for more than 8 hours and confirming that issue is not happening anymore, the case is closed.

1. 2026年5月20日 UTC 01:25investigating

   We are investigating delays in processing chart load times, validating if there is any impact to the alerts. Currently there is no impact to other areas of the platform.

2. 2026年5月20日 UTC 02:19investigating

   We are continuing to investigate this issue.

3. 2026年5月20日 UTC 03:19investigating

   We are continuing to investigate delayed chart load times in Splunk Observability Cloud. We will provide an update shortly, or as soon as there is a change in progress.

4. 2026年5月20日 UTC 03:41monitoring

   A fix has been implemented. We are monitoring the service to confirm full recovery. We will provide another update once the issue is fully resolved.

5. 2026年5月20日 UTC 03:54resolved

   This incident involving delayed chart load times in Splunk Observability Cloud has been resolved. The team implemented a fix and monitored the service to confirm recovery.

1. 2026年5月7日 UTC 19:17investigating

   We are currently investigating this issue.

2. 2026年5月7日 UTC 19:19identified

   we have identified the root cause, working on fixing the solution

3. 2026年5月7日 UTC 19:21resolved

   We are back to normal

1. 2026年4月25日 UTC 15:31investigating

   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. 2026年4月25日 UTC 16:27identified

   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. 2026年4月25日 UTC 18:33identified

   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. 2026年4月25日 UTC 22:19identified

   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. 2026年4月25日 UTC 23:45identified

   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. 2026年4月26日 UTC 00:52resolved

   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.

1. 2026年4月25日 UTC 00:57investigating

   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.

2. 2026年4月25日 UTC 01:20identified

   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.

3. 2026年4月25日 UTC 02:00identified

   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

4. 2026年4月25日 UTC 02:31identified

   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

5. 2026年4月25日 UTC 02:53monitoring

   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

6. 2026年4月25日 UTC 03:10resolved

   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.

1. 2026年4月5日 UTC 18:31investigating

   We are investigating a major outage of Splunk cloud involving logging in via Unified Identity. Ingest is not impacted at this time. We will provide an update as soon as possible. Splunk Log Observer may not be available for unified identity customers.

2. 2026年4月5日 UTC 18:44investigating

   Our team is currently working to resolve an issue impacting Unified Identity services.

3. 2026年4月5日 UTC 18:59investigating

   Investigation into the root cause of the Unified Identity issue is ongoing.

4. 2026年4月5日 UTC 19:14identified

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

5. 2026年4月5日 UTC 19:31identified

   Teams continue working to implement the fix for this issue.

6. 2026年4月5日 UTC 19:33monitoring

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

7. 2026年4月5日 UTC 19:46resolved

   This incident has been resolved.

1. 2026年3月23日 UTC 23:31identified

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

2. 2026年3月24日 UTC 00:52identified

   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. 2026年3月24日 UTC 18:16identified

   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. 2026年4月25日 UTC 02:52resolved

   This incident has been resolved.

1. 2026年3月3日 UTC 17:11monitoring

   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. 2026年3月5日 UTC 19:10resolved

   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.

1. 2026年2月27日 UTC 09:32investigating

   We are currently investigating this issue.

2. 2026年2月27日 UTC 10:35monitoring

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

3. 2026年2月27日 UTC 11:41resolved

   This incident has been resolved.

1. 2026年2月17日 UTC 18:20investigating

   Customers may be experiencing errors while loading Data Management Page.

2. 2026年2月17日 UTC 18:48identified

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

3. 2026年2月17日 UTC 19:18monitoring

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

4. 2026年2月17日 UTC 19:22resolved

   This incident has been resolved.

1. 2026年1月29日 UTC 17:26resolved

   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.

1. 2026年1月21日 UTC 12:23investigating

   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. 2026年1月21日 UTC 14:26investigating

   We are continuing to investigate this issue.

3. 2026年1月21日 UTC 15:50identified

   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.

4. 2026年1月21日 UTC 18:18identified

   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.

5. 2026年1月21日 UTC 22:38identified

   We are continuing to investigate this issue.

6. 2026年1月21日 UTC 23:41identified

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

7. 2026年1月22日 UTC 14:02resolved

   The issue has been identified and resolved.

1. 2026年1月19日 UTC 18:42investigating

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

2. 2026年1月19日 UTC 18:44investigating

   We are continuing to investigate this issue.

3. 2026年1月19日 UTC 19:23investigating

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

4. 2026年1月19日 UTC 20:07resolved

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

1. 2026年1月14日 UTC 15:23investigating

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

2. 2026年1月14日 UTC 16:06investigating

   We are continuing to investigate this issue.

3. 2026年1月14日 UTC 16:45identified

   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 and this incident is expected to be resolved in the next 3-5 hours.

4. 2026年1月14日 UTC 17:22identified

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

5. 2026年1月14日 UTC 18:28monitoring

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

6. 2026年1月14日 UTC 18:42resolved

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