Status Page
Investigating - Service Incident posted by Microsoft:

User impact -
Users' email messages may be rejected as potential spam due to poor IP address reputation and not delivered.

More info -
Users impacted by this event receive a Non-Delivery Report (NDR) with an error indicating that the email originated from an IP address that is on a Remote Block List/Realtime Blackhole (RBL) and was blocked by a third-party anti-spam service. Users may be successful in sending affected messages upon retry after waiting a period of 5 to 10 minutes from the last attempt.

Scope of impact -
The problem may impact some users that send outbound email messages if the recipient leverages a specific third-party anti-spam service mentioned within the NDR.

Root cause -
A third-party anti-spam service is blocking a portion of Microsoft’s email IP address ranges to protect organizations that use their services.

Current status -
We've received reports from some users who are receiving NDRs indicating that their email messages are being rejected by a third-party anti-spam service as potential spam due to poor IP address reputation. These email messages are not delivered as expected. We're working with the third-party to unblock the affected IP addresses to expedite mitigation of this issue.

In parallel, we're reviewing the reasons that led to the spam detection so that we may reduce the likelihood of the problem repeating. To accomplish this, we're correlating the spam detections to email sending behavior associated with the affected IP address pools. From our analysis of this data, we’ll begin looking into how to improve the reputation of the affected IP addresses and allow legitimate email to be sent as expected. However, our actions to prevent reoccurrences are expected to take an extended period to finalize and implement.

Jun 13, 2024 - 09:17 CDT
Investigating - Twitter (X) has a known issue from a recent change they made that has broken the OAuth workflow. A high severity issues has been raised for tracking and we have submitted a request with Twitter (X) to have this resolved as the issue lies with them. At this time only new installs not pre-existing connections are affected. We will update this alert when we hear anything back from Twitter (X)
Jun 06, 2024 - 07:57 CDT
Investigating -

*Please Note before proceeding* - If you are using Email Threat Protection Smarthosting for outbound service, DKIM/DMARC will need to be configured there instead of O365 – see the following link for ETP Smarthosting - Zix | AppRiver Status - DKIM signing for Email Threat Protection


Yahoo/Aol and a few other providers recently made some security updates and are beginning to require DKIM/DMARC in addition to SPF. These records would need to be configured with your DNS provider, in order to prevent the rejections, you have received.

Please ensure you have SPF (TXT) record configured first before proceeding with O365 DKIM/DMARC.


How to enable/add DKIM:

Generate DKIM keys within the M365 Admin Center -

1. Sign-in through the M365 admin center as a global administrator

2. In the left-hand menu, click on Security under Admin Centers. This will take you to the Microsoft Defender Portal.

3. From there, Under Email & Collaboration - click on Policies and Rules --> Threat policies --> Email Authentication Settings --> DKIM --> Select your Domain and Enable.

4. You can select Generate DKIM Key and it will populate the required CNAME record information


It will show in the form of an error message when attempting to enable. This error message also contains the needed CNAME records.

***Once you have configured these two CNAME records on your DNS side, please go back to the same location mentioned above in the Microsoft Defender Portal.***

1. M365 admin center --> Security Admin Center (Microsoft Defender Portal) --> Policies and Rules --> Threat policies --> Email Authentication Settings --> DKIM --> Click on Domain and Enable DKIM.


***DKIM should now be successfully be enabled.***


How to add DMARC:

1. After DKIM is enabled and configured, please contact your DNS provider for assistance with creating a DMARC record.

There is also third-party tools and sites that can be used as a DMARC generator to generate a DMARC record for you. Then you can add the record through your DNS provider.




For more information regarding both records, please see the articles below.

Set up DKIM to sign mail from your Microsoft 365 domain:


Set up DMARC to validate the From address domain for senders in Microsoft 365:

Mar 11, 2024 - 10:47 CDT
Identified - To better assist our customers and partners more promptly, we have made some changes to the IVR menu. When calling in, please listen carefully to the dial options.

The updated IVR menu will be active starting on 4/10/2024.

Below is a copy of our updated IVR menu options for your reference:

1. For Threat Protection or Customer Portal Support – Press 1

2. For Encryption, Archive, Social Media capture or Backup Support – Press 2

3. For help with Microsoft Licensing and Support – Press 3

- For Microsoft Domain Verifications, License upgrades, Scheduled reductions, CSP transition & Pending installations - Press 1

- For Microsoft 365 or Hosted Exchange Support – Press 2

4. For Carbonite Support - Press 4

5. For Webroot Support - Press 5

Apr 03, 2024 - 08:41 CDT
Identified -

A new Microsoft Security Update is being rolled out to Hosted Exchange to secure a new zero-day vulnerability. Microsoft states the update could impact the following short term:

