meddbase Outage History
meddbase is up right nowPingoru has recorded 51 incidents for meddbase: 16 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 2 | 4 of 744 (1%) |
| June 2026 | 1 | 2 of 720 (0%) |
| July 2026 | 2 | 1 of 744 (0%) |
| August 2026 | 1 | 34 of 744 (5%) |
| September 2026 | 3 | 146 of 720 (20%) |
| October 2026 | 1 | 0 of 581 (0%) |
Incidents, newest first
Minor December 18, 2024 Electronic prescription performance issues 2h 30m Critcal Services
Started Dec 18, 2024, 04:02 PM UTC· resolved Dec 18, 2024, 06:33 PM UTC
- 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.
Minor November 12, 2024 Document Printing Performance 46m Non-Critical Services
Started Nov 12, 2024, 11:46 AM UTC· resolved Nov 12, 2024, 12:32 PM UTC
- 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.
Minor November 12, 2024 Prescription performance issues 1d Non-Critical Services
Started Nov 12, 2024, 10:39 AM UTC· resolved Nov 13, 2024, 11:04 AM UTC
- 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.