Signalfx Eu0 장애 기록

1. 2026년 8월 14일 AM 7:49 UTCinvestigating

   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일 AM 8:11 UTCmonitoring

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

3. 2026년 8월 14일 AM 8:17 UTCresolved

   The incident has been resolved.

1. 2026년 8월 7일 AM 8:30 UTCinvestigating

   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일 AM 9:07 UTCresolved

   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일 AM 10:45 UTCresolved

   1a PDT와 2:50a PDT 사이, 모든 GCP 통합은 GCP에서 클라우드 모니터링 데이터의 일부가되었습니다. 이 문제는 해결되었습니다. GCP Cloud Monitoring metrics를 사용하는 차트 및 검지기의 간격을 볼 수 있습니다. AWS CloudWatch 및 Azure Monitor 메트릭은 영향을받지 않습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 1일 PM 3:02 UTCresolved

   Tag Spotlight에 영향을 미치는 문제가 해결되었습니다. 고객은 6월 30일 오후 4시 30분 PM PT에서 Tag Spotlight에서 제한된 기능을 경험할 수 있습니다. 전체 기능은 7 월 7 : 20 AM PT에서 복원되었습니다. 1.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 26일 AM 7:28 UTCresolved

   최근 출시에 대한 회귀로 인해, 사용자가 APM TraceView 페이지에 로그 관련 내용에서 Log Observer 대신 APM TraceView로 다시 리디렉션되었습니다. US3 및 Gov를 제외한 모든 영역의 고객을 위한 Logs Correlation 경험에 영향을 미쳤습니다. 변화는 예상 탐색 경험을 복원하기 위해 거꾸로되었습니다. APM 및 Log Observer의 제품 가용성은 영향을받지 않았습니다. TraceView의 Logs Correlation 워크플로에 문제가 발생했습니다. 법인 시작 시간: 05:09 PDT, 6월 25, 2026 법인 종료 시간: 22:15 PDT, 6월 25, 2026

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 2일 PM 12:39 UTCinvestigating

   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일 PM 4:39 UTCresolved

   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일 AM 5:10 UTCinvestigating

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

2. 2026년 5월 20일 AM 5:46 UTCinvestigating

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

3. 2026년 5월 20일 AM 7:25 UTCinvestigating

   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일 AM 7:48 UTCinvestigating

   We are continuing to monitor this issue.

5. 2026년 5월 20일 AM 7:49 UTCinvestigating

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

6. 2026년 5월 20일 AM 8:03 UTCmonitoring

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

7. 2026년 5월 20일 PM 4:41 UTCresolved

   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일 AM 1:25 UTCinvestigating

   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일 AM 2:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 5월 20일 AM 3:19 UTCinvestigating

   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일 AM 3:41 UTCmonitoring

   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일 AM 3:54 UTCresolved

   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일 PM 7:17 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 7일 PM 7:19 UTCidentified

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

3. 2026년 5월 7일 PM 7:21 UTCresolved

   We are back to normal

1. 2026년 4월 25일 PM 3:31 UTCinvestigating

   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일 PM 4:27 UTCidentified

   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일 PM 6:33 UTCidentified

   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일 PM 10:19 UTCidentified

   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일 PM 11:45 UTCidentified

   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일 AM 12:52 UTCresolved

   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일 AM 12:57 UTCinvestigating

   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일 AM 1:20 UTCidentified

   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일 AM 2:00 UTCidentified

   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일 AM 2:31 UTCidentified

   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일 AM 2:53 UTCmonitoring

   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일 AM 3:10 UTCresolved

   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일 PM 6:31 UTCinvestigating

   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일 PM 6:44 UTCinvestigating

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

3. 2026년 4월 5일 PM 6:59 UTCinvestigating

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

4. 2026년 4월 5일 PM 7:14 UTCidentified

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

5. 2026년 4월 5일 PM 7:31 UTCidentified

   Teams continue working to implement the fix for this issue.

6. 2026년 4월 5일 PM 7:33 UTCmonitoring

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

7. 2026년 4월 5일 PM 7:46 UTCresolved

   This incident has been resolved.

1. 2026년 3월 23일 PM 11:31 UTCidentified

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

2. 2026년 3월 24일 AM 12:52 UTCidentified

   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일 PM 6:16 UTCidentified

   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일 AM 2:52 UTCresolved

   This incident has been resolved.

1. 2026년 3월 3일 PM 5:11 UTCmonitoring

   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일 PM 7:10 UTCresolved

   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일 AM 9:32 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 2월 27일 AM 10:35 UTCmonitoring

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

3. 2026년 2월 27일 AM 11:41 UTCresolved

   This incident has been resolved.

1. 2026년 2월 17일 PM 6:20 UTCinvestigating

   Customers may be experiencing errors while loading Data Management Page.

2. 2026년 2월 17일 PM 6:48 UTCidentified

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

3. 2026년 2월 17일 PM 7:18 UTCmonitoring

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

4. 2026년 2월 17일 PM 7:22 UTCresolved

   This incident has been resolved.

1. 2026년 1월 29일 PM 5:26 UTCresolved

   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일 PM 12:23 UTCinvestigating

   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일 PM 2:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 21일 PM 3:50 UTCidentified

   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일 PM 6:18 UTCidentified

   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일 PM 10:38 UTCidentified

   We are continuing to investigate this issue.

6. 2026년 1월 21일 PM 11:41 UTCidentified

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

7. 2026년 1월 22일 PM 2:02 UTCresolved

   The issue has been identified and resolved.

1. 2026년 1월 19일 PM 6:42 UTCinvestigating

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

2. 2026년 1월 19일 PM 6:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 19일 PM 7:23 UTCinvestigating

   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일 PM 8:07 UTCresolved

   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일 PM 3:23 UTCinvestigating

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

2. 2026년 1월 14일 PM 4:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 14일 PM 4:45 UTCidentified

   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일 PM 5:22 UTCidentified

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

5. 2026년 1월 14일 PM 6:28 UTCmonitoring

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

6. 2026년 1월 14일 PM 6:42 UTCresolved

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