Historial de interrupciones de Veracross

1. September 8, 2026 at 9:15 PM UTCinvestigating

   Actualmente estamos investigando informes de errores cuando intentamos entrar en la Comunidad Veracross.

2. September 8, 2026 at 9:38 PM UTCidentified

   Creemos que hemos identificado la fuente de los errores de inicio de sesión de la Comunidad Veracross y estamos trabajando para implementar una solución.

3. September 8, 2026 at 9:51 PM UTCmonitoring

   Hemos implementado una solución y estamos monitoreando los accesos posteriores a la Comunidad Veracross.

4. September 8, 2026 at 10:09 PM UTCresolved

   Hemos confirmado que la solución ha resuelto el error de inicio de sesión de la Comunidad Veracross.

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

1. August 31, 2026 at 8:38 PM UTCinvestigating

   Estamos investigando un incidente que impacta la contabilidad y los correos electrónicos (salida completa) y archivos (experiencia degradada).

2. August 31, 2026 at 8:42 PM UTCmonitoring

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

3. August 31, 2026 at 8:45 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 27, 2026 at 9:39 PM UTCinvestigating

   Actualmente estamos investigando un problema con la visualización del tiempo en Axiom incorrectamente utilizando UTC en lugar de la zona horaria real de la escuela.

2. August 27, 2026 at 10:54 PM UTCresolved

   Este incidente ha sido resuelto y cada base de datos ahora muestra tiempo correctamente utilizando la zona horaria de la escuela.

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

1. August 20, 2026 at 4:08 PM UTCinvestigating

   Actualmente estamos investigando un incidente que implica la funcionalidad de exportación de consultas en Axiom.

2. August 20, 2026 at 4:20 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 17, 2026 at 11:39 PM UTCidentified

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

2. August 18, 2026 at 12:18 AM UTCmonitoring

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

3. August 18, 2026 at 5:00 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 12, 2026 at 3:51 PM UTCinvestigating

   We are currently investigating reports that Data Importer imports are stuck in pending status.

2. August 12, 2026 at 4:11 PM UTCresolved

   This incident has been resolved. We apologize for the disruption.

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

   We are currently investigating reports that Data Importer imports are stuck in pending status.

2. August 11, 2026 at 5:27 PM UTCresolved

   We have resolved the issue with the Data Importer that caused imports to be stuck in a pending status.

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

1. July 31, 2026 at 12:59 AM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. July 31, 2026 at 1:02 AM UTCmonitoring

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

3. July 31, 2026 at 1:08 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 22, 2026 at 9:14 PM UTCinvestigating

   Actualmente estamos investigando un problema que hace que las acciones estén atascadas en un estado pendiente. Estamos trabajando para corregir este problema y proporcionaremos actualizaciones tan pronto como podamos.

2. July 22, 2026 at 9:29 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 20, 2026 at 7:22 PM UTCidentified

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

2. July 20, 2026 at 7:42 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 18, 2026 at 9:38 PM UTCidentified

   We have detected an outage for Documents in the US.

2. June 18, 2026 at 9:53 PM UTCidentified

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

3. June 18, 2026 at 10:26 PM UTCresolved

   This incident has been resolved.

1. June 16, 2026 at 12:10 AM UTCresolved

   Between Friday 12 June at 21:00 UTC and Saturday 13 June at 14:00 UTC EMEA and APAC users experienced errors when accessing Portals. We identified a misconfiguration in the backend and resolved the issue.

1. June 4, 2026 at 3:38 PM UTCresolved

   Syncs for our Ravenna Integration were failing due to the same issue impacting our Data Importer. That issue has been resolved and Ravenna syncs should once again complete successfully.

1. June 4, 2026 at 2:04 PM UTCinvestigating

   We are currently investigating reports that Data Importer imports are stuck in pending status.

2. June 4, 2026 at 3:33 PM UTCresolved

   We have resolved the issue with the Data Importer that caused imports to be stuck in a pending status. To prevent inadvertent duplicate record imports in scenarios where users may have attempted the same import multiple times, imports that were stuck in pending status have been removed. Users should complete a new import process for any prior attempts that had been stuck.

