ResDiary had 19 outages in the last 2 years totaling 220h 5m of downtime — averaging 0.8 incidents per month.
There were 19 ResDiary outages since June 6, 2025 totaling 220h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue regarding users logging into their accounts
We have identified the issue, and we're beginning a fix.
A fix has been implemented and we are monitoring the results.
The fix has now rolled out successfully. Early indications are that this has resolved the issue. We are continuing to monitor the situation.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating the incident.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
ResDiary services experienced downtime due to a widespread Cloudflare outage impacting network connectivity and availability.
We are experiencing an issue with one of our third party software providers. This is affecting Access Identity logins and Dishcult.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating elevated CPU utilization on the Australia Diary production environment. This may result in degraded performance for some users. Our engineering team is actively working to identify the root cause and implement a resolution. Impact: Users may experience slower response times or intermittent issues when accessing the Australia Diary service.
The issue has been resolved by increasing the resource allocation.
We are currently investigating this issue.
Access Group is aware of an issue affecting Access Identity which is impacting multiple products. Access technical engineers have identified the fault and are working - as a priority activity - to resolve this. Access is committed to the highest levels of service quality; we apologise for the disruption caused and will provide further updates as swiftly as possible
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating some slowness in our Login service
We have implemented a fix and are monitoring the outcome.
We have identified a fix and are waiting for it to go out
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with Reserve with Google
The issue has been identified and a fix is being implemented.
We have identified an issue that caused our Reserve with Google integration to be disabled. The underlying issue has been resolved, but we've been unable to re-enable the Reserve with Google integration. We are continuing to work on this.
We are continuing to work on re-enabling our Reserve with Google integration. We have identified that customers are still able to update existing bookings, they just can't create new ones.
This incident has been resolved
We are aware of slowness while logging in. We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.