All Systems Operational
LuxSci Network Infrastructure
?
Operational
Shared WebMail
?
Operational
SecureForm
?
Operational
Premium Email Filtering
?
Operational
Email Archival
?
Operational
DNS
?
Operational
Spotlight Mailer
Operational
Hosted Email
Operational
Hosted Web Services
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Scheduled Maintenance
Legacy non-TLS Login Support Being Removed
Feb 1, 00:00 - Feb 29, 00:00 EST
During February, 2020, LuxSci will be removing all legacy support for logging into accounts without the use of TLS encryption.
Certain LONG-time legacy customers who do not have specific security or compliance requirements have a grandfathered ability to enable their users to login to specific services without TLS encryption -- i.e., in plain text. Often, this capacity was used to support legacy hardware devices (e.g., printers and scanners) that did not support TLS.
This grandfathered insecure login permission is being globally removed during this maintenance window. No one should be considering using any system that sends credentials of any kind "in the clear" across the public internet, no matter what the legacy reason. After all these years, the majority of equipment and software finally does support TLS so the barrier to better security is minimal.
Any legacy LuxSci customer that is currently using insecure logins for POP, IMAP, SMTP, or FTP should update their systems to use the secure alternatives before February 1st, 2020. Once the servers are updated, such connection attempts will begin to fail.
LuxSci will be auditing its customers and sending direct notices to those that have recently made insecure connections to alert them to this forced change.
Posted on Nov 26, 14:58 EST
Certain LONG-time legacy customers who do not have specific security or compliance requirements have a grandfathered ability to enable their users to login to specific services without TLS encryption -- i.e., in plain text. Often, this capacity was used to support legacy hardware devices (e.g., printers and scanners) that did not support TLS.
This grandfathered insecure login permission is being globally removed during this maintenance window. No one should be considering using any system that sends credentials of any kind "in the clear" across the public internet, no matter what the legacy reason. After all these years, the majority of equipment and software finally does support TLS so the barrier to better security is minimal.
Any legacy LuxSci customer that is currently using insecure logins for POP, IMAP, SMTP, or FTP should update their systems to use the secure alternatives before February 1st, 2020. Once the servers are updated, such connection attempts will begin to fail.
LuxSci will be auditing its customers and sending direct notices to those that have recently made insecure connections to alert them to this forced change.
Posted on Nov 26, 14:58 EST
MariaDB upgrades from v5.5 to v10.2
Mar 1, 12:00 - Apr 1, 13:00 EST
During the month of March, 2020, LuxSci will be upgrading all servers still running MariaDB v5.5 to v10.2. This upgrade is happening because MariaDB v5.5 is reaching its end of life and will stop receiving security updates after April 11th, 2020 (See: https://mariadb.org/about/)
This maintenance will be performed in a rolling fashion and, in general, only a few seconds of database downtime is expected as each server is updated. Your server could be updated at any time during the month.
If you would like to have your server upgraded before March, or if you would like to upgrade to MariaDB v10.4 instead, please contact support. We are upgrading to v10.2 in general as it is well used, very stable, and supported for two more years. Additionally, upgrades to v10.4 may require a longer downtime due to changes in InnoDB table format support.
While there is little downtime and impact expected from the database migrations, it is possible that your web applications may be using a feature of MariaDB v5.5 that is no longer available in v10.2, breaking your application. It does not seem like there are many backwards incompatible changes; however, we recommend that administrators review the following pages and check with their developers to make sure that there are none that apply to them:
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-55-to-mariadb-100/
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-100-to-mariadb-101/
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/
If you have any questions, please contact LuxSci support.
Posted on Dec 9, 12:04 EST
This maintenance will be performed in a rolling fashion and, in general, only a few seconds of database downtime is expected as each server is updated. Your server could be updated at any time during the month.
If you would like to have your server upgraded before March, or if you would like to upgrade to MariaDB v10.4 instead, please contact support. We are upgrading to v10.2 in general as it is well used, very stable, and supported for two more years. Additionally, upgrades to v10.4 may require a longer downtime due to changes in InnoDB table format support.
While there is little downtime and impact expected from the database migrations, it is possible that your web applications may be using a feature of MariaDB v5.5 that is no longer available in v10.2, breaking your application. It does not seem like there are many backwards incompatible changes; however, we recommend that administrators review the following pages and check with their developers to make sure that there are none that apply to them:
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-55-to-mariadb-100/
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-100-to-mariadb-101/
- https://mariadb.com/kb/en/library/upgrading-from-mariadb-101-to-mariadb-102/
If you have any questions, please contact LuxSci support.
Posted on Dec 9, 12:04 EST