Is meddbase Down Right Now? Check if there is a current outage ongoing.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The main Meddbase application will not be available for our Australian customers during the times stated. This is part of our regular weekly maintenance schedule. We apologise for any inconvenience caused during this time.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The main Meddbase application will not be available for our Canadian customers during the times stated. This is part of our regular weekly maintenance schedule. We apologise for any inconvenience caused during this time.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The main Meddbase application will not be available to our UK and EU users during the times stated. This is part of our regular weekly maintenance schedule. We apologise for any inconvenience caused during this time.

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.

We have now implemented the restart and are actively monitoring the situation to ensure it is resolved.

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.

This incident has been resolved.

We are aware of an issue with Pathways and we are investigating. We will update this when we have more information.

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.

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.

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.

The issue only affected one client on EU.

We are aware of an issue where our EU customers are unable to login to meddbase. This is currently being investigated.

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.

This incident has been resolved.

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.

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.

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.

We have now had confirmation that the fix rolled out by the provider has resolved the issue.

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.

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.

Following an overnight system refresh, this incident has now been resolved.

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.

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.

We can now confirm that the fix has been implemented and the issue has been resolved.

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.

We are continuing to work on a fix for this issue.

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.

This incident has been resolved.

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.

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.

We have managed to bring our databases back online and will begin restarting customer systems. We hope to restore access to the system shortly.

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.

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.

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.

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.

The immediate issue has been mitigated and we are seeing performance level return to normal

We are aware of performance issues impacting some UK sites and are currently investigating

Functionality is restored.

We are aware of SMS issues impacting some UK sites and are currently investigating

This incident has been resolved.

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.

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.

We are actively working to identify and resolve underlying issues affecting system stability.

This incident has been resolved.

We have now restored the reporting functionality for impacted clients on all historic data up to 22.30 yesterday evening and our team are working to restore access to 'live' data (after 22:30 to present). Clients on system 1 through to 10, system G and system I are not impacted by this issue nor is any other functionality in Meddbase impacted for any clients. Please contact our support team if you have any further queries.

We are aware Reports are not working for some of our customers and we are investigating.

Our service provider has informed us that this has been resolved and we have been able to test and confirm that all emails are sending as expected. We apologise for eany inconveniences caused during this time

We are aware of an issue delaying the sending of some emails. This is due to a reverse DNS problem being investigated by our upstream service provider. We apologise for any inconvenience.

This incident has been resolved.

Network based issue identified only affecting UK based clients using their own SMTP servers to send emails. This has since been resolved. We are monitoring to confirm system stability.

We are aware of an issue affecting general performance of the application. We are in the process of pinpointing the affecting features and cause. We apologise for any inconvenience caused and will be sure to keep you updated as we investigate.

This incident has been resolved.

Our engineers are continuing to investigate the pathways issue that we reported in the early hours of today. Some users may be experiencing timeout messages when using pathways but we are monitoring the situation and actively working to keep the service running with as limited an impact as possible. At the moment investigation is ongoing and as new information emerges we will keep the status page updated.

Following our scheduled maintenance we have encountered an issue with Pathways. This is being investigated, and we will update the page as we know more.

SMS functionality has been restored. Please continue to use this service as normal and re-send any messages or secure documents accordingly. We thank you for your understanding and apologise for any inconvenience caused.

We are aware of an issue affecting SMS messaging from the Meddbase application. This will also impact the sharing of secure documents as they utilise SMS two-factor authentication. At this point, we know the cause and are working on a resolution. We apologise for any inconvenience caused during this time.

Full functionality and stability restored We thank you for your patience and apologise for any inconvenience caused.

Reporting feature has been restored. We are continuing to monitor the situation and the effectiveness of the changes made. Please continue to use Meddbase and this feature as usual.

An issue affecting the running and building of reports in some of our UK based Meddbase environments has been identified. The reports feature will not be available until resolved. The cause has been identified and we are in the process of restoring the feature. More updates will be posted here as they become available. Thank you for your patience and we apologise for any inconvenience caused.

Card and online payments have been restored. A change to the Elavon / Opayo URLs resulted in an unexpected switch in security standards. This required an internal infrastructure change. We apologise for any inconvenience caused.

We are currently investigating

The issue affecting some of our UK environments with regards to the displaying of patient data has now been resolved and all data should be visible again. We are continuing to monitor the situation. We apologise for any inconvenience caused.

