Historial de interrupciones de Signalfx Us1

1. August 28, 2026 at 6:01 PM UTCinvestigating

   Estamos investigando una gran salida del Asistente de IA de la Observabilidad Splunk.

2. August 28, 2026 at 6:20 PM UTCidentified

   El tema ha sido identificado como una salida de Azure OpenAI y estamos procediendo con una solución de trabajo.

3. August 28, 2026 at 6:25 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. August 28, 2026 at 7:26 PM UTCresolved

   Fase de vigilancia completa. La cuestión se ha resuelto.

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

1. August 25, 2026 at 6:44 PM UTCinvestigating

   Desde 08/25/2026, 11:38AM PDT, una degradación en el rendimiento de la tubería de procesamiento de trazas Splunk APM está causando que Troubleshooting MetricSets sea retrasado en más de cinco minutos. Como resultado, la experiencia de solución de problemas APM, mapas de servicio y Tag Spotlight no tienen acceso a los datos más recientes. El procesamiento de métricas para los flujos de trabajo de negocios, que también depende de este oleoducto, se retrasa igualmente. Los datos de rastreo ingeridos no se impactan en este momento; tampoco se impactan las métricas de monitoreo de nivel de servicio y punto final y los detectores construidos a partir de ellas.

2. August 25, 2026 at 7:21 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. August 25, 2026 at 7:44 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. August 25, 2026 at 8:02 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. August 25, 2026 at 8:25 PM UTCmonitoring

   Nuestros equipos siguen vigilando la situación para garantizar la plena remediación.

6. August 25, 2026 at 9:07 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 1, 2026 at 2:35 PM UTCinvestigating

   Problemas con las alertas de procesamiento que conducen a notificaciones retardadas. Actualmente estamos investigando la cuestión.

2. August 1, 2026 at 3:33 PM UTCinvestigating

   Actualmente estamos investigando la latencia elevada de notificación. Los clientes pueden experimentar retrasos en recibir notificaciones de alerta. Estamos trabajando activamente para resolver este problema y proporcionaremos actualizaciones a medida que avancemos. Apreciamos su paciencia.

3. August 1, 2026 at 3:55 PM UTCidentified

   Hemos identificado y estamos resolviendo activamente la cuestión causando notificaciones de alerta retardada. La solución se ha aplicado y ya está mostrando una mejora significativa en los plazos de entrega de notificaciones. Si bien algunas notificaciones que fueron consultadas antes de nuestra solución pueden seguir experimentando retrasos menores a medida que el sistema se pone al día, se envían normalmente nuevas notificaciones. Apreciamos su paciencia y seguiremos monitoreando la situación de cerca.

4. August 1, 2026 at 5:09 PM UTCidentified

   Estamos trabajando activamente para resolver la cuestión. Los clientes pueden seguir experimentando retrasos en la entrega de notificación. Esto incluye notificaciones generadas recientemente, que se están procesando tras acontecimientos anteriores en la cola. El equipo está investigando activamente la causa raíz y trabajando para aclarar el atraso de las notificaciones internas. Como medida de mitigación temporal, tenemos previsiones de imagen desactivadas en notificaciones para mejorar la velocidad de procesamiento. Las notificaciones serán sólo de texto por ahora. Apreciamos su paciencia y proporcionaremos nuevas actualizaciones a medida que se haga el progreso.

5. August 1, 2026 at 5:31 PM UTCmonitoring

   Hemos implementado una solución para abordar los retrasos de notificación. Nuestro monitoreo muestra una mejora significativa en los plazos de entrega de notificaciones, y estamos siguiendo de cerca el rendimiento para asegurar que la cuestión se resuelva completamente. Gracias por su paciencia mientras trabajamos para restaurar el servicio completo.

6. August 1, 2026 at 6:21 PM UTCresolved

   The notification delivery delays have been fully resolved. Todas las notificaciones solicitadas han sido procesadas y el sistema está funcionando normalmente.

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

1. July 31, 2026 at 2:51 AM UTCinvestigating

   Una degradación en el rendimiento de la tubería de procesamiento de métricas Splunk APM está causando que las métricas de monitoreo se retrasan en más de cinco minutos. El ingerente de datos de trace no está afectado, pero los paneles de servicio, punta y flujo de trabajo, y otros gráficos y detectores construidos a partir de Monitor MetricSets son impactados.

2. July 31, 2026 at 2:54 AM UTCinvestigating

   Seguimos investigando el problema.

3. July 31, 2026 at 3:44 AM UTCinvestigating

   Seguimos investigando esta cuestión.

4. July 31, 2026 at 4:07 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. July 31, 2026 at 4:08 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. July 31, 2026 at 4:33 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 24, 2026 at 9:54 PM UTCresolved

   Datapoint ingert for new or reactivated metric time series was affected between 2:28 PM PST to 2:47 PM PST. Hubo pérdida parcial de datos para nuevas series de tiempo métricas durante ese período. Esta situación se recupera ahora.

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

1. July 22, 2026 at 6:02 PM UTCresolved

   Datapoint ingert for new metric time series was affected between 10:37 AM PST and 10:39 AM PST. Hubo pérdida parcial de datos para nuevas series de tiempo métricas durante ese período. Esta situación se recupera ahora.

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

1. July 14, 2026 at 11:25 AM UTCinvestigating

   A partir de 4a PT, estamos investigando una gran salida de la aplicación web de Splunk Observability Cloud. El ingerido de datos no se impacta en este momento. Proporcionaremos una actualización lo antes posible.

2. July 14, 2026 at 12:13 PM UTCinvestigating

   Seguimos investigando el problema.

