Cin7 had 14 outages in the last 2 years totaling 1597h 37m of downtime — averaging 0.6 incidents per month.
There were 14 Cin7 outages since April 11, 2026 totaling 1597h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Users are reporting that the B2B Portal is failing to load and eventually displays a **"This site can't be reached"** error.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are investigating intermittent reports of "Our Servers are busy at the moment" errors in Cin7 Core.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We have received reports of performance issues within the Reports module. Reports remain in an "Initializing" state for an extended period, eventually becoming "Unavailable". In some cases, reports successfully load but fail when users attempt to export them.
We identified a spike that may have contributed to the behavior being reported. The situation now appears to be clear, and we are continuing to monitor it.
We are continuing to monitor the incident.
Customers get an "Invalid Stripe API version". This is permissions related and we are working with Stripe to resolve it.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are currently investigating this incident.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Some Cin7 Pay merchants using Core may experience errors when accessing embedded payment components or processing payments directly within the Sales module. Payments initiated through document templates (quotes, orders, invoices) and the B2B Portal continue to process normally. We have escalated the issue to Stripe, who is actively working on a resolution. We will provide updates as they become available.
We are continuing to work on a fix for this incident with our payment partner Stripe. This incident is also impacting new sign-ups and payments from document templates.
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are investigating an issue where emails are successfully triggered in Core but failing to deliver to end customers.
We have implemented a fix and are currently monitoring the result. Emails should now start sending again.
While the fix has ensured that emails are flowing normally, "send from/reply to" custom domains will not work until a further fix is implemented. Meanwhile, in order to send emails currently, you need to change your [Send emails from settings](https://help.core.cin7.com/hc/en-us/articles/9034490726415-Introduction-to-document-and-email-templates#heading-7). This will change the **From** field to a Cin7/Dear email address; 1. Select **Settings** from the main menu, then **General settings**. 2. Go to the **Organization** section. 3. Look for setting **Send emails from** and select an available option: * Company's billing contact (sent from the system) * Currently logged-in user (sent from the system) We apologize for any inconvenience and will update here when this issue is fully resolved.
We are continuing to work on a fix for enabling customers to use the send from functionality.
We have implemented a fix and have confirmed that email delivery and send from / reply to functionality is now fully restored. Thank you for your patience while we worked on this.
A fix is being worked on for this issue.
As a temporary workaround, please update the tax type on the **“Exempt Sale”** rule to **“Tax on Sales.”** To help prevent this setting from reverting before the fix is released, we recommend reducing the frequency of Xero syncs where possible. If auto-sync is enabled, consider temporarily disabling it and using manual syncs only. Please note that running a sync may reset the tax type setting. If this occurs, you’ll need to reapply the change before creating any additional sales orders.
We are continuing to work on a fix for this incident.
We are continuing to work on a fix for this issue.; Meanwhile there is a workaround for customers where the tax type can be changed to "Tax on Sales" and by reducing the frequency of syncs with Xero, ideally via manual sync at longer intervals to avoid the tax type being over-ridden by Xero
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
We are investigating an issue where customer first and last names are missing from the delivery address on B2B orders.
This incident has been resolved.
We are investigating technical errors affecting product listings for Magento. Users may see 'runtime' or 'index out of bounds' errors during the listing process. Our team is working on a fix
We’ve completed work on a fix for this issue, and it is scheduled to be included in this weekend’s release.
This incident has been resolved.
Customers are currently unable to list products to Magento and Amazon Seller from the integration screen due to the following runtime error: "Could not load file or assembly 'Ben.Demystifier, Version=0.4.0.0, Culture=neutral, PublicKeyToken=a6d206e05440431a' or one of its dependencies. The system cannot find the file specified."
We implemented a fix and are currently monitoring the result.
This incident has been resolved.
Some Core users are unable to log in via 2FA using email; please contact Support for a manual reset to use the Authenticator app instead.
We are currently investigating this incident.
We are still working on a fix and we recommend not using @[hotmail.com](http://hotmail.com) or [live.com](http://live.com) as alternative email addresses at this time.
We’ve recently been advised that Microsoft has placed restrictions on our emails due to spam-related concerns. As a result, authentication and email delivery involving Microsoft domains such as [hotmail.com](http://hotmail.com), [live.com](http://live.com), [outlook.com](http://outlook.com), and variants are likely to be temporarily unreliable or blocked. We would not recommend using Microsoft 365 SSO either right now, as it could lead to ongoing login and verification issues for our users. In the meantime, we recommend either: * Using Google authenticator, Microsoft Authenticator or Authy app for login security, or * Switching to a different email domain other than Microsoft domains for your alternative email We understand this isn’t ideal, and we’re continuing to monitor and work on this to restore 2FA services to normal.
We’re continuing to actively work on the issue affecting email delivery and authentication for Microsoft domains (e.g. [hotmail.com](http://hotmail.com), [live.com](http://live.com), [outlook.com](http://outlook.com)). At this stage, there hasn’t been a significant change, and users may still experience issues with receiving authentication codes or using Microsoft 365 SSO. As a reminder, we recommend using an authenticator app (such as Google Authenticator, or Authy) for login security, or using a non-Microsoft email address for your alternative email where possible. We understand the ongoing impact this is having and appreciate your patience while we work towards a resolution. We’ll share further updates as soon as we have more progress.
We have discovered that customers are not able to send emails to Microsoft email domains e.g. outlook.com, live.com, hotmail.com, [msn.com](http://msn.com). We are working with Microsoft to resolve this.
Microsoft emails, such as hotmail.com, outlook.com, [live.com](http://live.com) and [msn.com](http://msn.com) are not sending via Cin7 Core. This applies to any type of email, including new user invites, purchase orders, invoices and any other document that is being sent to a Microsoft email domain. We are working with Microsoft to correct this.
We are continuing to work on a fix for this incident.
We’ve reconfigured our email application, and emails sent to Microsoft domains (e.g. Hotmail, Outlook, Live) should now be delivering successfully. As part of this temporary workaround, the FROM email address will appear as a Cin7 domain instead of your usual sender. We’re continuing to work on restoring full functionality and will share further updates as soon as we have them.