Medius had 49 outages in the last 2 years totaling 716h 19m of downtime — averaging 2 incidents per month.
There were 49 Medius outages since June 18, 2025 totaling 716h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
Customers on Cloud13 may have problems connecting to AP Automation. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
We are still monitoring the results after the implemented fix.
This incident has been resolved.
We are experiencing issues on Cloud 32 affecting some users in specific regions. Users may see errors such as "Could not load home page gadget data" or "Something went wrong" when opening invoices, loading the home page, or saving comments. The issue is caused by a recent platform update that removed support for certain regional timezone configurations. Our team has identified the root cause and is working on a fix. Not all users are affected.
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.
This incident has been resolved.
An incident impacting Cloud26 is currently affecting master data imports and report generation due to issues with the worker role. The root cause is still under investigation. Our team is working diligently to resolve the issue and minimize disruption. We apologize for any inconvenience caused and remain committed to delivering reliable services. Thank you for your patience as we address this matter.
We have implemented mitigation measures and are actively monitoring the current metrics.
We are currently monitoring the resources closely.
This incident has been resolved.
Customers on Cloud26 may have problems connecting to AP Automation. We are investigating the issue.
Access to AP Automation is restored for all customers.
Some customers may experience delays or failures in master data processing, voucher status updates, and invoice visibility in Medius/Capture. Our teams are actively working on this and will provide updates as soon as more information is available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some customers on cloud13 may experience delays or failures in master data processing, voucher status updates, and invoice visibility in Medius/Capture. Our teams are actively working on this and will provide updates as soon as more information is available.
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 increased processing times for email-based invoice ingestion in the EU region. Customers submitting invoices via email may experience delays of up to 30 minutes before processing begins. All other ingestion channels (Pagero, API upload, e-invoice) are unaffected.
We have identified an issue affecting email invoice processing. We have applied additional processing capacity and are seeing clear signs of recovery.
Processing times for email invoice ingestion have returned to normal as of 10:00 UTC.
This incident has been resolved.
Customers on Cloud10 may have problems connecting to AP Automation. We are investigating the issue.
Access to AP Automation is restored for all customers.
We are currently investigating elevated invoice processing times affecting Capture US customers. Processing delays are currently around 50 minutes above normal thresholds. Our engineering team has identified the cause and infrastructure scaling has been triggered to restore normal throughput.
We have identified the root cause of the delays. Invoice processing for Capture US customers is currently experiencing significant slowdowns due to an infrastructure issue with our cloud provider in the US region. This is preventing our systems from scaling up to handle the current workload as expected. We are actively working with our cloud provider to resolve the underlying infrastructure issue and restore normal processing capacity. Invoices submitted after 15:00 UTC are most affected and may experience delays of up to 90 minutes.
Invoice processing for Capture US customers has been restored. Our systems have recovered and are processing invoices at normal capacity as of approximately 18:50 UTC. Invoices submitted between 15:00–19:00 UTC today may have experienced delays of up to 90 minutes. All invoices have been processed — no data has been lost. We will continue monitoring to ensure full stability and will post a final update once we have confirmed complete recovery.
This incident has been resolved.
We are currently experiencing a performance degradation in the Cloud Connectors platform affecting the US region. The issue seems to be related to Multiservice issues on cloud provider side in East US region.
This incident has been resolved.
We are currently experiencing a performance degradation in the Data Platform affecting the US region. The issue is related to compute resource availability, and we are investigating in coordination with our cloud providers, including Azure Databricks: https://status.azuredatabricks.net/
This incident has been resolved.
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.
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.
This incident has been resolved.
We are currently experiencing intermittent performance issues affecting report generation and data retrieval in the European region. Customers in this region may encounter delays or timeouts when accessing reports. Our team is actively investigating and working to resolve the issue as quickly as possible. We will provide updates as more information becomes available.
We are currently experiencing performance issues with report data retrieval in our application in Europe. This is caused by degraded performance of the Azure Databricks SQL Warehouse. Our team is actively working with the Databricks support team to investigate and resolve the issue. We will provide updates as soon as more information becomes available. We apologize for any inconvenience this may cause and appreciate your patience.
This incident has been resolved.
We are currently investigating performance degradation affecting a subset of customers on Cloud17, Cloud30, and Cloud34 in the US region. Our team is actively working to identify the root cause and restore normal performance as quickly as possible.
This incident has been resolved.
We are experiencing an issue with exporting invoices from Capture to MediusGo. Almost all invoices sent to workflow after 07:45 CET are impacted. We are actively investigating the issue.
We have identified that one of the infrastructure components is in an impaired state. Unfortunately, a restart did not help. We are continuing our investigation.
We are still working on fixing the faulty infrastructure component.
We are continuing to work on resolving the faulty infrastructure component. We managed to restore operation, but it eventually entered an unpaired state again.
The fix has been applied. We are processing the backlog of failed invoices. At the same time, we are monitoring the system’s stability.
This incident has been resolved.
We have identified an issue in the latest release that prevents users with the Chinese language setting from accessing APA. Our engineering team is actively investigating the root cause. Temporary workaround: Please change user language setting to any option other than Chinese. This mitigate the access problem immediately.
We have identified the root cause of the access issue. The fix is currently being implemented and will be deployed to all affected environments as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
After the release of the new version, the Capture integration with APA became broken. Adding an incoming invoice to APA Inbox and sending it to the workflow is currently not working. We are actively investigating the issue.
We identified a regression that broke the integration and are preparing a rollback to restore service.
The rollback is currently in progress.
The rollback has been completed, and the integration has been fully restored. We are now processing the previously failed invoices.
We have processed 75% of the backlog. However, we have identified cases that cannot be automatically restarted and require manual patching.
85% of backlog was procees.
This incident has been resolved.
We are currently experiencing an issue with our AI model infrastructure, which is causing reduced functionality in some AI-powered features. This impacts Supplier Conversations, Supplier Statements, and Copilot.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Dear Users, Our telemetry detected that our OCR may have some slowness in processing some receipts and invoices. Workaround: Please use the manual entry while our teams are working on resolving the issue.
Dear Users, our technical team has identified the issue and is actively working on a resolution.
The issue has been identified and a fix is being implemented.
A fix has been implemented, and we are currently monitoring the results.
This incident has been resolved.
Due to an outage with our email service provider in the North America region, injecting emails into Capture via email is currently not working. We are in contact with the provider’s support team, who have confirmed they are aware of the issue and are actively working to restore service.
We have started to see incoming email traffic successfully reaching and being processed by Capture
The injection continues to remain stable. We are continuing to monitor the situation.
From our perspective, the issue with the email service provider has been fully resolved, and normal service operations have been restored. Based on the current injection pattern, we believe that the backlog of emails previously stuck in transit has now been delivered and processed in Capture.
We are currently experiencing degraded performance in the European region. The team is actively investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.