Zanda incident
Zanda not loading or slow to load, error code 500 for some users
Zanda experienced a major incident on October 13, 2026 affecting AU/Global Infrastructure (AU/Global - Clinic App), lasting 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 13, 2026, 02:18 AM UTC
We’re aware that many users are currently unable to access Zanda, or are seeing pages load very slowly before showing an “error code 500” or “Something went wrong” message. This may affect the calendar, client files, logging in and starting telehealth sessions. Our team is actively investigating and working to restore full access as quickly as possible. We’ll post another update here as soon as we have more information. We appreciate your patience in the meantime.
- resolved Oct 13, 2026, 02:28 AM UTC
The issue affecting access to Zanda has now been resolved, and all systems are operating normally. We experienced an issue with our Australian database which caused some connections to time out and then fail. Users may have seen slow loading, “error code 500” or “Something went wrong” messages during this time. It then recovered, and was initially slow for some users as the system recovered to full capacity. Full access has been restored, and we’re continuing to monitor and investigate what caused the database failure. If you were saving notes, appointments or payments between 12:55pm and 1:15pm, it’s worth checking that they saved correctly. Thanks again for your patience throughout.