Is Medius down?

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.

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.

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.

✅ 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.

✅ 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.

This incident has been resolved. Notification email delivery has been restored across all production environments. We apologise for the disruption this caused.

We are currently investigating a performance issue impacting customers on cloud39.

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 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.

This issue has been resolved. Reporting data processing is back to normal. Thank you for your patience.

Customers on Cloud17 may have problems connecting to AP Automation. We are investigating the issue.

Access to AP Automation is restored for all customers.

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.