- 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
- Aug 04, 2026, 06:33 AM UTC
- Resolved
- Aug 04, 2026, 10:12 AM UTC
- Duration
- 3h 39m
Affected: Cloud02
Timeline · 3 updates
-
investigating Aug 04, 2026, 06:33 AM UTC
Customers on Cloud02 may have problems connecting to AP Automation. We are investigating the issue.
-
monitoring Aug 04, 2026, 08:46 AM UTC
Incident affecting Cloud02 is currently disrupting operations due to a bug in the autoscaling code introduced during a recent runtime upgrade. Our team is actively addressing the issue to restore normal functionality and implement safeguards to prevent recurrence. Currently the workaround has been implemented and we are actively monitoring current performance. We apologize for any inconvenience caused and deeply appreciate your patience as we work to resolve this.
-
resolved Aug 04, 2026, 10:12 AM UTC
This incident has been resolved. Our team swiftly resolved the issue by rolling back to the previous version. We sincerely apologize for the disruption and are implementing measures to prevent similar occurrences. Thank you for your understanding and trust in us.
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 12, 2026, 05:36 AM UTC
- Resolved
- May 12, 2026, 06:02 AM UTC
- Duration
- 25m
Affected: Cloud26
Timeline · 2 updates
-
investigating May 12, 2026, 05:36 AM UTC
Customers on Cloud26 may have problems connecting to AP Automation. We are investigating the issue.
-
resolved May 12, 2026, 06:02 AM UTC
Access to AP Automation is restored for all customers.
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 →
- Detected by Pingoru
- May 04, 2026, 08:12 AM UTC
- Resolved
- May 04, 2026, 12:52 PM UTC
- Duration
- 4h 39m
Affected: Capture (Europe)
Timeline · 4 updates
-
investigating May 04, 2026, 08:12 AM UTC
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.
-
identified May 04, 2026, 08:34 AM UTC
We have identified an issue affecting email invoice processing. We have applied additional processing capacity and are seeing clear signs of recovery.
-
monitoring May 04, 2026, 10:47 AM UTC
Processing times for email invoice ingestion have returned to normal as of 10:00 UTC.
-
resolved May 04, 2026, 12:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 12:10 PM UTC
- Resolved
- Apr 28, 2026, 12:12 PM UTC
- Duration
- 2m
Affected: Cloud10
Timeline · 2 updates
-
investigating Apr 28, 2026, 12:10 PM UTC
Customers on Cloud10 may have problems connecting to AP Automation. We are investigating the issue.
-
resolved Apr 28, 2026, 12:12 PM UTC
Access to AP Automation is restored for all customers.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 04:48 PM UTC
- Resolved
- Apr 24, 2026, 07:42 PM UTC
- Duration
- 2h 53m
Affected: Capture (US)
Timeline · 4 updates
-
investigating Apr 24, 2026, 04:48 PM UTC
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.
-
identified Apr 24, 2026, 06:24 PM UTC
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.
-
monitoring Apr 24, 2026, 07:14 PM UTC
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.
-
resolved Apr 24, 2026, 07:42 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 04:32 PM UTC
- Resolved
- Apr 25, 2026, 07:12 AM UTC
- Duration
- 14h 40m
Affected: Dynamics 365 FODynamics 365 BCDynamics Ax 2012NetSuiteSAP
Timeline · 2 updates
-
identified Apr 24, 2026, 04:32 PM UTC
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.
-
resolved Apr 25, 2026, 07:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 02:51 PM UTC
- Resolved
- Apr 24, 2026, 04:13 PM UTC
- Duration
- 1h 22m
Affected: Data Platform (EU)
Timeline · 2 updates
-
investigating Apr 24, 2026, 02:51 PM UTC
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/
-
resolved Apr 24, 2026, 04:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 06:26 AM UTC
- Resolved
- Apr 17, 2026, 01:02 PM UTC
- Duration
- 6h 35m
Affected: Cloud23
Timeline · 4 updates
-
investigating Apr 17, 2026, 06:26 AM UTC
We are currently investigating this issue.
-
monitoring Apr 17, 2026, 07:00 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 17, 2026, 07:09 AM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 17, 2026, 01:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 07:30 AM UTC
- Resolved
- Apr 15, 2026, 01:40 PM UTC
- Duration
- 6h 10m
Affected: Capture (Europe)
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 07:03 AM UTC
- Resolved
- Apr 08, 2026, 05:54 AM UTC
- Duration
- 22h 50m
Affected: Cloud02Cloud10Cloud26
Timeline · 5 updates
-
investigating Apr 07, 2026, 07:03 AM UTC
We are currently investigating this issue.
-
identified Apr 07, 2026, 07:44 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 07, 2026, 07:45 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Apr 07, 2026, 11:07 AM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 08, 2026, 05:54 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 06:55 AM UTC
- Resolved
- Apr 14, 2026, 08:27 AM UTC
- Duration
- 7d 1h
Affected: Capture (Europe)Capture (US)
Timeline · 14 updates
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 11:56 AM UTC
- Resolved
- Apr 07, 2026, 11:05 AM UTC
- Duration
- 3d 23h
Affected: Data Platform (EU)
Timeline · 3 updates
-
investigating Apr 03, 2026, 11:56 AM UTC
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.
-
identified Apr 03, 2026, 03:23 PM UTC
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.
-
resolved Apr 07, 2026, 11:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 05:20 PM UTC
- Resolved
- Mar 31, 2026, 10:25 AM UTC
- Duration
- 17h 4m
Affected: Cloud17Cloud30Cloud34
Timeline · 2 updates
-
investigating Mar 30, 2026, 05:20 PM UTC
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.
-
resolved Mar 31, 2026, 10:25 AM UTC
This incident has been resolved.
Read the full incident report →