Veracross had 40 outages in the last 2 years totaling 270h 18m of downtime — averaging 1.6 incidents per month.
There were 40 Veracross outages since February 13, 2025 totaling 270h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We have detected an outage for Documents in the US.
We are continuing to work on a fix for this issue.
This incident has been resolved.
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.
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.
We are currently investigating reports that Data Importer imports are stuck in pending status.
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.
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.
We are currently investigating reports of degraded performance in Axiom for a subset of users.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue impacting Composer for a subset of users.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been deployed and Portals performance has stabilized. We are still closely monitoring Composer performance.
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.
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.
We are investigating an issue with downloading the PDFs for checks in AP check batches.
This incident has been resolved.
Our Veracross Community AI Service Assistant is currently displaying an error message. We are investigating the issue in order to restore the chatbot feature as quickly as possible. In the meantime, you can still use normal Community search functions to find knowledge articles, and can still contact our support team through the usual support case entry form.
This incident has been resolved.
We have received reports of degraded system performance and database connection errors impacting a subset of users. We are continuing to investigate further.
We have identified intermittent performance issues caused by increased load on certain backend systems. The impact is limited to a subset of users in North America, while others may not experience any issues. Our engineering teams are actively working to optimize performance. For additional context, please refer to the email sent to school point people on Tuesday, February 3 (ET).
We have resolved the intermittent availability issues some users experienced earlier in the week. Please refer to the forthcoming email to school point people for more details about specific work done to resolve this issue. Thank you for your patience.
We are investigating an issue that is impacting Composer, Online (Re-)Enrollment, Program Registration, and Admissions 2.0 for a subset of users.
Composer performance has returned to normal.
This issue has been resolved, but we continue to closely monitor system performance.
We are currently investigating an issue impacting the access and submission of Behavior & Comments records and approval of Student Logistics Requests for a subset of users.
The issue impacting Behavior & Comments records has been fully resolved. After further investigation, we determined that Student Logistics Requests were not impacted by this issue and have updated the title of this incident accordingly.
We have identified an issue impacting the display of person record details screens. We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
Unfortunately, workspace-related functionality is now disabled again due to performance issues. Workspaces will not show in the workspace picker or on homepages. Additionally, new queries cannot be saved. However, existing queries are available and can be updated. We continue to make restoring functionality our top priority and will provide another update by 5 pm Eastern (22:00 UTC).
We have implemented additional improvements, and all query functionality has now been restored, including the ability to create and save new queries. While the main Workspaces page is visible again, accessing individual workspaces will still result in an error message at this time. We will provide an update at noon ET (17:00 UTC) tomorrow.
We continue to work on restoring access to individual workspaces. Query functionality remains fully available. We will provide another update by 5 pm Eastern (22:00 UTC).
We are continuing to work on restoring access to individual workspaces while ensuring system stability. We will provide another update by EOD tomorrow.
As communicated to school point people in today’s email from our CTO, the scope of this issue is now limited to workspace functionality. Further updates about workspace availability will be published directly within Axiom, providing greater visibility for impacted users. Please refer to our CTO update for more details, and thank you for your patience as we’ve worked to address this issue.
We will be performing emergency maintenance on a core database system beginning at 4:30 PM ET today. We expect this maintenance to last approximately 15 minutes. During this time, some applications and services will be unavailable for all customers. We apologize for the inconvenience and will be providing additional updates on restoring Axiom shortly.
This incident has been resolved.
We are currently investigating reports of authentication issues that are impacting a subset of users.
An upgrade this morning to our authentication system this morning resulted in users in some contexts being unable to log in to Veracross. Users previously logged in were not impacted. We have fixed the issue and users should be able to log in to Veracross again. We are monitoring this issue.
After monitoring this issue closely, we have confirmed that this incident has been resolved. We apologize for the inconvenience this issue has caused.
We are currently observing elevated errors from BlueSnap impacting payout report retrieval and causing receipt failures across our systems. BlueSnap previously reported that a recent infrastructure-related outage had caused sporadic connectivity failures. We are monitoring the situation closely and validating the impact on our platform. Further updates will be provided as soon as more information becomes available.
This incident has been resolved. Please note that any payments that failed will not be automatically retried/reprocessed and will need to be resubmitted by the payer. We apologize for this disruption and thank you for your patience.
We are currently investigating this issue.
This incident has been resolved.
We are investigating an issue causing email delivery delays for a subset of customers.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating reports that MFA verification codes are not being received by recipients.
We have identified the issue and determined that this is impacting a subset of users. We are working to implement a fix. In the meantime, instructions for changing the MFA authentication method can be found here: https://community.veracross.com/s/article/How-do-I-change-my-MFA-authentication-method
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
At approximately 3:30 AM EDT we were made aware of issues with the availability of our Data API due to an ongoing issue at our cloud provider. We are monitoring the situation and will provide further updates as we are able.