1. May 4, 2026 at 7:48 PM UTCresolved

   On May 2, some users on US Platform Groups experienced intermittent errors when logging in due to issues in a portion of the authentication service. Users already logged in were not impacted. The issue has been resolved, and preventative improvements are underway.

1. April 20, 2026 at 1:43 PM UTCinvestigating

   We are currently investigating reports of degraded performance in Axiom for a subset of users.

2. April 20, 2026 at 1:55 PM UTCmonitoring

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

3. April 20, 2026 at 2:22 PM UTCresolved

   This incident has been resolved.

1. April 13, 2026 at 2:24 PM UTCinvestigating

   We are currently investigating an issue impacting Composer for a subset of users.

2. April 13, 2026 at 2:38 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 13, 2026 at 3:24 PM UTCmonitoring

   A fix has been deployed and Portals performance has stabilized. We are still closely monitoring Composer performance.

4. April 13, 2026 at 7:16 PM UTCresolved

   After monitoring for several hours, we can confirm that all systems are now operating normally. Between 9:35 AM ET and 11:10 AM ET, some users experienced degraded performance in Composer and Portals during a period of high usage. Our systems are designed to automatically add capacity when usage increases. However, when this process ran today, some of the additional capacity was not configured correctly, which limited our ability to absorb the increased demand. Once identified, we corrected the configuration and performance returned to normal. We apologize for the disruption and appreciate your patience.

1. April 7, 2026 at 4:28 PM UTCresolved

   Between 3:35 PM ET and 3:55 PM ET, a subset of users experienced errors when accessing Portals in the US. We identified an issue with a software update being performed and resolved the issue.

1. March 30, 2026 at 12:51 PM UTCinvestigating

   We are currently investigating an issue impacting the accessibility of Portals for a subset of users.

2. March 30, 2026 at 1:15 PM UTCidentified

   We have identified this issue and have updated the scope to reflect the impact on multiple Veracross platforms.

3. March 30, 2026 at 2:19 PM UTCidentified

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

4. March 30, 2026 at 4:41 PM UTCidentified

   We continue to work to address this issue. Intermittent access issues for schools on Platform Group US 30 are expected over the next 15 minutes. We apologize for this disruption and thank you for your continued patience.

5. March 30, 2026 at 8:15 PM UTCmonitoring

   We are continuing to monitor system health closely. Some users are still experiencing degraded performance. We we will be performing additional maintenance work to address this issue tonight. School contacts at impacted schools have been notified directly via email, and an in-app notification has been posted for users at those schools.

6. March 31, 2026 at 1:02 PM UTCmonitoring

   A subset of users on Platform Group US 30 are continuing to experience degraded performance across multiple platforms this morning despite the additional maintenance work we performed last evening. We are continuing to work to address these issues and will provide additional updates.

7. March 31, 2026 at 3:16 PM UTCmonitoring

   We will be performing additional emergency maintenance on Platform Group US 30 to continue mitigation efforts related to the ongoing performance issues. Learn more about determining your Platform Group here: https://community.veracross.com/s/article/What-is-My-Schools-Platform-Group This maintenance is scheduled for today from 12:00 PM to 12:20 PM ET. During this time, all Veracross services for Platform Group US 30 will be unavailable. We recognize the impact of this disruption and have determined this maintenance is necessary to support ongoing stabilization efforts. An in-app notification will be displayed to all impacted users in advance of the maintenance window. Our team will continue to monitor performance closely following the maintenance and will provide further updates as more information becomes available. We sincerely apologize for the continued disruption and appreciate your patience as we work to restore full service.

8. March 31, 2026 at 4:51 PM UTCmonitoring

   The emergency maintenance for Platform Group US 30 has been successfully completed. Initial results show meaningful improvements, but we continue to closely monitor performance.

9. March 31, 2026 at 9:58 PM UTCresolved

   After monitoring performance since the emergency maintenance was completed this afternoon, we can confirm that system performance has stabilized. Additionally, we sent an email update to designated school contacts at each school to provide a more comprehensive update regarding this incident.

1. March 3, 2026 at 6:59 PM UTCinvestigating

   We are investigating an issue with downloading the PDFs for checks in AP check batches.

2. March 3, 2026 at 8:24 PM UTCresolved

   This incident has been resolved.