We are aware of an issue affecting some of our UK environments with regards to the displaying of patient data. Our engineers are investigating and will have an update soon.

System stability restored and cause identified. An update to the operating system of the servers hosting the Canadian environments caused an unforeseen issue which has since been resolved and measures put in place to prevent it happening again in the future Thank you for your patience and we apologies for any inconvenience caused.

Access to all Canadian environments has been restored. We are monitoring to ensure its stability.

We are aware of login issues affecting our Canadian environments. Our engineers are investigating. We will update our status page as soon as we have more information.

Our engineers were notified by our monitoring systems of performance issues at 10:05 AM, This was soon identified as a large data transfer operation causing excessive bandwidth consumption within our data centre, affecting our internal operations, application access, and overall performance. Once the cause was identified and stopped, our monitoring systems informed us that our available bandwidth had been restored allowing access to all UK based Meddbase environments. We apologise for any inconvenience this may have caused and continue to monitor system stability.

Access to all UK environments restored. Our engineers are monitoring the performance across all systems.

The cause has been identified as an underlying service on one of our backend servers. This services was consuming most of the bandwidth within our data centre. Restoring of access to the main Meddbase Application in progress

We are aware of performance and access related issues affecting all UK environments. Our engineers are investigating and updates will be provided via out Status Page

This incident has been resolved.

Currently investigating

This incident has been resolved.

We are continuing to investigate this issue.

Engineers are onsite and investigating.

This incident has been resolved.

We have tracked down the cause and are making changes to rectify it. Please use Firefox Browser as a temporary workaround as the issue has been isolated to Google Chrome and Mircosoft Edge. Thank you for your patience while we resolve this

We are aware of an ongoing issue affecting the signing and dispensing of E-Prescriptions. This is being investigated by our engineers. An update will be provided as soon as one becomes available. We apologise for any inconvenience.

This incident has been resolved.

We’re currently experiencing high load on our SMTP server which may result in emails being slow to deliver. Emails are still being sent and delivered, and we are monitoring the queue. As the queue clears, we expect performance to return to normal but are monitoring performance and doing everything we can to ensure this happens as quickly as possible.

UK and EU Environments only. In order to resolve an issue with booking and changing the payer for services, we were required to complete an update to the system this morning that resulted in a brief period of disruption (approx. 5mins) in accessing the system. This update was completed just before 09:00 GMT. This was not a decision taken lightly but was one necessary to resolve the issue as quickly as possible and minimise disruption. Apologies for any inconvenience this caused.

This incident has now been resolved

We are aware of issues with loading and saving Documents. We are working on fixing it as we speak. Sorry for the incovenience, we will update this page as soon as possible.

This incident has been resolved.

We are experiencing issues with one of our databases resulting in degraded performance for some systems.

This incident has been resolved.

We are currently experiencing technical issues in our data centre which are impacting our services. Our engineers are aware and investigating.

This incident has been resolved.

We are currently experiencing issues with one of our hosting providers resulting in application outages, our team are investigating.

This incident has been resolved.

Our DNS provider is currently experiencing technical issues. Because of this, you may experience issues sending emails from your Meddbase inbox to some mail providers using Meddbase SMTP. This is under investigation with our provider and we will update this page once we have more information. All other Meddbase functionality remains unaffected.

In the last hour our infrastructure team have made DNS changes and failed over our internet service provider in order to resolve performance issues on our UK environment. This should have now resolved the issue. We would like to apologise for any inconvenience caused. Should any users still encounter issues please do not hesitate to get in touch.

We are aware of reports that some UK clients are experiencing degraded performance when accessing Meddbase. Our engineers are investigating this and we will endeavour to resolve the situation as soon as possible. We will keep the status page up to date as new information arises and we apologise for any disruption caused.

This incident has been resolved.

We are continuing to investigate this issue.

A planned upgrade to the system that handles inbound user email has taken longer than anticipated. Emails sent to users during this time may be returned as undeliverable. We apologise for any inconvenience.

The previous issue with regard to running reports and PDF previews has been resolved across all environments. We apologise for any inconvenience caused during this time.

We are aware of an issue affecting some reports and PDF previews within the main Meddbase application. The cause has been identified and is in the process of being resolved in all live environments. These features should be operational shortly. Apologies for any inconvenience caused during this time.

All issues were resolved after the minor release last night Feel free to get in touch with our helpdesk if you have any questions or queries. We apologise for any inconvenience caused during this time.

