meddbase had 12 outages in the last 2 years totaling 87h 4m of downtime — averaging 0.5 incidents per month.
There were 12 meddbase outages since October 20, 2025 totaling 87h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue affecting the new unified email configuration (SMTP/OAuth). We've temporarily disabled the feature while we investigate and will update this page once it's resolved. Existing email functionality (including OAuth SMTP for automated emails) is unaffected.
This incident has been resolved.
We are aware of the issue currently affecting the pathway functionality and are actively investigating.
We identified a database query issue that was impacting performance and have successfully resolved it. We are now seeing improved performance and continue to monitor the environment.
Service performance has returned to normal, and the issue is now resolved.
We are aware of an issue affecting our payment system and this is being investigated as a matter of urgency. At this time we belive this only impacting UK clients and will provide a further update as soon as one becomes available.
The Engineering team are continuing to investigate the Issue regarding payment and we will provide a further update as soon as we can.
The engineering team have investigated and confirmed that the issue with Payments has now been resolved.
We are aware of intermittent issues currently affecting SMS Delivery, Our team is actively investigating the root cause with our supplier and working to restore service as quickly as possible. We appreciate your patience and will provide further updates as soon as more information is available.
We are continuing to work on a fix for this issue.
We are continuing to work with our supplier to ascertain the root cause of the issue
We have received confirmation from our supplier that the issue has now been resolved. We are currently observing previously delayed SMS messages being successfully sent via our monitoring tools. There is still a slight delay as the system processes the backlog; however, this is expected to clear shortly. We will continue to monitor the situation closely and provide any further updates if needed.
We are aware of intermittent issues currently affecting Activity, which may also impact other areas of the system. Our team is actively investigating the root cause and working to restore service as quickly as possible. We appreciate your patience and will provide further updates as soon as more information is available.
This incident has been resolved.
We are aware of an issue impacting electronic prescription services. The issue lays with SignatureRX and you can track the status of the incident here: https://signaturerx.statuspage.io/
This incident has been resolved.
We are aware of an issue affecting our Pathology Labs integration and are actively investigating the cause.
Our engineering team have now confirmed that this issue has been fully resolved, Pathology Labs results are now processing as expected, but we are closely monitoring the system to ensure continued stability.
We are aware of an issue affecting our Australian clients ability to send SMS messages and are investigating with our supplier. If you are experiencing this issue please raise a case via the community for the latest updates.
We have worked with our supplier and have now resolved this issue.
We are aware of an issue affecting our 'Postcode Search' feature impacting the ability to perform postcode look ups, within address fields. If you are experiencing issues with postcode look up functionality this morning, please follow the guidance in the article below to utilise an alternate search, 'Fuzzy Search', which will replicate most functionality. Please click or paste this link into a new browser tab: https://userdocs.cority.com/articles/#!meddbase-help-center/25268545828637-address-lookup-fuzzy-search/ Or search 'Address Lookup - Fuzzy Search' on the Cority Community Page. We apologise for any inconvenience caused by this.
This issue has now been resolved, if you had turned on 'Fuzzy Search' and wish to return to the original postcode lookup experience, you can do so by simply turning off the 'Fuzzy Search' option in your chambers. For guidance on this process, please refer to the 'Address Lookup - Fuzzy Search' article. We appreciate your patience and understanding during this transition and apologise for any inconvenience caused.
We have identified an issue impacting our results being received from TDL. A hotfix has been implemented and deployed, and we are now observing results being processed. There was no downtime; however, some services may have experienced minor processing delays. All results from TDL, including any previously queued historic results, should now be processing as expected. We will continue to monitor the situation, but we are confident that the issue has been resolved.
We can confirm that the issues is fully resolved.
We have identified an issue impacting our accountancy software, Xero. A Hot Fix has been prepared and will be deployed shortly. This will only affect selected customers and may result in approximately 3 minutes of downtime for those impacted. We sincerely apologise for any inconvenience this may cause and appreciate your understanding as we work to resolve the issue promptly.
The Hot Fix has now been successfully deployed to most impacted clients, who should now be fully operational. We are continuing to deploy the fix for a small number of remaining clients and will provide further updates once this process is complete. Thank you for your patience and understanding as we work to ensure full resolution.
The Hot Fix has now been successfully deployed to all affected clients, and the issue is fully resolved.
We have been experiencing service disruption due to a widespread Amazon Web Services (AWS) outage. This is impacting some areas of the Meddbase application, including integrations dependent on AWS such as Twilio and Xero. Due to the same underlying issue, we have also been unable to update this page until now. AWS are actively working to restore normal operations, and the latest information we have is that the issue has mostly been mitigated. We will continue to monitor the situation closely, and if you are affected, please raise a case via the Community, where we will be able to share updates with you as they become available.
We are now observing a resumption of normal services which coincides with the latest updates from AWS that this underlying issue has been fully mitigated. We will continue to monitor the service, but believe the issue is now resolved.