Medius Outage History
Medius major outage · 1 active incident View live status →Pingoru has recorded 82 incidents for Medius: 78 in the last 12 months and 24 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 9 | 289 of 720 (40%) |
| May 2026 | 6 | 52 of 744 (7%) |
| June 2026 | 11 | 145 of 720 (20%) |
| July 2026 | 4 | 191 of 744 (26%) |
| August 2026 | 18 | 86 of 744 (12%) |
| September 2026 | 4 | 51 of 720 (7%) |
| October 2026 | 1 | 42 of 556 (8%) |
Incidents, newest first
Minor September 23, 2026 Capture US delay with processing PDF invoices 2h 1m Capture (US)
Started Sep 23, 2026, 03:04 PM UTC· resolved Sep 23, 2026, 05:06 PM UTC
- investigating Sep 23, 2026, 03:04 PM UTC
Due to an issue with our external OCR service provider, we are experiencing a delay in processing incoming PDF invoices in the US region. Approximately 10% of invoice ingestion is impacted.
- monitoring Sep 23, 2026, 04:10 PM UTC
The issue with our external OCR service provider has been mitigated. The backlog of impacted invoices has been processed, and invoice processing has returned to normal operations.
- resolved Sep 23, 2026, 05:06 PM UTC
This incident has been resolved.
Minor September 15, 2026 Cloud23 - Performance degradation 1d 23h Cloud23
Started Sep 15, 2026, 02:52 PM UTC· resolved Sep 17, 2026, 02:51 PM UTC
- investigating Sep 15, 2026, 02:52 PM UTC
We are currently investigating this issue.
- monitoring Sep 15, 2026, 04:07 PM UTC
Performance has stabilized. We continue to monitor the situation closely.
- monitoring Sep 16, 2026, 07:43 AM UTC
We are continuing to monitor for any further issues.
- resolved Sep 17, 2026, 02:51 PM UTC
This incident has been resolved.
Major September 14, 2026 Degraded Performance in Reporting (US) 43m Data Platform (US)
Started Sep 14, 2026, 08:47 PM UTC· resolved Sep 14, 2026, 09:31 PM UTC
- investigating Sep 14, 2026, 08:47 PM UTC
We are currently experiencing intermittent performance issues affecting report generation and data retrieval in the US region. Customers in this region may encounter delays or timeouts when accessing reports. This has been identified as being caused by a confirmed incident with the Azure Databricks SQL component in the US region. Our team is actively monitoring the situation and working with Databricks as they resolve the issue. We will provide updates as more information becomes available.
- resolved Sep 14, 2026, 09:31 PM UTC
The issue has been mitigated and service is operational.
Critical September 4, 2026 Cloud26 - Outage 31m Cloud26
Started Sep 04, 2026, 05:00 AM UTC· resolved Sep 04, 2026, 05:32 AM UTC
- investigating Sep 04, 2026, 05:00 AM UTC
Customers on Cloud26 may have problems connecting to AP Automation. We are investigating the issue.
- resolved Sep 04, 2026, 05:32 AM UTC
Access to AP Automation is restored for all customers.
Minor August 26, 2026 Capture performance degradation 2h 14m Capture (Europe)
Started Aug 26, 2026, 06:50 AM UTC· resolved Aug 26, 2026, 09:05 AM UTC
- investigating Aug 26, 2026, 06:50 AM UTC
We are investigating performance degradation affecting Medius Capture in the European region. Customers may experience delays in invoice processing.
- monitoring Aug 26, 2026, 08:38 AM UTC
The issue has been mitigated, and invoice processing performance has returned to normal.
- resolved Aug 26, 2026, 09:05 AM UTC
The issue has been mitigated, and invoice processing performance has returned to normal. Processing remained stable during the monitoring period. This incident is now resolved.
Minor August 26, 2026 Cloud (EU, UK) - Performance degradation 4h 30m Cloud02, Cloud10, Cloud13, Cloud20 and 4 more
Started Aug 26, 2026, 06:32 AM UTC· resolved Aug 26, 2026, 11:03 AM UTC
- identified Aug 26, 2026, 06:32 AM UTC
The issue has been identified and a fix is being implemented.
- identified Aug 26, 2026, 06:40 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 26, 2026, 07:19 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 26, 2026, 11:03 AM UTC
This incident has been resolved.
Minor August 17, 2026 Capture - Delayed processing of incoming emails 1h 46m Capture (Europe), Capture (US)
Started Aug 17, 2026, 02:15 PM UTC· resolved Aug 17, 2026, 04:02 PM UTC
- investigating Aug 17, 2026, 02:15 PM UTC
We are currently experiencing an issue affecting the processing of a subset of incoming emails in Capture. This may cause delays in some invoices appearing in the inbox. Our team is actively investigating.
- investigating Aug 17, 2026, 02:42 PM UTC
Processing of emails has been restored. We are now processing the backlog.
- resolved Aug 17, 2026, 04:02 PM UTC
The backlog has been fully processed. Email processing remains fully operational.
- postmortem Sep 16, 2026, 12:42 PM UTC
### Incident summary On 17 August 2026, a subset of incoming emails routed through Capture EU experienced processing delays. This also affected some US customers whose traffic is served from Europe. The issue affected messages that require an email service recipient lookup to identify the original recipient. Messages configured using Capture's recommended forwarding method were not dependent on this lookup and were not affected. ### Customer impact Some incoming emails remained in a pending state or entered a failure state while the recipient lookup was unavailable. ~50% of email input volume during the incident window was identified in the affected states. The affected email volume was a subset of all email inputs, not a loss of all incoming email processing. No data loss was identified. Once processing was restored, the backlog was processed and email processing returned to normal. ### Root cause The incident was caused by a failure in the email service recipient lookup path in Capture EU. The underlying provider-side cause could not be conclusively confirmed from the available evidence, so we are not attributing it to a specific provider fault in this report. ### Resolution and prevention Email processing was restored, and the accumulated backlog was fully processed on the same day. We are reviewing the email service integration and adding monitoring for recipient lookup failures so that a similar condition can be detected and addressed sooner. For the recommended forwarding configuration, Capture receives the original recipient directly and does not need the recipient lookup. Customers using an alternative forwarding configuration should follow the guidance in [Email forwarding in Office 365](https://success.medius.com/documentation/capture/user_guide/email_forwarding_in_Office_365/#automatic-email-forwarding).
Critical August 17, 2026 Cloud30 - Outage 22m Cloud30
Started Aug 17, 2026, 02:02 PM UTC· resolved Aug 17, 2026, 02:24 PM UTC
- investigating Aug 17, 2026, 02:02 PM UTC
Customers on Cloud30 may have problems connecting to AP Automation. We are investigating the issue.
- resolved Aug 17, 2026, 02:24 PM UTC
Access to AP Automation is restored for all customers.
Critical August 17, 2026 Cloud21 - Outage 39m Cloud21
Started Aug 17, 2026, 06:46 AM UTC· resolved Aug 17, 2026, 07:26 AM UTC
- investigating Aug 17, 2026, 06:46 AM UTC
Customers on Cloud21 may have problems connecting to AP Automation. We are investigating the issue.
Critical August 17, 2026 Cloud20 - Outage 56m Cloud20
Started Aug 17, 2026, 06:30 AM UTC· resolved Aug 17, 2026, 07:26 AM UTC
- investigating Aug 17, 2026, 06:30 AM UTC
Customers on Cloud20 may have problems connecting to AP Automation. We are investigating the issue.
Critical August 17, 2026 Cloud02, Cloud20, Cloud21 - Outage 9h 9m Cloud02, Cloud20, Cloud21
Started Aug 17, 2026, 05:51 AM UTC· resolved Aug 17, 2026, 03:00 PM UTC
- investigating Aug 17, 2026, 05:51 AM UTC
Customers on Cloud02 may have problems connecting to AP Automation. We are investigating the issue.
- identified Aug 17, 2026, 06:26 AM UTC
Incident affecting Cloud02 resulted in temporary disruptions due to a sharp increase in CPU usage. While auto-scaling measures activated as designed, additional manual capacity adjustments were required to restore access. Service is now restored. Our team is investigating the underlying cause to prevent recurrence.
- monitoring Aug 17, 2026, 08:14 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 17, 2026, 08:15 AM UTC
We are continuing to monitor for any further issues.
- resolved Aug 18, 2026, 04:29 AM UTC
This incident has been resolved.
Critical August 14, 2026 Cloud34 - Outage 24m Cloud34
Started Aug 14, 2026, 12:50 PM UTC· resolved Aug 14, 2026, 01:15 PM UTC
- investigating Aug 14, 2026, 12:50 PM UTC
Customers on Cloud34 may have problems connecting to AP Automation. We are investigating the issue.
- resolved Aug 14, 2026, 01:15 PM UTC
Access to AP Automation is restored for all customers.
Critical August 14, 2026 Cloud02 - Outage 54m Cloud02
Started Aug 14, 2026, 06:45 AM UTC· resolved Aug 14, 2026, 07:40 AM UTC
- investigating Aug 14, 2026, 06:45 AM UTC
Customers on Cloud02 may have problems connecting to AP Automation. We are investigating the issue.
- monitoring Aug 14, 2026, 07:29 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 14, 2026, 07:40 AM UTC
This incident has been resolved.
Critical August 13, 2026 Cloud10 - Outage 51m Cloud10
Started Aug 13, 2026, 12:30 PM UTC· resolved Aug 13, 2026, 01:21 PM UTC
- investigating Aug 13, 2026, 12:30 PM UTC
Customers on Cloud10 may have problems connecting to AP Automation. We are investigating the issue.
- resolved Aug 13, 2026, 01:21 PM UTC
Access to AP Automation is restored for all customers.
Major August 10, 2026 Cloud13 - Scheduled jobs outage 3h 23m Cloud13
Started Aug 10, 2026, 09:28 AM UTC· resolved Aug 10, 2026, 12:51 PM UTC
- investigating Aug 10, 2026, 09:28 AM UTC
Incident affecting Cloud13 has disrupted the performance of scheduled jobs, including imports and reports. While the exact cause is still under investigation, our team is actively working to resolve the issue and minimize further disruption.
- identified Aug 10, 2026, 09:42 AM UTC
Incident affecting Cloud13 is currently disrupting invoice processing functionality. The issue arose from a technical anomaly within a worker machine infrastructure. Remedial actions are underway, including resource adjustments and system restarts, though full restoration may take some time.
- monitoring Aug 10, 2026, 11:17 AM UTC
The issue has been resolved and the cloud is operational, late invoices may take a few hours to fully appear in the system. Our team is closely monitoring the situation and implementing measures to enhance system reliability.
- resolved Aug 10, 2026, 12:51 PM UTC
This incident has been resolved.
Notice August 4, 2026 Reporting Data Not Updating 3h 52m
Started Aug 04, 2026, 11:21 AM UTC· resolved Aug 04, 2026, 03:13 PM UTC
- investigating Aug 04, 2026, 11:21 AM UTC
We are currently investigating an issue where report data in Medius is not reflecting the latest updates. Invoices and other report data may appear outdated. Our engineering team is actively investigating. We will provide an update as soon as we have more information. We apologize for the inconvenience.
- investigating Aug 04, 2026, 01:10 PM UTC
We have identified the root cause of the reporting delay. Data is currently being processed. Reports will return to normal once processing is complete. We will post a final update when reports are fully up to date.
- resolved Aug 04, 2026, 03:13 PM UTC
The issue affecting report data has been resolved. Reports are recovering and data is being processed automatically. Some reports may still reflect a slight delay while the system catches up — no action is required. We apologize for the inconvenience.
Notice July 29, 2026 Email Service Disruption 4d 18h
Started Jul 29, 2026, 01:40 PM UTC· resolved Aug 03, 2026, 07:58 AM UTC
- identified Jul 29, 2026, 01:40 PM UTC
We are currently experiencing an issue affecting the purchase requisition notification emails. Our team is actively investigating.
Minor July 17, 2026 Email Service – Summary Email Disruption 4d 23h Cloud02, Cloud10, Cloud13, Cloud17 and 8 more
Started Jul 17, 2026, 07:15 AM UTC· resolved Jul 22, 2026, 06:53 AM UTC
- investigating Jul 17, 2026, 07:15 AM UTC
We are currently experiencing an issue affecting the delivery of summary notification emails. Our team is actively investigating. The following notification types may be impacted: • New task notifications — alerts when a document or task is assigned to a user's inbox • Document in inbox reminders — alerts for documents that have been pending beyond a configured number of days • Imminent due date reminders — alerts for invoices approaching their payment due date • Past invoice date reminders — alerts for invoices overdue for processing based on their invoice date • Overdue goods receipt reminders — alerts for purchase orders where goods have not been confirmed received past the expected delivery date We recommend checking your inbox directly in Medius in the meantime. We will provide further updates as our investigation progresses.
- investigating Jul 17, 2026, 12:50 PM UTC
Our team continues to investigate the issue affecting summary notification email delivery. No additional impact has been identified beyond what was reported at 07:15 UTC.
- investigating Jul 20, 2026, 09:04 AM UTC
We have identified the root cause and a fix is being deployed progressively across our environments. ✅ Resolved — cloud02, cloud10, cloud20: Notification emails are resuming as of this morning. 🔄 In progress — cloud17, cloud30, cloud34: Fix is planned for today. Notification emails are expected to resume later today. ⏳ Remaining environments: Fix is planned for tomorrow. We will confirm once deployed. We will post a final update once all environments have been resolved. Thank you for your patience.
- investigating Jul 20, 2026, 11:55 AM UTC
✅ Resolved — cloud17, cloud30, cloud34 (US region): Notification emails are now resuming. A fix for remaining environments is still planned for tomorrow. We will confirm once deployed.
- investigating Jul 21, 2026, 07:57 AM UTC
✅ Resolved — saas13, saas21, saas23, saas32: Notification emails are now resuming. 🔄 In progress — cloud26, cloud39: Fix is still being worked on. We will post a further update once these environments have been resolved.
- resolved Jul 22, 2026, 06:53 AM UTC
This incident has been resolved. Notification email delivery has been restored across all production environments. We apologise for the disruption this caused.
Notice July 15, 2026 Cloud39 - Performance degradation 10h 31m Cloud39
Started Jul 15, 2026, 01:27 AM UTC· resolved Jul 15, 2026, 11:58 AM UTC
- investigating Jul 15, 2026, 01:27 AM UTC
We are currently investigating a performance issue impacting customers on cloud39.
- monitoring Jul 15, 2026, 02:16 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 15, 2026, 07:07 AM UTC
We are continuing to monitor for any further issues.
- resolved Jul 15, 2026, 11:58 AM UTC
This incident has been resolved.
Minor July 6, 2026 (Cloud03/14/22)Delayed Reporting Data Processing 2h 4m Cloud03, Cloud14, Cloud22
Started Jul 06, 2026, 04:54 AM UTC· resolved Jul 06, 2026, 06:58 AM UTC
- investigating Jul 06, 2026, 04:54 AM UTC
We are currently investigating an issue affecting scheduled reporting/ETL data processing for a subset of tenants, resulting in delayed report data updates since the weekend. We are still working to confirm the underlying cause, and are deploying a change we expect will mitigate the issue. Other scheduled or long-running background tasks may also be affected; we are assessing the full scope. We will provide a further update shortly as we learn more.
- resolved Jul 06, 2026, 06:58 AM UTC
This issue has been resolved. Reporting data processing is back to normal. Thank you for your patience.
Critical June 30, 2026 Cloud17 - Outage 44m Cloud17
Started Jun 30, 2026, 03:28 PM UTC· resolved Jun 30, 2026, 04:13 PM UTC
- investigating Jun 30, 2026, 03:28 PM UTC
Customers on Cloud17 may have problems connecting to AP Automation. We are investigating the issue.
- resolved Jun 30, 2026, 04:13 PM UTC
Access to AP Automation is restored for all customers.
Notice June 30, 2026 Performance degradation –
Started Jun 30, 2026, 02:23 PM UTC· resolved Jun 30, 2026, 02:23 PM UTC
- resolved Jun 30, 2026, 02:25 PM UTC
Incident affecting Cloud34 resulted in users being unable to access their tasks, displaying an incorrect message about permissions or task existence. This was caused by a worker process becoming unhealthy and ceasing task processing, leading to a backlog. The issue, present from 13:06 to ~14:52, has been resolved. We are implementing measures to prevent future occurrences and appreciate your patience during this time.
Critical June 12, 2026 Cloud13 - Outage 4d 2h Cloud13
Started Jun 12, 2026, 07:46 AM UTC· resolved Jun 16, 2026, 10:22 AM UTC
- investigating Jun 12, 2026, 07:46 AM UTC
Customers on Cloud13 may have problems connecting to AP Automation. We are investigating the issue.
- monitoring Jun 12, 2026, 10:10 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 15, 2026, 08:16 AM UTC
We are still monitoring the results after the implemented fix.
- resolved Jun 16, 2026, 10:22 AM UTC
This incident has been resolved.
Minor June 10, 2026 Cloud32 - Potential performance degradation 1d 21h Cloud32
Started Jun 10, 2026, 12:52 PM UTC· resolved Jun 12, 2026, 10:09 AM UTC
- investigating Jun 10, 2026, 12:52 PM UTC
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.
- investigating Jun 10, 2026, 12:52 PM UTC
We are continuing to investigate this issue.
- identified Jun 10, 2026, 12:53 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 11, 2026, 04:58 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 12, 2026, 10:09 AM UTC
This incident has been resolved.
Minor May 18, 2026 Cloud26 - partial performance degradation 20h 31m Cloud26
Started May 18, 2026, 10:27 AM UTC· resolved May 19, 2026, 06:58 AM UTC
- investigating May 18, 2026, 10:27 AM UTC
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.
- investigating May 18, 2026, 12:11 PM UTC
We have implemented mitigation measures and are actively monitoring the current metrics.
- monitoring May 19, 2026, 06:26 AM UTC
We are currently monitoring the resources closely.
- resolved May 19, 2026, 06:58 AM UTC
This incident has been resolved.