Time: July 5, 2024, 1:07 p.m.

Status: Resolved

Update: The issues with EMP has been resolved and it back in working order. If you are continuing to experience issues please contact our support team.

Time: July 3, 2024, 2:41 p.m.

Status: Investigating

Update: We have received reports that our DeliverySlip portals are experiencing issues ranging from being inaccessible to not being able to upload attachments . We have raised a high severity ticket and our engineers are currently investigating. We will continue to update this status as soon as updates come available.

Time: June 19, 2024, 6:03 p.m.

Status: Resolved

Update: We have confirmed this issue has been resolved.

Time: June 19, 2024, 2:01 p.m.

Status: Investigating

Update: We are currently investigating an issue with the UI in which the DKIM section (Account Management->DKIM) is missing. We are actively investigating and triaging this issue now.

Time: June 18, 2024, 7:03 p.m.

Status: Resolved

Update: We have resolved the issue and have confirmed the filter metrics for the tests are falling within our normal metrics. We will continue to monitor the traffic but the underlying issue has been resolved.

Time: June 18, 2024, 4:04 p.m.

Status: Identified

Update: We have identified an issue with an optional/additional filter that is causing a large number of false positives. We are working on resolving this issue but in the interim, this filter can be disabled under the Additional Filtering section within Zix Central.

Time: June 27, 2024, 2 p.m.

Status: Resolved

Update: Final Update from Microsoft: Our extended service monitoring has confirmed that our implemented measures to protect the service have improved IP address reputation and remediated the impact.

Time: June 24, 2024, 1:30 p.m.

Status: Identified

Update: Update from Microsoft: We've identified a pattern of malicious email sending behavior that was contributing to the reduced IP address reputation and implemented measures to protect the service. Our initial review of telemetry after these changes indicates a positive response and a reduction in messages being blocked as expected. We're continuing to monitor our telemetry to ensure this stays on a positive trend and confirm the issue is resolved.

Time: June 13, 2024, 2:17 p.m.

Status: Investigating

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

Time: July 19, 2024, 12:03 p.m.

Status: Resolved

Update: This issue was resolved on 11 Jun. Closing status.

Time: June 6, 2024, 12:57 p.m.

Status: Investigating

Update: 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)