3. July 14, 2026 at 12:28 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 14, 2026 at 12:38 PM UTCresolved

   Este incidente ha sido resuelto. Tenga en cuenta que el Splunk Observability Cloud API también fue afectado durante este incidente.

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

1. July 8, 2026 at 10:52 AM 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. July 4, 2026 at 5:07 PM UTCinvestigating

   Los clientes pueden experimentar retrasos en ver series de tiempo métricas recién creadas. Datapoint ingest no se ve afectada por la serie de tiempo existente. Estamos investigando y proporcionaremos una actualización en breve.

2. July 4, 2026 at 6:39 PM UTCresolved

   Se ha resuelto la cuestión que causa retrasos en la nueva serie de tiempo métrico. La creación de series temporales métricas funciona normalmente. La ingestión de puntos de datos para las series de tiempo existentes no se vio afectada.

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

1. July 1, 2026 at 3:08 PM 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. June 26, 2026 at 7:37 AM 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. June 12, 2026 at 12:03 AM UTCresolved

   Rum API Endpoints were not available for one of our IPs, resulting in degraded service or a partial outage at first, and possibly a complete outage towards the end. This issue occurred from 4:22pm PST to 4:57pm PST

1. June 3, 2026 at 10:49 PM UTCinvestigating

   Datapoint ingest is affected , some datapoints could be dropped. Team is investigating and will provide an update shortly.

2. June 3, 2026 at 11:25 PM UTCinvestigating

   Our engineering team is currently implementing an impact mitigation configuration change. The internal investigation is still ongoing. We will share an additional update as soon as possible.

3. June 4, 2026 at 12:05 AM UTCmonitoring

   Our engineering team has completed impact mitigating configuration changes and confirmed services are recovered as of 4:55 PDT. We will continue monitoring and share an update as soon as possible.

4. June 4, 2026 at 1:08 AM UTCresolved

   Our engineering team has confirmed that all the services recovered as of 4:55 PM PDT and remained stable during monitoring. This incident is now resolved.

1. June 2, 2026 at 12:50 PM 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. June 2, 2026 at 4:51 PM 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. May 29, 2026 at 5:40 AM UTCinvestigating

   Charts for customers may not be loading. App and UI availability is also impacted. We are investigating and will provide an update shortly.

2. May 29, 2026 at 5:43 AM UTCidentified

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

3. May 29, 2026 at 5:56 AM UTCmonitoring

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

4. May 29, 2026 at 6:06 AM UTCresolved

   This Incident has been resolved.

1. May 12, 2026 at 10:38 AM UTCinvestigating

   A degradation of the Splunk O11y Cloud ingest path is causing ~20% of AWS CloudWatch metrics to be dropped. We are investigating the issue and will provide an update as soon as possible.

2. May 12, 2026 at 3:44 PM UTCresolved

   This incident has been resolved. We have since confirmed that only AWS CloudWatch metrics were impacted during this incident. Azure and GCP metrics were not impacted.

1. May 8, 2026 at 4:21 AM UTCinvestigating

   We are currently investigating this issue.

2. May 8, 2026 at 4:22 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 8, 2026 at 5:46 AM UTCidentified

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

4. May 8, 2026 at 5:46 AM UTCresolved

   This incident has been resolved.

1. May 6, 2026 at 2:44 PM UTCinvestigating

   Charts for all customers may not be loading. Datapoint ingest is not affected. We are investigating and will provide an update shortly.

2. May 6, 2026 at 3:07 PM UTCinvestigating

   Our teams continue working to identify the cause and implement a fix.

3. May 6, 2026 at 3:36 PM UTCinvestigating

   Our investigation remains ongoing, and there is no change in status at this time. We are continuing to prioritize this issue and will provide the next update in thirty minutes.

4. May 6, 2026 at 4:14 PM UTCinvestigating

   Our teams are continuing their efforts to identify the root cause of this issue. There is no change in status to report at this time, but we are dedicating all necessary resources to reach a resolution. We will provide another update shortly.

5. May 6, 2026 at 4:31 PM UTCinvestigating

   Update (8:50 AM PST): We have observed that charts are now loading successfully. While service is recovering, our teams remain on-site to investigate the root cause and ensure full system stability. We will continue to monitor performance closely.

6. May 6, 2026 at 5:02 PM UTCinvestigating

   We are continuing to monitor the environment. There is no change in status at this time; our teams remain focused on resolving the remaining isolated issues.

7. May 6, 2026 at 5:31 PM UTCinvestigating

   Our teams are continuing to monitor the environment and are actively working to fully resolve the issue.

8. May 6, 2026 at 5:44 PM UTCinvestigating

   Update 10:30 PST: We are also investigating reports of login issues. Users may experience difficulty authenticating or accessing their accounts at this time.

9. May 6, 2026 at 5:58 PM UTCidentified

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

10. May 6, 2026 at 6:13 PM UTCmonitoring

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

11. May 6, 2026 at 7:08 PM UTCmonitoring

    We are continuing to monitor the environment to ensure full remediation.

12. May 6, 2026 at 7:25 PM UTCresolved

    This incident has been resolved.

1. April 25, 2026 at 5:01 PM 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. April 25, 2026 at 5:02 PM 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. April 25, 2026 at 6:37 PM 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. April 25, 2026 at 10:26 PM 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. April 25, 2026 at 11:48 PM 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. April 26, 2026 at 12:55 AM 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. April 25, 2026 at 1:03 AM 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. April 25, 2026 at 1:22 AM 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. April 25, 2026 at 2:02 AM 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. April 25, 2026 at 2:33 AM 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. April 25, 2026 at 2:55 AM 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. April 25, 2026 at 3:13 AM 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.