1. Search errors in Outlook Desktop: Microsoft has linked an article regarding this error and provided registry change fixes to resolve the issue - Search error in Outlook cached mode after installing March 2024 SU - Microsoft Support

2. Users may be unable to preview certain Office attachments via OWA – Microsoft is working on releasing a patch

3. Read vs Unread message indications may be inconsistent via Outlook Desktop – Microsoft is working on releasing a patch

Mar 20, 2024 - 07:13 CDT
Update - If you still experience password prompts on your Outlook clients after ruling out your third-party AV causing the issue, you should check the following registry key / value on your computer unless you have an Active Directory Group Policy Object (GPO) policy overriding your local computer. Please check with your IT admin if you have a GPO configured (Please Note, Zix/Appriver support cannot directly support GPO configurations).


From user computer:

- Registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa

- Registry value: LmCompatibilityLevel

- It must be set at least to a value of 3 which is Send NTLMv2 response only. If the key is not there the computer will default to a value of 3 unless you have an Active Directory GPO overriding the local computer.


If your admin is using Active Directory GPOs instead to set your security policy, please verify the following Policy location to ensure it is set to one of the supported values below. (Please Note, Zix/Appriver support cannot directly support GPO configurations).

Policy location: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options

Policy Name: Network security: LAN Manager authentication level

Unsupported values
Send LM & NTLM responses
Send LM & NTLM - use NTLMv2 session security if negotiated
Send NTLM responses only

Supported values
Send NTLMv2 responses only
Send NTLMv2 responses only. Refuse LM
Send NTLMv2 responses only. Refuse LM & NTLM
Not Defined

Mar 09, 2024 - 19:40 CST
Monitoring - We are getting reports of some users unable to log into Outlook desktop but can successfully log into Outlook Web Access.

There was a recent Microsoft Exchange security update that could be causing this impact if you are using an outdated non-supported version of Outlook or using an Anti-Virus service on your computer. Clients using AV that does endpoint protection of the Outlook connections could cause repeated login prompts as that would appear as a man-in-the-middle attack.

Please ensure you are currently running at least Outlook 2013 (that is fully updated) or newer.
*Please note however, Outlook 2013 Microsoft end of life was on April 11th, 2023, so it is further recommended to run at least Outlook 2016 or newer*

If you have a third-party Anti-Virus service running on your computer, please temporarily disable the setting doing endpoint protection on Outlook connections through your AV, restart Outlook, then see if you can successfully log into Outlook.
If successful, this indicates your AV could be running encrypted connection checks on Outlook connections or could be running an AV that needs to be updated.

We recommend to please contact your AV service provider / support team to report this issue for assistance.

Mar 09, 2024 - 13:59 CST
Archive Services ? Partial Outage
Information Archive / ZCP Partial Outage
Erado Archiving ? Partial Outage
Legacy Archive / ZixArchive Partial Outage
CloudAlly Backup Operational
Encryption Services Operational
EMP/DeliverySlip Operational
Erado SecureMail (ESM) Operational
Hosted ZixGateway Operational
Hosted SMB Operational
Secure Cloud Email Encryption (AEE/ZEE) Operational
ZixPortal Operational
Customer Portal Interface Operational
Customer Portal Operational
Partner Portal Operational
Billing Area Operational
ZixCentral ? Operational
Secure Hosted Exchange Operational
Exchange 2013/2016+ (EXG7) Operational
Office 365 Degraded Performance
DNS Hosting ? Operational
Support Infrastructure Operational
Phone System Operational
Live Chat Operational
Support Ticketing System Operational
Threat Protection Operational
Email Threat Protection ? Operational
Zix Protect/Spam Stops Here ? Operational
Email Continuity Operational
Secure Cloud Email Continuity Operational
Legacy Continuty Operational
Datacenter Operational
90 days ago
100.0 % uptime
Degraded Performance
Partial Outage
Major Outage
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Jun 14, 2024

No incidents reported today.

Jun 13, 2024

Unresolved incident: Microsoft Service Incident: Email messages may be rejected due to poor IP address reputation.

Jun 12, 2024

No incidents reported.

Jun 11, 2024

No incidents reported.

Jun 10, 2024

No incidents reported.

Jun 9, 2024

No incidents reported.

Jun 8, 2024

No incidents reported.

Jun 7, 2024

No incidents reported.

Jun 6, 2024

Unresolved incident: Twitter Compliance and Capture - New installs only.

Jun 5, 2024

No incidents reported.

Jun 4, 2024

No incidents reported.

Jun 3, 2024

No incidents reported.

Jun 2, 2024

No incidents reported.

Jun 1, 2024

No incidents reported.

May 31, 2024

No incidents reported.