Historial de interrupciones de Signalfx Eu0

1. 14 de agosto de 2026 a las 7:49 UTCinvestigating

   Una degradación en el rendimiento de la tubería de ingestión de datos Splunk APM está causando que el procesamiento y almacenamiento de datos de traza cruda se retrasen en más de cinco minutos. No se están perdiendo datos en este momento y MetricSets no están impactados, pero los datos más recientes pueden no estar disponibles en los resultados de búsqueda de rastros.

2. 14 de agosto de 2026 a las 8:11 UTCmonitoring

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

3. 14 de agosto de 2026 a las 8:17 UTCresolved

   The incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. 7 de agosto de 2026 a las 8:30 UTCinvestigating

   Una degradación en el rendimiento de la tubería de ingestión de datos Splunk APM está causando que el procesamiento y almacenamiento de datos de traza cruda se retrasen en más de cinco minutos. No se están perdiendo datos en este momento y MetricSets no están impactados, pero los datos más recientes pueden no estar disponibles en los resultados de búsqueda de rastros.

2. 7 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de julio de 2026 a las 10:45 UTCresolved

   Entre 1a PDT y 2:50a PDT, cualquier integración GCP que tuviera habilitado el ajuste "Sync all (dinámicamente) de los proyectos listados" tenía algunos de los datos de monitoreo de nube de GCP bajaron. Esta cuestión se ha resuelto. Los clientes pueden ver lagunas en gráficos y detectores que utilizan métricas de monitoreo de la nube GCP afectada. Las métricas AWS CloudWatch y Azure Monitor no son impactadas.

Traducido automáticamente desde la actualización oficial del incidente.

1. 1 de julio de 2026 a las 15:02 UTCresolved

   Hemos confirmado que el problema que afecta a Tag Spotlight ha sido resuelto. Los clientes pueden haber experimentado funcionalidad limitada dentro de Tag Spotlight comenzando aproximadamente a las 4:30 PM PT el 30 de junio. La funcionalidad completa fue restaurada a las 7:20 AM PT el 1 de julio.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de junio de 2026 a las 7:28 UTCresolved

   Debido a una regresión en una reciente versión, los usuarios navegando desde Logs Contenido relacionado en la página APM TraceView a Log Observer fueron redireccionados de nuevo a APM TraceView. Esto impactó la experiencia de Correlación Logs para clientes en todos los ámbitos, excepto US3 y Gov. El cambio se ha revertido para restaurar la experiencia de navegación prevista. La disponibilidad de productos para APM y Log Observer no se vio afectada; la cuestión se limitó al flujo de trabajo de Correlación Logs de TraceView. Tiempo de inicio del incidente: 05:09 PDT, 25 de junio, 2026 Tiempo final del incidente: 22:15 PDT, 25 de junio de 2026

Traducido automáticamente desde la actualización oficial del incidente.

1. 2 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 5:10 UTCinvestigating

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

2. 20 de mayo de 2026 a las 5:46 UTCinvestigating

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

3. 20 de mayo de 2026 a las 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. 20 de mayo de 2026 a las 7:48 UTCinvestigating

   We are continuing to monitor this issue.

5. 20 de mayo de 2026 a las 7:49 UTCinvestigating

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

6. 20 de mayo de 2026 a las 8:03 UTCmonitoring

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

7. 20 de mayo de 2026 a las 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 de mayo de 2026 a las 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. 20 de mayo de 2026 a las 2:19 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 de mayo de 2026 a las 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. 20 de mayo de 2026 a las 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. 20 de mayo de 2026 a las 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. 7 de mayo de 2026 a las 19:17 UTCinvestigating

   We are currently investigating this issue.

2. 7 de mayo de 2026 a las 19:19 UTCidentified

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

3. 7 de mayo de 2026 a las 19:21 UTCresolved

   We are back to normal

1. 25 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 0: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 de abril de 2026 a las 0: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 de abril de 2026 a las 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. 25 de abril de 2026 a las 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. 25 de abril de 2026 a las 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. 25 de abril de 2026 a las 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. 25 de abril de 2026 a las 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. 5 de abril de 2026 a las 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 de abril de 2026 a las 18:44 UTCinvestigating

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

3. 5 de abril de 2026 a las 18:59 UTCinvestigating

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

4. 5 de abril de 2026 a las 19:14 UTCidentified

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

5. 5 de abril de 2026 a las 19:31 UTCidentified

   Teams continue working to implement the fix for this issue.

6. 5 de abril de 2026 a las 19:33 UTCmonitoring

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

7. 5 de abril de 2026 a las 19:46 UTCresolved

   This incident has been resolved.

1. 23 de marzo de 2026 a las 23:31 UTCidentified

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

2. 24 de marzo de 2026 a las 0: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 de marzo de 2026 a las 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 de abril de 2026 a las 2:52 UTCresolved

   This incident has been resolved.

1. 3 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de febrero de 2026 a las 9:32 UTCinvestigating

   We are currently investigating this issue.

2. 27 de febrero de 2026 a las 10:35 UTCmonitoring

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

3. 27 de febrero de 2026 a las 11:41 UTCresolved

   This incident has been resolved.

1. 17 de febrero de 2026 a las 18:20 UTCinvestigating

   Customers may be experiencing errors while loading Data Management Page.

2. 17 de febrero de 2026 a las 18:48 UTCidentified

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

3. 17 de febrero de 2026 a las 19:18 UTCmonitoring

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

4. 17 de febrero de 2026 a las 19:22 UTCresolved

   This incident has been resolved.

1. 29 de enero de 2026 a las 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.

1. 21 de enero de 2026 a las 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. 21 de enero de 2026 a las 14:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 de enero de 2026 a las 15: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. 21 de enero de 2026 a las 18: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. 21 de enero de 2026 a las 22:38 UTCidentified

   We are continuing to investigate this issue.

6. 21 de enero de 2026 a las 23:41 UTCidentified

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

7. 22 de enero de 2026 a las 14:02 UTCresolved

   The issue has been identified and resolved.

1. 19 de enero de 2026 a las 18:42 UTCinvestigating

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

2. 19 de enero de 2026 a las 18:44 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 de enero de 2026 a las 19:23 UTCinvestigating

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

4. 19 de enero de 2026 a las 20: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. 14 de enero de 2026 a las 15:23 UTCinvestigating

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

2. 14 de enero de 2026 a las 16:06 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 de enero de 2026 a las 16: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. 14 de enero de 2026 a las 17:22 UTCidentified

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

5. 14 de enero de 2026 a las 18:28 UTCmonitoring

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

6. 14 de enero de 2026 a las 18:42 UTCresolved

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