All Systems Operational

AP Automation Operational
Cloud02 Operational
Cloud03 Operational
Cloud04 Operational
Cloud08 Operational
Cloud10 Operational
Cloud13 Operational
Cloud14 Operational
Cloud17 Operational
Cloud18 Operational
Cloud20 Operational
Cloud21 Operational
Cloud22 Operational
Cloud23 Operational
Cloud24 Operational
Cloud25 Operational
Cloud26 Operational
Cloud27 Operational
Cloud30 Operational
Cloud32 Operational
Cloud34 Operational
Cloud37 Operational
Cloud38 Operational
Cloud39 Operational
Cloud40 Operational
Demo01 Operational
Demo02 Operational
Demo03 Operational
Demo07 Operational
Demo08 Operational
Services Operational
Analytics Operational
Capture (Europe) Operational
Capture (US) Operational
Data Platform (EU) Operational
Data Platform (US) Operational
Expense Operational
MiCloud (Prod) Operational
MiCloud (QA) Operational
Office 365 Operational
Pay Operational
Pay (Corpay) Operational
Supplier Mgmt Operational
Supplier Portal Operational
ERP Cloud Connectors Operational
Dynamics 365 FO Operational
Dynamics 365 BC Operational
Dynamics Ax 2012 Operational
NetSuite Operational
SAP Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Apr 22, 2026

No incidents reported today.

Apr 21, 2026

No incidents reported.

Apr 20, 2026

No incidents reported.

Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026
Cloud23 - Partial Outage
Resolved - This incident has been resolved.
Apr 17, 13:02 UTC
Update - We are continuing to monitor for any further issues.
Apr 17, 07:09 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 07:00 UTC
Investigating - We are currently investigating this issue.
Apr 17, 06:26 UTC
Apr 16, 2026

No incidents reported.

Apr 15, 2026
Capture — Pagero invoice ingestion disruption
Postmortem - Read details
Apr 15, 15:43 UTC
Resolved - The incident has been resolved. The backlog of invoices that accumulated during the disruption has been processed.
Apr 15, 13:40 UTC
Monitoring - 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.
Apr 15, 09:44 UTC
Identified - 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.
Apr 15, 08:27 UTC
Investigating - 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.
Apr 15, 07:30 UTC
Apr 14, 2026
Capture - Delayed processing of incoming emails
Postmortem - Read details
Apr 14, 14:37 UTC
Resolved - This incident has been resolved.
Apr 14, 08:27 UTC
Monitoring - A permanent fix has been applied. Capture alias management has been restored to normal operation. We are currently monitoring system stability.
Apr 13, 22:21 UTC
Update - 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.
Apr 10, 14:43 UTC
Update - 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.
Apr 9, 15:22 UTC
Update - The backlog of affected invoices has been fully processed. Incoming email processing remains operational and we are continuing to monitor the situation.
Apr 9, 05:39 UTC
Update - 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.
Apr 9, 04:32 UTC
Update - 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.
Apr 8, 14:02 UTC
Update - 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.
Apr 7, 20:50 UTC
Update - Capture alias management functionality is currently not working, as it depends on the same faulty component.
Apr 7, 12:03 UTC
Update - 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.
Apr 7, 11:48 UTC
Update - We have started observing the issue in the US region as well.
Apr 7, 10:36 UTC
Identified - 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.
Apr 7, 10:00 UTC
Investigating - 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.
Apr 7, 06:55 UTC
Apr 13, 2026
Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026
Apr 9, 2026
Apr 8, 2026
Cloud02, Cloud10, Cloud26 - Degraded performance
Resolved - This incident has been resolved.
Apr 8, 05:54 UTC
Update - We are continuing to monitor for any further issues.
Apr 7, 11:07 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 7, 07:45 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 7, 07:44 UTC
Investigating - We are currently investigating this issue.
Apr 7, 07:03 UTC
← Incident History Powered by Atlassian Statuspage