We are aware of two issues currently affecting all environments. Namely the ability to dispense stock from appointments and the ability to book meetings with multiple attendees that have offset start times. Both issues have been identified and are currently being resolved and tested with the intention to release them tonight. We apologise for any inconvenience caused due to these issues.

Functionality of the reporting feature was restored on the evening of 17/01/2023 We apologise for any inconvenience caused and encourage you to get in touch with our support team if you have any questions or queries.

Efforts to restore the reporting feature are ongoing and functionality has been restored to some environments. This process will continue for the remainder of the evening with all environments having their reporting feature restored by the early hours of the morning. We apologise for any inconvenience caused during this time.

Reporting server is currently unavailable or intermittent on some of our UK environments. The cause has been identified, however, the fix will take several hours to implement. Due to this, we will only have another status update at or before 17:00 GMT today

Service has been restored and emails from external sources are no longer being blocked by our firewalls. We apologise for any inconvenience caused. Feel free to raise a ticket with our helpdesk if you have any questions or concerns.

We are continuing to work on a fix for this issue.

Currently, external emails into the main Meddbase application are being blocked. We are aware of the issue and our engineers are investigating. Updates to be provided as soon as more become available.

This incident has been resolved.

The service has been restored. Please let us know if you encounter any issues.

The team is continuing to investigate and resolve intermittent problems with availability.

Our UK clients may experience slow or delayed access to documents while we are restoring the high-capacity dedicated connection between our datacentres. We would like to assure all clients that there is no data loss or corruption, and the issue is caused by temporarily degraded connection.

Microsoft Azure are currently experiencing an issue which is affecting services that we use to provision Meddbase. Our engineers have put a fix in place which restored access to Meddbase. We are also working with the Microsoft Azure team to understand when the issue they are experiencing will be resolved. We apologise for any inconvenience this has caused.

Microsoft Azure are currently experiencing an issue which is affecting services that we use to provision Meddbase. Our engineers are working to put a fix in place which will restore access to Meddbase. We are also working with the Microsoft Azure team to understand when the issue they are experiencing will be resolved.

Our engineers are continuing to work on this issue. We apologise for the inconvenience. We will provide another update on this in the next 20 minutes.

Our engineers have identified the issue and are hoping to have this resolved shortly. We apologise for the inconvenience this has caused. We will provide an update on this in the next 20 minutes.

Our engineers are continuing to investigate this issue. We apologise for the inconvenience this has caused. We will provide an update on this in the next 20 minutes.

We are aware that accessing the log-in page for the EU environments is currently unavailable. We know this is frustrating and we’re working to resolve this as soon as possible. We have escalated this to our engineering team and will provide an update on this in the next 10 minutes.

Email firewall configuration updated and usual email services restored.

We have identified an issue with our email firewall blocking nonthreats. This will result in some emails being sent to your Meddbase environment being blocked. We have identified the cause and are in the process of restoring this service. Please be assured that there is no security threat related to this degraded service.

Following on from our email/update below we would like to provide further information regarding our Meddbase pathology integration. As part of the routine running of this integration we regularly receive invalid and erroneous messages from lab systems, our system correctly filters these out, during a recent incident we identified the possibility that some valid messages may also have been filtered. Without reprocessing the messages we are unable to ascertain whether you have been impacted by this, however, we believe the volume of valid messages in this situation to be very low. Nonetheless, as a precaution, we would like to reprocess all messages to ensure patient medical records are complete and up to date in Meddbase. We would like to complete this reprocessing on the evening of Wed 11th May. Following the reprocessing of these messages, you may notice new message notifications and review tasks appear in Meddbase on the morning of 12th May. Please review these as necessary although please note some of these may not be new and may already be known to clinicians. Other than acknowledging any reprocessed pathology tests in Meddbase there are no actions for you to take at this time. The functionality of the pathology system has now returned to normal and this issue will no longer impact the receiving of pathology results into Meddbase. We would like to apologise for any inconvenience caused.

We are continuing to investigate this issue.

Routine monitoring has alerted us to an issue with our Meddbase pathology integration meaning that a limited number of pathology result messages from labs have not been delivered. If you are not a user of the pathology integration in Meddbase you will not be affected. However, if you are a user of the Meddbase pathology integration then some patient records in Meddbase may contain incomplete or outdated pathology results. If you suspect you have any results missing from Meddbase please consult your lab portal and/or contact the lab directly regarding the pathology test in question. We are currently investigating the issue and aim to provide an update as soon as possible. We would like to apologise for any inconvenience caused and we will endeavour to keep you updated as our investigation continues as well as notify you once this issue is resolved.

