Spectrum (charter.net) has started to receive email from the SMB hosted systems. We will continue to monitor the situation and update this notice accordingly.
We do apologize for any inconveniences this has caused.
Thank you
Zix|Appriver Support
Apr 9, 10:27 CDT
Identified - Dear Zix|Appriver Customer,
Our hosted SMB system is currently having issues relaying mail to charter.net servers.
Our engineers are actively working with Spectrum (charter.net) to resolve the issue as quickly as possible.
We do apologize for the inconvenience this is causing.
Update - We have updated our plan of roll out to be March 8th at 9 AM CST.
Mar 7, 13:01 CST
Monitoring -
As a security update to help combat spoofing and unauthorized email, we are making improvements to our Relay Server (relay.appriver.com) on March 1st, 2022. This server was mainly used for alerting or scan to email systems.
The security update will be an SPF record validation on incoming connections to our relay server. The SPF record check will verify the sending IP address is listed in the domain's SPF record. We understand this improvement will require many customers to add their sending IP address to their SPF record. The Set Up a SPF Record for AppRiver Hosted Services article provides more information on setting up an SPF record for Zix|Appriver services. An example of an valid SPF record is below.
Update - We have reverted the SPF security update for now. We are planning on implementing this in a future security update to our relay server. We recommend anyone using our relay server to update their SPF to include the IP of the application/software to avoid future issues.
Feb 3, 11:24 CST
Update - We have scheduled this change to go into effect Feb 1st, 2022 (Tuesday). Please ensure your SPF records are correctly listing your IP's you will connect from to ensure no issues with use of our Relay Server.
Jan 26, 11:50 CST
Update - We are updating our security settings for our Relay Server which is normally used for scan-to-email systems. We are implementing an SPF check on incoming connections to ensure the sender of the email is validity listed in their SPF records. Any customer using relay will need to follow the guide below and update their SPF to include their sending IP in their SPF. This will be in the format of "v=sp1 ip4:1.2.3.4 -all" as an example. The below article will go over this as well. If you have any questions please reach out to support via ticket to support@appriver.com
Identified - We are updating our security settings for our Relay Server which is normally used for scan-to-email systems. We are implementing an SPF check on incoming connections to ensure the sender of the email is validity listed in their SPF records. Any customer using relay will need to follow the guide below and update their SPF to include their sending IP in their SPF. This will be in the format of "v=spf1 include:edgepilot.com ip4:1.2.3.4 -all" as an example. The below article will go over this as well. If you have any questions please reach out to support via ticket to support@appriver.com
Monitoring - We will continue to monitor as our teams work through the intermittent issues with the Customer Portal login page failing to load properly. We apologize for the inconvenience and appreciate your patience as we work to fully resolve the issue.
Mar 14, 10:22 CDT
Investigating - We are currently investigating an intermittent issue with the Customer Portal login page failing to load properly. We do apologize for the inconvenience and appreciate your patience as we work to resolve the issue.
Mar 14, 08:59 CDT
Identified - Secure Cloud is experiencing intermittent issues ordering and migrating Microsoft products. This is due to several factors including:
1. Microsoft Partner Center API outages and instability due to high order volumes 2. Microsoft's rollout for the ordering changes (discontinuation of Legacy CSP ordering)
Due to the issues, some of the behavior you may experience includes:
1. Inability to access the O365 licensing page 2. Longer than expected completion time for Microsoft orders 3. Issues with management of O365 licensed users
This is our highest priority. We are actively working with Microsoft to mitigate and eliminate these issues as soon as possible.
Mar 10, 16:03 CST
Monitoring - As of 10:45 PM Central Time on Wednesday, December 15th, 2021, we have reviewed all of our production systems, corporate internal IT systems, and all relevant third-party software for the presence of Log4j vulnerabilities as described by the vendor, and we have completed all vendor-recommended remediations with respect to those systems and third-party software.
We have also completed a review of our supported on-site (on-prem) products and found no Log4j vulnerabilities as described by the vendor in any of those products.
We also continue to monitor our systems (which does not include customer-premise products) for the purpose of detecting certain exploits known to leverage the Log4j vulnerability.
Dec 16, 21:15 CST
Incident information Title: Admins are unable to access the Exchange admin center ID: EX382252
Status Service Restored Impacted Services
Exchange Online
Details Title: Admins are unable to access the Exchange admin center
User Impact: Admins were unable to access the Exchange admin center (EAC).
Final status: While reproducing the issue internally, we've confirmed that the spike in CPU utilization has leveled off and the service has recovered. Additional monitoring and customer reports have validated that access to the EAC has been restored in all impacted regions.
Scope of impact: Impact was specific to a subset of users who were served through the affected infrastructure. Telemetry indicated that the majority of impact occurred to admins located in the North America and Europe regions.
Start time: Thursday, May 19, 2022, at 1:17 PM UTC End time: Thursday, May 19, 2022, at 2:35 PM UTC
Preliminary root cause: A spike in CPU utilization on components which facilitate EAC access resulted in impact. Next steps: - We’re reviewing our code for improved performance and potential automated recovery options to reduce or avoid similar impact in the future.
Thank you, The Microsoft team
May 19, 11:04 CDT
Investigating -
Exchange Online service alert
Incident information Title: Admins are unable to access the Exchange admin center ID: EX382252
Status Investigating
Impacted Services Exchange Online
Details Title: Admins are unable to access the Exchange admin center User Impact: Admins are unable to access the Exchange admin center (EAC). Current status: We're reviewing support case details and diagnostic data to isolate the source of the issue. Scope of impact: Impact is specific to a subset of admins who are served through the affected infrastructure. Next update by: Thursday, May 19, 2022, at 3:00 PM UTC
Resolved -
All services have been restored to operational status. We apologize for any inconvenience this may have caused.
May 17, 17:23 CDT
Investigating -
We are currently experiences issues with our Zurich Data Center and are actively investigating this issue with our vendor. This will effect access for some EMEA customers and their access to our Hosted Exchange/ETP filtering and our EMP products lines. We apologize for any inconvenience this may be causing. We will follow with another update as soon as more information is available.
May 17, 17:01 CDT