- Detected by Pingoru
- Sep 14, 2026, 08:47 PM UTC
- Resolved
- Sep 14, 2026, 09:31 PM UTC
- Duration
- 43m
Affected: Data Platform (US)
Timeline · 2 updates
-
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.
Read the full incident report →
Critical September 4, 2026 - Detected by Pingoru
- Sep 04, 2026, 05:00 AM UTC
- Resolved
- Sep 04, 2026, 05:32 AM UTC
- Duration
- 31m
Affected: Cloud26
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 06:50 AM UTC
- Resolved
- Aug 26, 2026, 09:05 AM UTC
- Duration
- 2h 14m
Affected: Capture (Europe)
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 06:32 AM UTC
- Resolved
- Aug 26, 2026, 11:03 AM UTC
- Duration
- 4h 30m
Affected: Cloud02Cloud10Cloud13Cloud20Cloud21Cloud23Cloud26Cloud32
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 02:15 PM UTC
- Resolved
- Aug 17, 2026, 04:02 PM UTC
- Duration
- 1h 46m
Affected: Capture (Europe)Capture (US)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 02:02 PM UTC
- Resolved
- Aug 17, 2026, 02:24 PM UTC
- Duration
- 22m
Affected: Cloud30
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 06:46 AM UTC
- Resolved
- Aug 17, 2026, 07:26 AM UTC
- Duration
- 39m
Affected: Cloud21
Timeline · 1 update
-
investigating Aug 17, 2026, 06:46 AM UTC
Customers on Cloud21 may have problems connecting to AP Automation. We are investigating the issue.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 06:30 AM UTC
- Resolved
- Aug 17, 2026, 07:26 AM UTC
- Duration
- 56m
Affected: Cloud20
Timeline · 1 update
-
investigating Aug 17, 2026, 06:30 AM UTC
Customers on Cloud20 may have problems connecting to AP Automation. We are investigating the issue.
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 05:51 AM UTC
- Resolved
- Aug 17, 2026, 03:00 PM UTC
- Duration
- 9h 9m
Affected: Cloud02Cloud20Cloud21
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 12:50 PM UTC
- Resolved
- Aug 14, 2026, 01:15 PM UTC
- Duration
- 24m
Affected: Cloud34
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2026, 06:45 AM UTC
- Resolved
- Aug 14, 2026, 07:40 AM UTC
- Duration
- 54m
Affected: Cloud02
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2026, 12:30 PM UTC
- Resolved
- Aug 13, 2026, 01:21 PM UTC
- Duration
- 51m
Affected: Cloud10
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 10, 2026, 09:28 AM UTC
- Resolved
- Aug 10, 2026, 12:51 PM UTC
- Duration
- 3h 23m
Affected: Cloud13
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 11:21 AM UTC
- Resolved
- Aug 04, 2026, 03:13 PM UTC
- Duration
- 3h 52m
Timeline · 3 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 01:40 PM UTC
- Resolved
- Aug 03, 2026, 07:58 AM UTC
- Duration
- 4d 18h
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 07:15 AM UTC
- Resolved
- Jul 22, 2026, 06:53 AM UTC
- Duration
- 4d 23h
Affected: Cloud02Cloud10Cloud13Cloud17Cloud20Cloud21Cloud23Cloud26Cloud30Cloud32Cloud34Cloud39
Timeline · 6 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 01:27 AM UTC
- Resolved
- Jul 15, 2026, 11:58 AM UTC
- Duration
- 10h 31m
Affected: Cloud39
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 04:54 AM UTC
- Resolved
- Jul 06, 2026, 06:58 AM UTC
- Duration
- 2h 4m
Affected: Cloud03Cloud14Cloud22
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 03:28 PM UTC
- Resolved
- Jun 30, 2026, 04:13 PM UTC
- Duration
- 44m
Affected: Cloud17
Timeline · 2 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 02:25 PM UTC
- Resolved
- Jun 30, 2026, 02:23 PM UTC
- Duration
- —
Timeline · 1 update
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 07:46 AM UTC
- Resolved
- Jun 16, 2026, 10:22 AM UTC
- Duration
- 4d 2h
Affected: Cloud13
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 12:52 PM UTC
- Resolved
- Jun 12, 2026, 10:09 AM UTC
- Duration
- 1d 21h
Affected: Cloud32
Timeline · 5 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 10:27 AM UTC
- Resolved
- May 19, 2026, 06:58 AM UTC
- Duration
- 20h 31m
Affected: Cloud26
Timeline · 4 updates
-
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.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 08:14 AM UTC
- Resolved
- May 12, 2026, 07:58 AM UTC
- Duration
- 23h 43m
Affected: Cloud23
Timeline · 3 updates
-
investigating May 11, 2026, 08:14 AM UTC
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.
-
monitoring May 11, 2026, 11:01 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 12, 2026, 07:58 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 09:08 AM UTC
- Resolved
- May 08, 2026, 11:18 AM UTC
- Duration
- 2h 10m
Affected: Cloud13
Timeline · 4 updates
-
investigating May 08, 2026, 09:08 AM UTC
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.
-
monitoring May 08, 2026, 09:32 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 08, 2026, 11:17 AM UTC
We are continuing to monitor for any further issues.
-
resolved May 08, 2026, 11:18 AM UTC
This incident has been resolved.
Read the full incident report →