Historial de interrupciones de Veracode

1. September 2, 2026 at 8:00 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. September 3, 2026 at 2:17 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 3, 2026 at 2:37 AM UTCidentified

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

4. September 3, 2026 at 2:58 AM UTCmonitoring

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

5. September 3, 2026 at 8:24 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. September 1, 2026 at 4:08 AM UTCinvestigating

   Actualmente estamos investigando el tema

2. September 1, 2026 at 4:09 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 1, 2026 at 4:34 AM UTCidentified

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

4. September 1, 2026 at 4:35 AM UTCmonitoring

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

5. September 1, 2026 at 4:37 AM UTCmonitoring

   Monitoring - issue seems to be resolved

6. September 1, 2026 at 4:40 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 26, 2026 at 1:33 PM UTCinvestigating

   Estamos investigando retrasos que hacen que los cálculos de políticas tomen más tiempo de lo esperado.

2. August 26, 2026 at 1:45 PM UTCidentified

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

3. August 26, 2026 at 3:12 PM UTCmonitoring

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

4. August 26, 2026 at 6:22 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 19, 2026 at 10:03 PM UTCmonitoring

   Veracode ha detectado tiempos de terminación de escaneo estático más largos de lo normal para algunos clientes. Se ha aplicado una solución y estamos monitoreando los resultados.

2. August 20, 2026 at 11:48 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 14, 2026 at 3:35 PM UTCinvestigating

   We are currently investigating this issue.

2. August 14, 2026 at 4:42 PM UTCidentified

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

3. August 14, 2026 at 5:01 PM UTCmonitoring

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

4. August 14, 2026 at 6:13 PM UTCresolved

   This incident has been resolved.

1. August 11, 2026 at 5:15 PM UTCinvestigating

   Los clientes están viendo la página de mantenimiento. La investigación está en marcha.

2. August 11, 2026 at 5:40 PM UTCmonitoring

   This incident is being monitored. The impact of this issue appears to be limited to requests that originate within the Veracode network.

3. August 11, 2026 at 7:34 PM UTCresolved

   This incident has been resolved.

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

1. July 21, 2026 at 3:40 PM UTCinvestigating

   Al navegar por la interfaz de usuario, los usuarios pueden ser redireccionados a Ajustes de su cuenta.

2. July 21, 2026 at 3:48 PM UTCidentified

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

3. July 21, 2026 at 4:26 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. July 21, 2026 at 4:26 PM UTCmonitoring

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

5. July 21, 2026 at 4:38 PM UTCmonitoring

   Hay una serie de escaneos estáticos que se presentaron durante el incidente que todavía puede estar en un estado atorado. Veracode está trabajando a través de llevarlos a procesar.

6. July 21, 2026 at 6:00 PM UTCmonitoring

   Continuamos trabajando a través de la acumulación de escaneos estáticos.

7. July 21, 2026 at 10:53 PM UTCresolved

   Hemos completado el procesamiento de nuestro atraso de escaneos estáticos. En algunos casos no pudimos procesar los escaneos que han fracasado. En ese caso, el escaneo debe ser eliminado y recargado.

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

1. July 17, 2026 at 1:15 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 17, 2026 at 1:35 PM UTCmonitoring

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

3. July 17, 2026 at 2:48 PM UTCresolved

   Este incidente ha sido resuelto. Los clientes que utilizan la plataforma veracode o API entre los siguientes períodos pueden haber visto problemas de inicio de sesión o 500 respuestas de nivel de las API de veracode. - 6:20 AM EDT - 7:00 AM EDT - 8:20 AM EDT - 9:05 AM EDT

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

1. July 15, 2026 at 2:37 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 15, 2026 at 3:04 PM UTCidentified

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

3. July 15, 2026 at 3:13 PM UTCmonitoring

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

4. July 15, 2026 at 4:03 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 11, 2026 at 4:01 PM UTCidentified

   La SCA sigue siendo objeto de mantenimiento y estará disponible lo antes posible.

