Veracross incident

Axiom Degraded Performance

Minor Resolved View vendor source →

Veracross experienced a minor incident on January 20, 2026 affecting Axiom US and Axiom EU and 1 more component, lasting 2d 9h. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 02:26 PM UTC
Resolved
Jan 22, 2026, 11:43 PM UTC
Duration
2d 9h
Detected by Pingoru
Jan 20, 2026, 02:26 PM UTC

Affected components

Axiom USAxiom EUAxiom AU

Update timeline

  1. investigating Jan 20, 2026, 02:27 PM UTC

    We are currently investigating this issue.

  2. identified Jan 20, 2026, 02:52 PM UTC

    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).

  3. identified Jan 20, 2026, 10:08 PM 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.

  4. identified Jan 21, 2026, 04:59 PM UTC

    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).

  5. identified Jan 21, 2026, 10:00 PM UTC

    We are continuing to work on restoring access to individual workspaces while ensuring system stability. We will provide another update by EOD tomorrow.

  6. resolved Jan 22, 2026, 11:43 PM UTC

    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.