The TCSI Tracker displays the current status of TCSI and associated systems. It is updated whenever these statuses change.
To get notified about system outages, new user guides and other technical advice, subscribe to TCSI website alerts.
TCSI Tracker
| Environment | Status | Notes |
|---|---|---|
Webservice Alert |
Operating | Verification of Unique Student Identifiers (USI) was re-triggered on Thursday 30 January 2025 for all students with an unverified USI in TCSI (where the student has active unit enrolments on or after 1 January 2021). |
PRODA |
Operating | Please review the expiry dates of your B2B devices and renew the activation periods to ensure PRODA access will continue without disruption. Further information can be found in our PRODA guide. |
B2G APIs |
Operating |
Some providers have been experiencing intermittent system errors in the production environment since Tuesday 22 April 2025. You may see a '500' error returned when reporting via a Student Management System and 'SYSERROR' in TCSI Data Entry. Providers who encounter these intermittent errors are encouraged to provide a screenshot of the error message, the API logs, and context behind what triggered the message to TCSISupport@education.gov.au for further investigation. The URL that providers use to consume TCSI APIs - https://api.humanservices.gov.au had a certificate authority update, from Entrust to ssl.com, on Thursday 3 April 2025 at 8pm [AEDT] in production. If your vendor has a TLS truststore in your application that only currently trusts Entrust certificates, you will need to update that truststore to support ssl.com. From 28 February 2025, TCSI support will no longer return CHESSN notifications. For more information see the TCSI releases and upcoming development page. API system codes follow the National API Standards. TCSI Validation codes are TCSI specific and can be found on the TCSI Validations page. |
TCSI Data Entry |
Operating | Some providers have been experiencing intermittent system errors in the production environment since Tuesday 22 April 2025. You may see a '500' error returned when reporting via a Student Management System and 'SYSERROR' in TCSI Data Entry. Providers who encounter these intermittent errors are encouraged to provide a screenshot of the error message, the API logs, and context behind what triggered the message to TCSISupport@education.gov.au for further investigation. |
TCSI Analytics |
Operating | If you require production data from TCSI, that are not available from TCSI Analytics, please submit a data extract request. |
Production environment |
Operating |
Some providers have been experiencing intermittent system errors in the production environment since Tuesday 22 April 2025. You may see a '500' error returned when reporting via a Student Management System and 'SYSERROR' in TCSI Data Entry. Providers who encounter these intermittent errors are encouraged to provide a screenshot of the error message, the API logs, and context behind what triggered the message to TCSISupport@education.gov.au for further investigation. The URL that providers use to consume TCSI APIs - https://api.humanservices.gov.au had a certificate authority update, from Entrust to ssl.com, on Thursday 3 April 2025 at 8pm [AEDT] in production. If your vendor has a TLS truststore in your application that only currently trusts Entrust certificates, you will need to update that truststore to support ssl.com. The production release due on Friday, 25 April 2025, will not go ahead due to the public holiday. The next production release will occur on Friday 9 May 2025 and will continue fortnightly thereafter. The regular releases require an outage to TCSI Data Entry and B2G APIs from 8.00am to 10.00am [AEST]. Release notes will be available following a major production release. |
Test environment |
Operating |
From 4 March 2025, regular deployments to the test environment are scheduled for 8.00 am – 9.30 am [AEDT] on Tuesdays. Providers and TCSI developers can now apply to the test environment by completing the TCSI test account request. Delays may be experienced when assigning CHESSNs and verifying mock TFNs. |