2. July 11, 2026 at 4:27 PM UTCidentified

   Continuamos trabajando para completar el mantenimiento. Durante este tiempo, otras API de Veracode verán mayores tasas de error.

3. July 11, 2026 at 4:33 PM UTCmonitoring

   Se ha completado el mantenimiento, se están terminando las pruebas. Se han resuelto las tasas de error de API.

4. July 11, 2026 at 4:43 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 1, 2026 at 12:48 PM UTCidentified

   Estamos rastreando errores mayores relacionados con el acceso o la edición de información de políticas. Los servicios de análisis y la evaluación de políticas no son afectados.

2. July 1, 2026 at 12:54 PM UTCmonitoring

   Se ha desplegado una solución, el tráfico se está procediendo normalmente.

3. July 1, 2026 at 1:19 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. May 26, 2026 at 1:12 PM UTCinvestigating

   We are currently investigating this issue.

2. May 26, 2026 at 1:32 PM UTCmonitoring

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

3. May 26, 2026 at 1:33 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. May 26, 2026 at 4:27 PM UTCresolved

   This incident has been resolved.

1. May 19, 2026 at 3:45 PM UTCinvestigating

   We are currently investigating this issue.

2. May 19, 2026 at 3:47 PM UTCidentified

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

3. May 19, 2026 at 3:53 PM UTCmonitoring

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

4. May 19, 2026 at 3:54 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. May 19, 2026 at 6:54 PM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 5:04 PM UTCinvestigating

   We are currently investigating this issue.

2. April 24, 2026 at 5:35 PM UTCidentified

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

3. April 24, 2026 at 5:51 PM UTCmonitoring

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

4. April 24, 2026 at 6:27 PM UTCresolved

   This incident has been resolved.

1. April 14, 2026 at 8:30 AM UTCinvestigating

   We are currently investigating this issue.

2. April 14, 2026 at 8:48 AM UTCidentified

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

3. April 14, 2026 at 8:54 AM UTCmonitoring

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

4. April 14, 2026 at 8:55 AM UTCmonitoring

   We are continuing to monitor for any further issues.

5. April 14, 2026 at 9:04 AM UTCresolved

   This incident has been resolved.

1. April 1, 2026 at 11:01 AM UTCinvestigating

   We are investigating the issue

2. April 1, 2026 at 11:25 AM UTCidentified

   We have identified the issue and working on the fix

3. April 1, 2026 at 11:40 AM UTCmonitoring

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

4. April 1, 2026 at 11:40 AM UTCmonitoring

   We are continuing to monitor for any further issues.

5. April 1, 2026 at 11:49 AM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 7:42 PM UTCinvestigating

   We are currently investigating this issue.

2. March 10, 2026 at 8:27 PM UTCidentified

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

3. March 10, 2026 at 8:34 PM UTCidentified

   We are continuing to work on a fix for this issue.

4. March 10, 2026 at 8:34 PM UTCmonitoring

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

5. March 10, 2026 at 10:45 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 5:34 PM UTCinvestigating

   We are currently investigating this issue.

2. March 10, 2026 at 5:35 PM UTCidentified

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

3. March 10, 2026 at 5:36 PM UTCidentified

   We are continuing to work on a fix for this issue.

4. March 10, 2026 at 5:36 PM UTCmonitoring

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

5. March 10, 2026 at 5:39 PM UTCresolved

   This incident has been resolved.

1. February 3, 2026 at 7:28 PM UTCinvestigating

   We are currently investigating this issue.

2. February 3, 2026 at 7:45 PM UTCinvestigating

   We are continuing to investigate this issue.

3. February 3, 2026 at 7:45 PM UTCmonitoring

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

4. February 3, 2026 at 10:46 PM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 10:16 PM UTCinvestigating

   We are currently investigating this issue.

2. January 27, 2026 at 10:33 PM UTCidentified

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

3. January 27, 2026 at 11:33 PM UTCmonitoring

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

4. January 27, 2026 at 11:53 PM UTCresolved

   This incident has been resolved.