Status and uptime

A public status page is live at status.firstsix.com.au, with current service status and incident history. This is the plain-language backdrop to it: what the service is built on, and what to expect if something goes wrong.

Availability

First Six runs on managed infrastructure (a Sydney-region database and a global application edge) chosen for reliability. Two properties matter most for uptime:

• The application is stateless, which means no user data lives on the application servers themselves; the data sits in the database. A server can be replaced without losing anything.
• It deploys continuously, so a bad release can be rolled back quickly. Because the data is held separately, a rollback restores the previous code without touching the data behind it.

During an incident

If something is wrong, the team follows a documented incident process, in order:

1. Containment

   First, stop the bleeding. Limit the impact before doing anything else, which may mean rolling back the latest release.

2. Investigation

   Once the situation is stable, find the root cause rather than just the symptom.

3. Resolution and notice

   Send a clear "resolved" message to anyone affected. Institutions are notified through their agreed contact, within the window set in their agreement.

The status page

First Six's public status page is live at status.firstsix.com.au. It shows current service status and incident history, and you can subscribe there for updates. Significant incidents affecting your institution are also communicated directly through your support contact.

Common questions

Related