There were 14 Medius outages since March 4, 2026 totaling 471h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 experiencing an issue affecting the processing of incoming invoices from Pagero in the Europe region. Our systems have been unable to retrieve invoices from Pagero since approximately 12:00 UTC on April 14th. We are actively investigating the cause.
The disruption is caused by a problem with the Pagero platform, which we have reported to Pagero and are working with them to resolve. We will provide a further update once we have more information.
Processing of Pagero invoices has been restored. The issue on the Pagero platform has been resolved and our systems are now successfully retrieving invoices. We are monitoring to confirm full recovery and that the backlog of affected invoices is being processed.
The incident has been resolved. The backlog of invoices that accumulated during the disruption has been processed.
## What happened On April 14 at approximately 14:00 CEST, a defect in the Pagero platform caused all requests from Medius Capture to the Pagero invoice API to be rejected. As a result, no invoices were retrieved from Pagero during the disruption period. The Medius Capture integration service continued to operate and retried automatically throughout the disruption. When the Pagero platform recovered, Capture automatically resumed retrieving invoices without any manual intervention and began processing the accumulated backlog. We became aware of the issue at approximately 08:30 CEST on April 15 following a customer report. ## Customer impact * All Pagero invoice ingestion in the European region was interrupted from approximately 14:00 CEST on April 14 until ~11:20 CEST on April 15. * Invoices that were available in Pagero during this period were not retrieved or processed until after service was restored. * The accumulated invoice backlog was fully processed by approximately 13:00 CEST on April 15 — no invoices were lost. * Customers in the US region and non-Pagero channels were not affected. ## Root cause The disruption was caused by a defect in the Pagero platform. A supplier submitted an invoice containing an invalid date value that Pagero's API could not handle, causing the API to reject all requests during the affected window. This was confirmed and resolved by Pagero support.
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 an issue affecting the processing of a subset of incoming emails in Capture, causing some invoices to be delayed or not appear in the inbox. Our team is actively investigating.
We have identified a faulty infrastructure component responsible for the integration with our mail service. We have reported the issue to our cloud provider support and are actively working on restoring it to operation.
We have started observing the issue in the US region as well.
We have implemented an alternative connection to our mail service, bypassing the faulty component. Processing of the backlog of stuck emails has started. In parallel, we are continuing to work on restoring the faulty component to full operation.
Capture alias management functionality is currently not working, as it depends on the same faulty component.
We have identified the root cause of the issue. A change rolled out by our cloud provider affected the integration with our mail service, causing the processing disruption. As a workaround, we have implemented an alternative connection path and incoming email processing has been restored. However, the Capture email alias management functionality remains unavailable as it depends on the same affected component. We are working on a permanent fix and will provide a further update once it is restored.
Incoming email processing has remained stable since the workaround was applied. We are continuing to work on restoring the email alias management functionality. A permanent fix requires an update from our mail service provider, and we are in contact with their support to expedite this.
The workaround solution implemented for incoming email processing experienced an unexpected failure overnight. It has been restarted and is now operational. Processing of the backlog of affected invoices is currently underway. We apologize for the additional disruption and continue to work on a permanent fix with our mail service provider.
The backlog of affected invoices has been fully processed. Incoming email processing remains operational and we are continuing to monitor the situation.
We have partially restored the email alias management functionality. However, alias creations triggered by users require manual intervention by our support team and can take up to 24 hours to propagate.
Incoming email processing remains stable. We are continuing to work on fully restoring the email alias management functionality in cooperation with our mail service provider's support team.
A permanent fix has been applied. Capture alias management has been restored to normal operation. We are currently monitoring system stability.
This incident has been resolved.
## What happened On 2026-04-07, a change rolled out by our email infrastructure provider caused the Capture service to be unable to reliably connect to its mail integration service. This affected incoming email processing and the management of Capture email aliases \(process addresses\) in both the European and US regions. The issue was detected by our operations team in the morning of 2026-04-07, and a status page incident was opened at 06:55 UTC. A temporary workaround was applied on the same day at 11:48 UTC, which restored email processing. A permanent fix — migrating to a more resilient authentication method — was deployed on 2026-04-13 and confirmed fully operational by 2026-04-14 08:27 UTC. ## Customer impact * Incoming email processing experienced delays starting 2026-04-07. Email processing was restored via workaround at ~11:48 UTC on the same day, with a brief interruption overnight on 2026-04-09 that was resolved by 05:39 UTC. * Email alias \(process address\) management was unavailable from 2026-04-07 12:03 UTC. New alias creation required manual support intervention until 2026-04-09 15:22 UTC, and was fully self-service again from 2026-04-13 22:15 UTC. * All emails submitted during the incident were retained and processed — no data was lost. ## Root cause Our email integration service relies on a cloud provider-supplied component to authenticate and communicate with the underlying mail service. On 2026-04-07, our cloud provider rolled out a security enforcement change that triggered a compatibility issue in that component, causing authentication to fail and requests to the mail service to be rejected. The root cause was a defect in the provider-supplied component, confirmed by the provider's support team. We resolved the incident by migrating our mail service integration to a different, more resilient authentication method that is not subject to this issue.
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 currently experiencing an issue in Capture that is affecting the processing of incoming emails. This is causing delays in displaying them in the APA/MediusGo inbox. Our team is actively investigating the issue.
We have identified the root cause of the issue affecting the processing of incoming emails in Capture. The disruption was caused by an unexpected infrastructure upgrade on the environment hosting our application. This unplanned activity led to service instability. We are working to stabilize the platform and mitigate the impact.
The system is still struggling to return to normal operation. Unfortunately, in the meantime it has become even more unstable, and the performance impact is now more severe. We are attempting to overprovision our infrastructure to mitigate the impact.
We are continuing to work on a fix for this issue. The majority of incoming traffic should now be processing, however a subset of it is still blocked. We have requested assistance from our cloud provider to help resolve the remaining problems.
We are continuing to work on a fix for this issue.
The system has started to show signs of recovery. All invoices sent into the system after 15:30 UTC should now be processed in a timely manner. We have also started processing the backlog of stuck or failed invoices.
The system has remained stable since the last update regarding the processing of incoming invoices. We are continuing to work through the backlog of invoices affected by the incident.
The backlog of affected invoices has now been fully processed, and the system has remained stable.
## What happened On Monday 2026-03-23, invoice processing in the European Capture cluster experienced significant delays lasting ~13 hours. The issue was detected at 08:16 UTC by our operations team, and a status page incident was opened at 08:44 UTC. The team scaled additional capacity and performed targeted recovery actions throughout the day. Processing was fully restored by 16:00 UTC, and all backlogged invoices were cleared by 21:52 UTC. ## Customer impact * Invoice processing through email and API channels experienced delays throughout the day. * During the peak impact period \(approximately 08:00–15:00 UTC\), a significant portion of invoices took longer than normal to appear in customer inboxes. * Some customers experienced timeouts when approving invoices in the correction/validation workflow. * All invoices submitted during the incident were ultimately processed — no data was lost. * A small number of duplicate invoices were created during recovery operations; affected customers have been identified and notified. ## Root cause An unplanned infrastructure maintenance operation by our cloud provider caused internal resource contention on the European processing cluster. The system's resource reserves were insufficient to maintain normal processing throughput while the maintenance was in progress.
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.
Pingoru polls Medius's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required