Störungsverlauf von Signalfx Eu0

1. 15. Oktober 2026 um 19:02 UTCinvestigating

   Wir untersuchen eine Verschlechterung der Splunk Observability Cloud-Webanwendung für einige Kunden. Die Datenaufnahme ist derzeit nicht betroffen. Wir werden so schnell wie möglich ein Update bereitstellen.

2. 15. Oktober 2026 um 20:00 UTCinvestigating

   Unsere Engineering-Teams beheben aktiv die identifizierten Leistungsprobleme in der Splunk Observability Web-Benutzeroberfläche, wir werden so schnell wie möglich ein neues Update veröffentlichen.

3. 15. Oktober 2026 um 21:05 UTCinvestigating

   Unsere Engineering-Teams werden weiterhin die identifizierten Leistungsprobleme in der Splunk Observability Web-Benutzeroberfläche beheben, wir werden so schnell wie möglich ein neues Update veröffentlichen.

4. 15. Oktober 2026 um 21:44 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Oktober 2026 um 02:20 UTCinvestigating

   Wir untersuchen Verzögerungen bei der Verarbeitung von Splunk Observability Synthetic Monitoring Testergebnissen. Synthetische Monitoring-Tests sind funktionsfähig, aber Metriken können fehlen, bis das Problem behoben ist.

2. 3. Oktober 2026 um 02:59 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 3. Oktober 2026 um 03:12 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 3. Oktober 2026 um 03:12 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. September 2026 um 15:35 UTCresolved

   Einige Kunden sehen Anmeldefehler aufgrund von Zertifikatsfehlern. Kunden, die bereits protokolliert sind, sind nicht betroffen. Das Problem ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 07: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. 14. August 2026 um 08:11 UTCmonitoring

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

3. 14. August 2026 um 08:17 UTCresolved

   The incident has been resolved.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 7. August 2026 um 08: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. 7. August 2026 um 09: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. 8. Juli 2026 um 10:45 UTCresolved

   Zwischen 1a PDT und 2:50a PDT wurden bei jeder GCP-Integration, bei der die Einstellung "Alle (dynamisch) aufgeführten Projekte synchronisieren" aktiviert war, einige der Cloud-Monitoring-Daten von GCP gelöscht. Dieses Problem ist gelöst. Kunden können Lücken in Diagrammen und Detektoren sehen, die betroffene GCP Cloud Monitoring-Metriken verwenden. Die Metriken AWS CloudWatch und Azure Monitor sind nicht betroffen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juli 2026 um 15:02 UTCresolved

   Wir haben bestätigt, dass das Problem mit Tag Spotlight behoben wurde. Kunden haben möglicherweise eine eingeschränkte Funktionalität innerhalb von Tag Spotlight, die am 30. Juni um ca. 16:30 Uhr PT beginnt. Die volle Funktionalität wurde am 1. Juli um 7:20 Uhr PT wiederhergestellt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. Juni 2026 um 07:28 UTCresolved

   Aufgrund einer Regression in einer kürzlich veröffentlichten Version wurden Benutzer, die von Logs Related Content auf der APM TraceView-Seite zu Log Observer navigieren, stattdessen zu APM TraceView umgeleitet. Dies beeinflusste die Logs Correlation-Erfahrung für Kunden in allen Bereichen, außer US3 und Gov. Die Änderung wurde rückgängig gemacht, um das erwartete Navigationserlebnis wiederherzustellen. Die Produktverfügbarkeit für APM und Log Observer war nicht betroffen; das Problem war auf den Logs Correlation Workflow von TraceView beschränkt. Incident Startzeit: 05:09 PDT, 25. Juni 2026 Incident End Time: 22:15 PDT, 25. Juni 2026

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juni 2026 um 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. 2. Juni 2026 um 16: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. 20. Mai 2026 um 05:10 UTCinvestigating

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

2. 20. Mai 2026 um 05:46 UTCinvestigating

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

3. 20. Mai 2026 um 07: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. 20. Mai 2026 um 07:48 UTCinvestigating

   We are continuing to monitor this issue.

5. 20. Mai 2026 um 07:49 UTCinvestigating

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

6. 20. Mai 2026 um 08:03 UTCmonitoring

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

7. 20. Mai 2026 um 16:41 UTCresolved

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

1. 20. Mai 2026 um 01: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. 20. Mai 2026 um 02:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. Mai 2026 um 03: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. 20. Mai 2026 um 03: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. 20. Mai 2026 um 03: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. 7. Mai 2026 um 19:17 UTCinvestigating

   We are currently investigating this issue.

2. 7. Mai 2026 um 19:19 UTCidentified

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

3. 7. Mai 2026 um 19:21 UTCresolved

   We are back to normal

1. 25. April 2026 um 15: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. 25. April 2026 um 16: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. 25. April 2026 um 18: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. 25. April 2026 um 22: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. 25. April 2026 um 23: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. 26. April 2026 um 00: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. 25. April 2026 um 00: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. 25. April 2026 um 01: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. 25. April 2026 um 02: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. 25. April 2026 um 02: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. 25. April 2026 um 02: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. 25. April 2026 um 03: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. 5. April 2026 um 18: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. 5. April 2026 um 18:44 UTCinvestigating

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

3. 5. April 2026 um 18:59 UTCinvestigating

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

4. 5. April 2026 um 19:14 UTCidentified

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

5. 5. April 2026 um 19:31 UTCidentified

   Teams continue working to implement the fix for this issue.

6. 5. April 2026 um 19:33 UTCmonitoring

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

7. 5. April 2026 um 19:46 UTCresolved

   This incident has been resolved.

1. 23. März 2026 um 23:31 UTCidentified

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

2. 24. März 2026 um 00: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. 24. März 2026 um 18: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. 25. April 2026 um 02:52 UTCresolved

   This incident has been resolved.

1. 3. März 2026 um 17: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. 5. März 2026 um 19: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. 27. Februar 2026 um 09:32 UTCinvestigating

   We are currently investigating this issue.

2. 27. Februar 2026 um 10:35 UTCmonitoring

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

3. 27. Februar 2026 um 11:41 UTCresolved

   This incident has been resolved.

1. 17. Februar 2026 um 18:20 UTCinvestigating

   Customers may be experiencing errors while loading Data Management Page.

2. 17. Februar 2026 um 18:48 UTCidentified

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

3. 17. Februar 2026 um 19:18 UTCmonitoring

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

4. 17. Februar 2026 um 19:22 UTCresolved

   This incident has been resolved.

1. 29. Januar 2026 um 17: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.