VETtrak incident

SQL Server Connectivity | 500 Internal Server Error

Critical Resolved View vendor source →

VETtrak experienced a critical incident on February 1, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 01, 2026, 10:50 PM UTC
Resolved
Jan 31, 2026, 02:00 PM UTC
Duration
—
Detected by Pingoru
Feb 01, 2026, 10:50 PM UTC

Update timeline

  1. resolved Feb 01, 2026, 10:50 PM UTC

    Over the weekend, VETtrak experienced a service interruption following an automated Windows update on one of the application servers. The update process triggered a server restart; however, the Microsoft SQL Server service did not automatically restart as expected. This resulted in the VETtrak application being unavailable until the issue was identified and resolved. Our engineering team investigated the incident, manually restored the SQL Server service, and confirmed full-service functionality. No data loss was identified as part of this incident. Preventative actions To reduce the risk of recurrence, we are implementing the following: Updating monitoring and alerting to immediately detect database service start-up failures after system restarts Automated service recovery attempts when failure is detected Reviewing automated patching behaviour to ensure critical services are validated post-update We apologise for any inconvenience caused and appreciate your patience while we worked to restore service.