We can confirm that our engineers have fixed the issue affecting email inboxes. No data has been lost as the emails were queued before being processed and sent to individual recipients. Should you require any further help, please log a ticket via our Helpdesk.

Our infrastructure engineers have applied a fix and we are currently monitoring its effectiveness.

We are continuing to investigate this issue. We apologise for any inconvenience caused.

We are currently experiencing an issue across all live environments with the receiving of emails. The sending of emails is unaffected. Our infrastructure engineers are aware of the issue and are working on a fix. We apologise for any inconvenience caused.

At 11:44 on 05/04 a billing rule that was self-referential was created. This should not be possible and is usually prevented in the user interface. This has not been seen before. It is not currently known how this was possible but our QA team are investigating. The 'self referential' rule caused an update message to be created in our service bus that was extremely long and malformed. This message is typically broadcast and so received by other Meddbase instances. Upon receipt of the 'bad message' the receiving system crashed. Technically, the malformed message created a 'stack overflow' due to its size and structure. Each time the affected system started back up, it would eventually resend the bad message and cause a cascade of failures elsewhere. The team first had to identify the cause of the crash, and this enabled them to work backwards to the system generating the message. Once the problem was understood, a data fix was applied to correct the 'self referential' rule. Some message queues were also cleared in the service bus, fortunately, these queues did not contain any customer data by design - only transient system notifications. These actions remediated the immediate problem and the next time sites were started up at approximately 16:22, they did not crash and have continued as normal since. The action we will take next is to investigate how the 'self referential' ruleset was created and take steps to prevent this in the future. Longer term, the current service bus implementation is approaching end of life and is due to be replaced by our engineering team. The replacement system is not susceptible to the same 'broadcast' problem, and this should further mitigate the risk of a future, similar event.

Full application functionality returned and stabilised We are continuing to monitor all components. If there are any remaining issues in your particular environment, please log a ticket via our helpdesk at https://helpdesk.meddbase.com/ We apologise for any inconvenience caused during this time. Please refer to our postmortem posted above for more info.

Hot fix applied and application access restored. We are monitoring the application and will provide any updates as they become available. Expect degraded and possible instability while the environments come online.

The hot-fix was unsuccessful, and the issue remains unresolved. Please expect system instability while the cause is identified. Updates will be posted as soon as they become available.

Restarting all UK environments to apply a hotfix. Please bear with us while application access is restored.

Application access for most environments has been restored. However, are still in the process of restoring other features within the main application. Please bear with us while complete functionality is restored. Thank you for your patience and we apologise for any inconveniences caused.

An underlying process vital to the operation of the main Meddbase application has unexpectantly failed affecting all UK based clients. We are yet to find the cause of this and reassure you that our engineers are in the process of restoring access. We thank you for your patience and apologise for any inconvenience caused.

The cause has been identified and our engineers are in the process of restoring access. We can confirm that all UK based environments are affected. More updates will be provided as soon as they become available.

Some of our live environments are currently inaccessible. We are aware of the issue and are in the process of restoring access. We apologise for any inconvenience caused during this time. Access should be restored soon.

Access to all live environments restored. We apologise for any inconvenience caused and please feel free to contact support if you have any further questions or queries.

We are aware of an issue resulting in some of our live environments not being accessible or slow. The issue has been identified and we are in the process of rectifying it. We apologise for any inconvenience caused

Send and receiving of emails restored for all live environments. All emails affected should be sent/received by now. Apologies for any inconvenience or delays caused. If you have any further questions or queries feel free to contact support.

We have reports of delays with emails. We are currently investigating.

Full email functionality restored as of 20:00 23/02. We apologise for any inconvenience caused and please feel free to contact Support if you have further questions or queries.

We are currently experiencing an issue across all live environments with the receiving of emails. The sending of emails is unaffected. Our infrastructure engineers are aware of the issue and are working on a fix. Please refer to our status page for the latest updates.

We can confirm that the issue affecting the running of reports in some of our live environments has now been resolved. We apologise for any inconvenience caused by this.

We are currently experiencing an issue running reports in some of our live environments. This is being investigated. An update will be provided as soon as it becomes available.