Dashboard and app
Business dashboard, customer records and campaign tools
The app is serving and the database is responding.
Service status
Current availability and recent performance across the Starworks platform, checked automatically every 30 minutes.
No active incidents or scheduled maintenance
Components
Business dashboard, customer records and campaign tools
The app is serving and the database is responding.
Automated SMS review request delivery
No SMS review requests were due in the last 3 hours, so there is nothing failing.
Automated email review request delivery
No email review requests were due in the last 3 hours, so there is nothing failing.
Scheduled sync of Google reviews and ratings
Google review imports are completing normally.
Public Starworks Score cards and local rankings
Directory data is reachable.
Routing quotes, bookings and enquiries to businesses
Enquiry records are reachable.
Support email and in-app live chat
The live chat service is responding.
Automated checks began on 11 August 2026 and run every 30 minutes. Earlier days show as clear because no incident was logged against them.
Incident history
Every period a system was not fully operational, recorded automatically.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 4:08 am AEST. Recovered 4:37 am AEST, after about 30 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 1:51 am AEST. Recovered 2:07 am AEST, after about 16 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
The database was unreachable during this period, so pages that read data were failing.
Started 3:10 pm AEST. Recovered 3:37 pm AEST, after about 27 minutes.
4 of 18 review imports failed in the last 6 hours.
Started 2:37 pm AEST. Recovered 7:56 pm AEST, after about 5 hours.
Errors have been reported on this system in the last hour.
Started 1:07 pm AEST. Recovered 2:07 pm AEST, after about 1 hour.