Cin7 Outage History

We are continuing to work on a fix for this incident.

We are continuing to work on a fix for this incident.

We are continuing to work on a fix for this incident.

We are continuing to work on a fix for this incident.

We've identified the root cause. We're building a fix to be rolled out soon.

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 are continuing to work on a fix for enabling customers to use the send from functionality.

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’ve completed work on a fix for this issue, and it is scheduled to be included in this weekend’s release.

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

We are continuing to work on a fix for this incident.