Störungsverlauf von Veracross

1. 8. September 2026 um 21:15 UTCinvestigating

   Wir untersuchen derzeit Berichte über Fehler beim Versuch, uns in die Veracross Community einzuloggen.

2. 8. September 2026 um 21:38 UTCidentified

   Wir glauben, dass wir die Quelle der Veracross Community-Login-Fehler identifiziert haben und daran arbeiten, einen Fix zu implementieren.

3. 8. September 2026 um 21:51 UTCmonitoring

   Wir haben einen Fix implementiert und überwachen nachfolgende Logins in der Veracross Community.

4. 8. September 2026 um 22:09 UTCresolved

   Wir haben bestätigt, dass der Fix den Anmeldefehler für die Veracross Community behoben hat.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. August 2026 um 20:38 UTCinvestigating

   Wir untersuchen derzeit einen Vorfall, der sich auf Buchhaltung und E-Mails (vollständiger Ausfall) und Dateien (degradierte Erfahrung) auswirkt.

2. 31. August 2026 um 20:42 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 31. August 2026 um 20:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. August 2026 um 21:39 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit der Zeitanzeige in Axiom, das UTC und nicht die tatsächliche Zeitzone der Schule falsch verwendet.

2. 27. August 2026 um 22:54 UTCresolved

   Dieser Vorfall wurde behoben und jede Datenbank zeigt nun die Zeit korrekt in der Zeitzone der Schule an.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. August 2026 um 16:08 UTCinvestigating

   Wir untersuchen derzeit einen Vorfall mit der Abfrageexportfunktionalität in Axiom.

2. 20. August 2026 um 16:20 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 23:39 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

2. 18. August 2026 um 00:18 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 18. August 2026 um 05:00 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. August 2026 um 15:51 UTCinvestigating

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

2. 12. August 2026 um 16:11 UTCresolved

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

1. 11. August 2026 um 17:14 UTCinvestigating

   Wir untersuchen derzeit Berichte, dass Datenimporteure im ausstehenden Status stecken bleiben.

2. 11. August 2026 um 17:27 UTCresolved

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

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. Juli 2026 um 00:59 UTCinvestigating

   Wir untersuchen derzeit dieses Problem.

2. 31. Juli 2026 um 01:02 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 31. Juli 2026 um 01:08 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 21:14 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das dazu führt, dass Maßnahmen in einem anhängigen Staat stecken bleiben. Wir arbeiten daran, dieses Problem zu beheben und werden Updates bereitstellen, sobald wir in der Lage sind.

2. 22. Juli 2026 um 21:29 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. Juli 2026 um 19:22 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

2. 20. Juli 2026 um 19:42 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. Juni 2026 um 21:38 UTCidentified

   We have detected an outage for Documents in the US.

2. 18. Juni 2026 um 21:53 UTCidentified

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

3. 18. Juni 2026 um 22:26 UTCresolved

   This incident has been resolved.

1. 16. Juni 2026 um 00:10 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. 4. Juni 2026 um 15:38 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. 4. Juni 2026 um 14:04 UTCinvestigating

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

2. 4. Juni 2026 um 15:33 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. 4. Mai 2026 um 19:48 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. 20. April 2026 um 13:43 UTCinvestigating

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

2. 20. April 2026 um 13:55 UTCmonitoring

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

3. 20. April 2026 um 14:22 UTCresolved

   This incident has been resolved.

1. 13. April 2026 um 14:24 UTCinvestigating

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

2. 13. April 2026 um 14:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 13. April 2026 um 15:24 UTCmonitoring

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

4. 13. April 2026 um 19:16 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. 7. April 2026 um 16:28 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. 30. März 2026 um 12:51 UTCinvestigating

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

2. 30. März 2026 um 13:15 UTCidentified

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

3. 30. März 2026 um 14:19 UTCidentified

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

4. 30. März 2026 um 16:41 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. 30. März 2026 um 20:15 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. 31. März 2026 um 13:02 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. 31. März 2026 um 15:16 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. 31. März 2026 um 16:51 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. 31. März 2026 um 21:58 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. 3. März 2026 um 18:59 UTCinvestigating

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

2. 3. März 2026 um 20:24 UTCresolved

   This incident has been resolved.