- Detected by Pingoru
- May 19, 2026, 11:33 AM UTC
- Resolved
- May 19, 2026, 12:38 PM UTC
- Duration
- 1h 4m
Affected: Non-Critical Services
Timeline · 2 updates
-
investigating May 19, 2026, 11:33 AM UTC
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.
-
resolved May 19, 2026, 12:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 08:43 AM UTC
- Resolved
- May 19, 2026, 12:38 PM UTC
- Duration
- 3h 54m
Affected: Non-Critical Services
Timeline · 2 updates
-
identified May 19, 2026, 08:43 AM UTC
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/
-
resolved May 19, 2026, 12:38 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 26, 2026 - Detected by Pingoru
- Feb 26, 2026, 09:41 AM UTC
- Resolved
- Feb 26, 2026, 11:17 AM UTC
- Duration
- 1h 36m
Affected: Critcal Services
Timeline · 2 updates
-
investigating Feb 26, 2026, 09:41 AM UTC
We are aware of an issue affecting our Pathology Labs integration and are actively investigating the cause.
-
resolved Feb 26, 2026, 11:17 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 09:39 PM UTC
- Resolved
- Feb 20, 2026, 11:49 AM UTC
- Duration
- 14h 10m
Affected: Non-Critical Services
Timeline · 2 updates
-
investigating Feb 19, 2026, 09:39 PM UTC
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.
-
resolved Feb 20, 2026, 11:49 AM UTC
We have worked with our supplier and have now resolved this issue.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 09:12 AM UTC
- Resolved
- Feb 12, 2026, 12:27 PM UTC
- Duration
- 1d 3h
Affected: Non-Critical Services
Timeline · 2 updates
-
identified Feb 11, 2026, 09:12 AM UTC
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.
-
resolved Feb 12, 2026, 12:27 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Dec 19, 2025, 09:44 AM UTC
- Resolved
- Dec 19, 2025, 10:20 AM UTC
- Duration
- 35m
Affected: Critcal Services
Timeline · 2 updates
-
monitoring Dec 19, 2025, 09:44 AM UTC
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.
-
resolved Dec 19, 2025, 10:20 AM UTC
We can confirm that the issues is fully resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 09:40 AM UTC
- Resolved
- Nov 18, 2025, 10:17 AM UTC
- Duration
- 36m
Affected: Critcal Services
Timeline · 3 updates
-
identified Nov 18, 2025, 09:40 AM UTC
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.
-
monitoring Nov 18, 2025, 10:03 AM UTC
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.
-
resolved Nov 18, 2025, 10:17 AM UTC
The Hot Fix has now been successfully deployed to all affected clients, and the issue is fully resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 10:17 AM UTC
- Resolved
- Oct 20, 2025, 11:33 AM UTC
- Duration
- 1h 16m
Affected: Non-Critical Services
Timeline · 2 updates
-
monitoring Oct 20, 2025, 10:17 AM UTC
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.
-
resolved Oct 20, 2025, 11:33 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 09:10 AM UTC
- Resolved
- Aug 01, 2025, 11:52 AM UTC
- Duration
- 2h 42m
Affected: Application AccessCritical ServicesNon-Critical Services
Timeline · 5 updates
-
investigating Aug 01, 2025, 09:10 AM UTC
We are aware of a performance issue affecting some UK customers and are actively investigating the cause.
-
investigating Aug 01, 2025, 09:46 AM UTC
Our team is actively investigating the issue and continuing to work through potential causes. We’ve taken several steps so far, including recycling key systems, but the issue persists. Please rest assured that resolving this remains our top priority.
-
investigating Aug 01, 2025, 10:27 AM UTC
We're continuing to investigate the root cause of the issue and are running a number of processes to help stabilise performance. You may still experience slower response times while this work is ongoing. We're monitoring the situation closely and will provide further updates as we make progress.
-
monitoring Aug 01, 2025, 11:09 AM UTC
We have taken actions that appear to have addressed the performance issue. Initial results indicate considerable performance improvements, but we are closely monitoring the system to ensure continued stability.
-
resolved Aug 01, 2025, 11:52 AM UTC
The solution we implemented has successfully mitigated the issue, and all clients should be able to access the system without further problems. The incident is now considered resolved, but we will continue to monitor the system to ensure ongoing stability.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 04:20 PM UTC
- Resolved
- Jul 02, 2025, 05:08 PM UTC
- Duration
- 48m
Affected: Critical Services
Timeline · 2 updates
-
investigating Jul 02, 2025, 04:20 PM UTC
We are aware of an issue affecting the ability of some customers to upload documents. This is being treated as a high priority incident and we are actively investigating.
-
resolved Jul 02, 2025, 05:08 PM UTC
We identified an IO performance issue with our document storage platform, which has now been rectified, and full functionality has been restored. The incident is now considered resolved, but we will continue to monitor the system to ensure ongoing stability.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2025, 09:54 AM UTC
- Resolved
- Jun 19, 2025, 10:01 AM UTC
- Duration
- 7m
Affected: Non-Critical Services
Timeline · 3 updates
-
identified Jun 19, 2025, 09:54 AM UTC
We are currently aware of an issue affecting some clients' ability to print to PDF and have identified a solution which we are actively looking to implement.
-
monitoring Jun 19, 2025, 09:58 AM UTC
We have implemented a solution that we believe addresses the issue and are currently monitoring the system closely to ensure stability and confirm resolution.
-
resolved Jun 19, 2025, 10:01 AM UTC
This incident has now been resolved
Read the full incident report →
- Detected by Pingoru
- May 20, 2025, 09:27 AM UTC
- Resolved
- May 20, 2025, 12:59 PM UTC
- Duration
- 3h 31m
Affected: Application AccessCritical Services
Timeline · 3 updates
-
identified May 20, 2025, 09:27 AM UTC
We are currently experiencing performance issues with our back-end databases, which may be causing timeouts for some UK customers. To resolve the problem, we will be performing a system restart. This may temporarily require some users to log back into the application. We are actively monitoring the situation and will continue to provide updates on this status page.
-
monitoring May 20, 2025, 09:54 AM UTC
We have now implemented the restart and are actively monitoring the situation to ensure it is resolved.
-
resolved May 20, 2025, 12:59 PM UTC
The issue has now been stabilised, and we will be implementing additional changes this evening to ensure it is fully resolved. We will continue to monitor the situation closely until all updates have been completed.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2025, 05:21 PM UTC
- Resolved
- Apr 16, 2025, 06:42 PM UTC
- Duration
- 1h 21m
Affected: Critical Services
Timeline · 2 updates
-
investigating Apr 16, 2025, 05:21 PM UTC
We are aware of an issue with Pathways and we are investigating. We will update this when we have more information.
-
resolved Apr 16, 2025, 06:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2025, 08:58 AM UTC
- Resolved
- Apr 01, 2025, 10:06 AM UTC
- Duration
- 1h 8m
Affected: Application Access
Timeline · 3 updates
-
investigating Apr 01, 2025, 08:58 AM UTC
We are aware of an issue currently affecting clients' ability to access the main Meddbase application on our EU servers. This is currently being investigated as a top priority.
-
identified Apr 01, 2025, 09:48 AM UTC
We have identified the issue as a failure of a server which has lost connection to its internal storage. Our team is actively exploring workarounds and coordinating with Azure Support to understand the cause of the issue.
-
resolved Apr 01, 2025, 10:06 AM UTC
We now have confirmation that application access for EU environments has been restored. The server failure was caused by a Microsoft Azure outage for Northern Europe, which has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2025, 07:59 AM UTC
- Resolved
- Mar 27, 2025, 08:23 AM UTC
- Duration
- 24m
Affected: Application AccessCritcal ServicesNon-Critical Services
Timeline · 2 updates
-
investigating Mar 27, 2025, 07:59 AM UTC
We are aware of an issue where our EU customers are unable to login to meddbase. This is currently being investigated.
-
resolved Mar 27, 2025, 08:23 AM UTC
The issue only affected one client on EU.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2025, 09:02 AM UTC
- Resolved
- Mar 18, 2025, 09:02 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 18, 2025, 09:02 AM UTC
We were made aware of an issue at approx. 08:09 this morning preventing new patients from being created. This issue was caused as we introduced validation checks against the referrer name in the system in order to streamline our codebase. This caused an error to appear due to the presence of invalid data in our database and more specifically an empty referrer was selected. To resolve this, a SQL query was run to update the invalid entries to "Deleted – Do not use", restoring functionality by 08:36. There is no downstream impact, and we will review and optimise the validation logic in a future release.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2025, 08:57 AM UTC
- Resolved
- Feb 25, 2025, 10:44 PM UTC
- Duration
- 13h 46m
Affected: Non-Critical ServicesNon-Critical Services
Timeline · 4 updates
-
investigating Feb 25, 2025, 08:57 AM UTC
We are aware of an issue affecting our reporting functionality impacting some of our users. We are actively reviewing this and will provide further updates via this Status Page and on tickets raised via our support desk.
-
investigating Feb 25, 2025, 10:05 AM UTC
Our Engineering team are continuing to investigate the issue and has identified a possible cause for the error. We will continue to provide updates as and when they are available.
-
monitoring Feb 25, 2025, 10:50 AM UTC
Thank you for your patience while we performed our investigation. We have now successfully replicated the issue and identified the cause of the reporting error reported by some UK clients. We can confirm that this issue only affects clients in the UK and EU. To resolve it, we will be scheduling a system release for 22:30 GMT this evening (25th February 2025). No changes or releases will be deployed before this time to minimise system unavailability and prevent disruption to business-critical activities for our clients. We apologise for any inconvenience caused to you and your clients during this time, and we appreciate your patience while we work to resolve the issue.
-
resolved Feb 25, 2025, 10:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 18, 2024, 04:02 PM UTC
- Resolved
- Dec 18, 2024, 06:33 PM UTC
- Duration
- 2h 30m
Affected: Critcal Services
Timeline · 3 updates
-
investigating Dec 18, 2024, 04:02 PM UTC
We are aware of an issue with electronic prescribing that is impacting some of our users. We are actively reviewing this and will provide further updates via this Status Page and on respected support tickets. Should you have further details please log a support ticket.
-
monitoring Dec 18, 2024, 06:21 PM UTC
We can confirm that there have been no recent changes or updates within Meddbase that would affect the prescribing function. Based on our investigation, the issue appears to be related to the external provider of this functionality. The provider has informed us that they have made updates to their system today, which may be contributing to the issue. They have now rolled out a fix which they believe should resolve this and we are currently monitoring the results.
-
resolved Dec 18, 2024, 06:33 PM UTC
We have now had confirmation that the fix rolled out by the provider has resolved the issue.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2024, 11:46 AM UTC
- Resolved
- Nov 12, 2024, 12:32 PM UTC
- Duration
- 46m
Affected: Non-Critical Services
Timeline · 4 updates
-
identified Nov 12, 2024, 11:46 AM UTC
We are aware of an issue impacting a small number of users ability to print documents. We are currently investigating this as a matter of urgency and will update this page once more information is available.
-
identified Nov 12, 2024, 12:03 PM UTC
We are continuing to work on a fix for this issue.
-
monitoring Nov 12, 2024, 12:06 PM UTC
We've discovered that there’s a problem with how some files are being loaded into the browser. Specifically, one of our scripts is trying to access HTML files without using a proper version identifier. This means some browser were loading older, cached versions of these files, which now have broken links and can’t display properly. To fix this, we plan to update the script so that it always fetches the newest versions of these HTML files. After making this change, we'll clear the cache on our side so that your browser downloads the latest versions of everything the next time you access the page. This should resolve the issue and a further update will be sent when this is complete.
-
resolved Nov 12, 2024, 12:32 PM UTC
We can now confirm that the fix has been implemented and the issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2024, 10:39 AM UTC
- Resolved
- Nov 13, 2024, 11:04 AM UTC
- Duration
- 1d
Affected: Non-Critical Services
Timeline · 3 updates
-
investigating Nov 12, 2024, 10:39 AM UTC
We are aware of an issue impacting prescription services on System E and are currently investigating. We will update this page once more information is available.
-
monitoring Nov 12, 2024, 10:56 AM UTC
Following an initial issue early this morning with prescribing in our UK environment, that has since been resolved, we have become aware of ongoing issues with prescribing from the system that may impact some users. The majority of users should have access to prescribing functionality as usual. However, we are aware that some users may be faced with an error message when prescribing. This is due to caching. We are actively monitoring the issue and can confirm that a system refresh overnight will resolve any outstanding issues. In the meantime should you be one of the few users/clients impacted by any ongoing issue, please raise a support ticket.
-
resolved Nov 13, 2024, 11:04 AM UTC
Following an overnight system refresh, this incident has now been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2024, 10:49 AM UTC
- Resolved
- Oct 22, 2024, 09:47 PM UTC
- Duration
- 10h 58m
Affected: Non-Critical ServicesNon-Critical Services
Timeline · 2 updates
-
monitoring Oct 22, 2024, 10:49 AM UTC
We are aware of an issue that is currently affecting some clients ability to amend appointments and plan to release a fix this evening at 10.30pm that will rectify this issue. Please accept our apologies for any inconvenience caused to you and your clients during this time.
-
resolved Oct 22, 2024, 09:47 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 24, 2024 - Detected by Pingoru
- Sep 24, 2024, 04:13 PM UTC
- Resolved
- Sep 24, 2024, 07:35 PM UTC
- Duration
- 3h 22m
Affected: Application Access
Timeline · 6 updates
-
investigating Sep 24, 2024, 04:13 PM UTC
We are aware of issues impacting users logging into the Meddbase UK environment. We are currently investigating this as a matter of urgency and will update this page once more information is available.
-
investigating Sep 24, 2024, 04:55 PM UTC
We continue to investigate and attempt to resolve the issue impacting the availability of our UK system. Data that was being saved in the system against a Clinical Form should be saved once the system resumes. Other actions will have surfaced an error to users and will have to be repeated. We may need to restart the system to resolve the login issues. Please note that the system will be unavailable during restarts. This page will be updated regularly including once the system becomes operational again.
-
investigating Sep 24, 2024, 06:19 PM UTC
Our engineers are currently investigating if the cause of the outage is server related in an attempt to further isolate the issue which will then allow us to take steps to address this. We will keep this page updated and endeavour to give notice if we suspect this issue to continue in the medium term. Our engineers all continue to work beyond typical working hours to ensure the system becomes operational as soon as possible.
-
identified Sep 24, 2024, 06:51 PM UTC
We have narrowed the issue to being related to our Microsoft SQL Server Availability groups causing various client systems and our microservices to become unavailable. Our engineers are actively attempting to diagnose the problem and resolve it. There is currently no risk of data loss. The issue appears to be related to the failover cluster that ensures that Meddbase data is replicated between two locations at all times. This has caused the databases to become inaccessible since it is unable to replicate any transactions to the replicas. We are currently unable to see why the replicas are not syncing as the network is fully functional. We continue to investigate the issue and are considering all options possible to bring the systems back online safely.
-
identified Sep 24, 2024, 07:28 PM UTC
We have managed to bring our databases back online and will begin restarting customer systems. We hope to restore access to the system shortly.
-
resolved Sep 24, 2024, 07:35 PM UTC
We have now restored system access for all UK customers. Our teams will continue to monitor the situation but this incident is now resolved and system use can resume. A postmortem and investigation of this incident will follow.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2024, 03:31 PM UTC
- Resolved
- Sep 18, 2024, 04:05 PM UTC
- Duration
- 34m
Affected: Application Access
Timeline · 2 updates
-
investigating Sep 18, 2024, 03:31 PM UTC
We are aware of performance issues impacting some UK sites and are currently investigating
-
resolved Sep 18, 2024, 04:05 PM UTC
The immediate issue has been mitigated and we are seeing performance level return to normal
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2024, 09:51 AM UTC
- Resolved
- Sep 11, 2024, 10:13 AM UTC
- Duration
- 22m
Affected: Non-Critical Services
Timeline · 2 updates
-
investigating Sep 11, 2024, 09:51 AM UTC
We are aware of SMS issues impacting some UK sites and are currently investigating
-
resolved Sep 11, 2024, 10:13 AM UTC
Functionality is restored.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2024, 08:43 AM UTC
- Resolved
- Aug 19, 2024, 08:49 AM UTC
- Duration
- 5d
Affected: Application Access
Timeline · 4 updates
-
investigating Aug 14, 2024, 08:43 AM UTC
We are actively working to identify and resolve underlying issues affecting system stability.
-
investigating Aug 14, 2024, 09:53 AM UTC
We are continuing to monitor and implement mitigations to stabilise performance. We are aware that some clients on UK systems 1 to 11 continue to be affected intermittently but all other environments are stable. We are observing longer periods of stability on affected systems before slowness is observed again. We will continue to monitor the situation and keep this status page updated.
-
monitoring Aug 14, 2024, 12:44 PM UTC
The immediate issue has been mitigated through an urgent fix. We're monitoring the situation and will keep you updated with any important updates throughout the day.
-
resolved Aug 19, 2024, 08:49 AM UTC
This incident has been resolved.
Read the full incident report →