Signalfx Eu0 driftsforstyrrelser

1. 15. oktober 2026 kl. 19.02 UTCinvestigating

   Vi undersøger en nedbrydning af Splunk Observability Cloud webapplikation for nogle kunder. Data ingest er ikke påvirket på nuværende tidspunkt. Vi vil give en opdatering så hurtigt som muligt.

2. 15. oktober 2026 kl. 20.00 UTCinvestigating

   Vores engineering teams er aktivt fejlfinding de identificerede performance problemer i Splunk Observability Web UI, vil vi dele en ny opdatering så hurtigt som muligt.

3. 15. oktober 2026 kl. 21.05 UTCinvestigating

   Vores ingeniørhold fortsætter fejlfinding af de identificerede performance problemer i Splunk Observability Web UI, vil vi dele en ny opdatering så hurtigt som muligt.

4. 15. oktober 2026 kl. 21.44 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. oktober 2026 kl. 02.20 UTCinvestigating

   Vi er ved at undersøge forsinkelser i behandlingen af Splunk Observability Synthetic Monitoring testresultater. Synthetic Monitoring tests er operationelle, men målinger kan være mangler, indtil problemet er løst.

2. 3. oktober 2026 kl. 02.59 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 3. oktober 2026 kl. 03.12 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 3. oktober 2026 kl. 03.12 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 18. september 2026 kl. 15.35 UTCresolved

   Nogle af kunden ser login fejl på grund af certifikat fejl. Kunder, der allerede er logget er ikke påvirket. Spørgsmålet er løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. august 2026 kl. 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 kl. 08.11 UTCmonitoring

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

3. 14. august 2026 kl. 08.17 UTCresolved

   The incident has been resolved.

1. 7. august 2026 kl. 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 kl. 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 kl. 10.45 UTCresolved

   Mellem 1a PDT og 2: 50a PDT, enhver GCP integration, der havde "Sync all (dynamisk) listet projekter" indstilling aktiveret havde nogle af Cloud Overvågning data fra GCP faldet. Dette spørgsmål er blevet løst. Kunder kan se huller i diagrammer og detektorer, der bruger påvirket GCP Cloud Overvågning målinger. AWS CloudWatch og Azure Monitor målinger er ikke påvirket.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. juli 2026 kl. 15.02 UTCresolved

   Vi har bekræftet, at problemet med Tag Spotlight er løst. Kunder kan have oplevet begrænset funktionalitet inden for Tag Spotlight begynder omkring 4: 30 PM PT den 30. juni. Fuld funktionalitet blev genoprettet på 7: 20 AM PT den 1. juli.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. juni 2026 kl. 07.28 UTCresolved

   På grund af en regression i en nylig udgivelse, blev brugere, der navigerer fra Logs Related Content på APM TraceView side til log Observer omdirigeret tilbage til APM TraceView i stedet. Dette påvirkede Logs korrelation oplevelse for kunder på tværs af alle riger, undtagen US3 og Gov. Ændringen er blevet vendt for at genoprette den forventede navigationserfaring. Product tilgængelighed for APM og log Observer var ikke påvirket; problemet var begrænset til Logs Correlation workflow fra TraceView. Tilfælde Starttid: 05: 09 PDT, 25 juni, 2026 Hændelsestidspunkt: 22: 15 PDT, 25. juni 2026

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juni 2026 kl. 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 kl. 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. maj 2026 kl. 05.10 UTCinvestigating

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

2. 20. maj 2026 kl. 05.46 UTCinvestigating

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

3. 20. maj 2026 kl. 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. maj 2026 kl. 07.48 UTCinvestigating

   We are continuing to monitor this issue.

5. 20. maj 2026 kl. 07.49 UTCinvestigating

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

6. 20. maj 2026 kl. 08.03 UTCmonitoring

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

7. 20. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 02.19 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 19.17 UTCinvestigating

   We are currently investigating this issue.

2. 7. maj 2026 kl. 19.19 UTCidentified

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

3. 7. maj 2026 kl. 19.21 UTCresolved

   We are back to normal

1. 25. april 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 18.44 UTCinvestigating

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

3. 5. april 2026 kl. 18.59 UTCinvestigating

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

4. 5. april 2026 kl. 19.14 UTCidentified

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

5. 5. april 2026 kl. 19.31 UTCidentified

   Teams continue working to implement the fix for this issue.

6. 5. april 2026 kl. 19.33 UTCmonitoring

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

7. 5. april 2026 kl. 19.46 UTCresolved

   This incident has been resolved.

1. 23. marts 2026 kl. 23.31 UTCidentified

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

2. 24. marts 2026 kl. 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. marts 2026 kl. 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 kl. 02.52 UTCresolved

   This incident has been resolved.

1. 3. marts 2026 kl. 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. marts 2026 kl. 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 kl. 09.32 UTCinvestigating

   We are currently investigating this issue.

2. 27. februar 2026 kl. 10.35 UTCmonitoring

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

3. 27. februar 2026 kl. 11.41 UTCresolved

   This incident has been resolved.

1. 17. februar 2026 kl. 18.20 UTCinvestigating

   Customers may be experiencing errors while loading Data Management Page.

2. 17. februar 2026 kl. 18.48 UTCidentified

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

3. 17. februar 2026 kl. 19.18 UTCmonitoring

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

4. 17. februar 2026 kl. 19.22 UTCresolved

   This incident has been resolved.

1. 29. januar 2026 kl. 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.