All Systems Operational
LuxSci Network Infrastructure
?
Operational
Shared WebMail
?
Operational
SecureForm
?
Operational
Premium Email Filtering
?
Operational
Email Archival
?
Operational
DNS
?
Operational
Spotlight Mailer
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
Shared Web Server Maintenance: rs125
Jul 19, 21:00-22:00 EDT
LuxSci will be updating disk space for one shared web server on Friday, July 19th, between 9pm and 9:59pm Eastern Time, USA. During this maintenance window there will be a period of 5-15 minutes of server downtime for web and database services.
Affected users are those that use the shared web server rs125. Your web server hostname looks like: rs125.luxsci.com and IP 64.39.17.194 or a private IP. If you are unsure if this maintenance window applies to you, please contact LuxSci support.
Posted on Jul 16, 09:51 EDT
Affected users are those that use the shared web server rs125. Your web server hostname looks like: rs125.luxsci.com and IP 64.39.17.194 or a private IP. If you are unsure if this maintenance window applies to you, please contact LuxSci support.
Posted on Jul 16, 09:51 EDT
Web Server Migration for rs450
Aug 23, 21:00 - Aug 24, 00:00 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Jul 10, 14:10 EDT
Jul 10, 14:10 EDT
Scheduled -
We are preparing for a server migration of the shared web server rs450.luxsci.com (CentOS 6.1) to rs2007.luxsci.com (CentOS 7.6).
Customers with web sites and/or databases hosted on rs450.luxsci.com will be affected by this migration in the following way.
*DNS A record IPs must be changed immediately after this migration takes place.
*The SSH host key will change. If you login to your server this way you will need to delete the old SSH host key from your known_hosts file.
If you are hosting your web site on rs450.luxsci.com
Your current A record IP should be: 72.3.217.239
Your new A record will be: 18.235.56.65
If you manage your own DNS you will be responsible for updating the A record of your web sites once the migration is complete. If LuxSci manages your DNS, you will not need to make any DNS changes.
The server is scheduled to be migrated on Friday of August 23, 2019 from 9 PM ET to 12 PM ET. Expected downtime may be from 30 - 60 minutes.
Please watch https://status.luxsci.com/ for updates to this scheduled maintenance.
Jul 8, 14:58 EDT
Customers with web sites and/or databases hosted on rs450.luxsci.com will be affected by this migration in the following way.
*DNS A record IPs must be changed immediately after this migration takes place.
*The SSH host key will change. If you login to your server this way you will need to delete the old SSH host key from your known_hosts file.
If you are hosting your web site on rs450.luxsci.com
Your current A record IP should be: 72.3.217.239
Your new A record will be: 18.235.56.65
If you manage your own DNS you will be responsible for updating the A record of your web sites once the migration is complete. If LuxSci manages your DNS, you will not need to make any DNS changes.
The server is scheduled to be migrated on Friday of August 23, 2019 from 9 PM ET to 12 PM ET. Expected downtime may be from 30 - 60 minutes.
Please watch https://status.luxsci.com/ for updates to this scheduled maintenance.
Jul 8, 14:58 EDT
Web Server Upgrades from PHP 7.1 to PHP 7.3
Nov 1, 00:00 - Nov 30, 23:00 EDT
During the month of November, 2019, LuxSci will be upgrading all dedicated web servers that are currently running PHP v7.1 to PHP v7.3; shared web servers running PHP v7.1 will be upgraded to PHP v7.2.
After December 1st, 2019, PHP v7.1 will no longer be supported by the PHP development community and will no longer be receiving security updates. As such, using PHP v7.1 after November, 2019 is not an option for security reasons.
If you are on a server that is currently running PHP v7.1 and you are unsure if your web site fully supports PHP v7.2 or 7.3, we recommend that you review your site and verify support during the coming months, so that when the software on your server is updated, your site will keep on chugging along. If you are unsure if your server is running PHP v7.1, please contact LuxSci support. See also the list of backwards-incompatible changes to PHP:
https://www.php.net/manual/en/migration72.incompatible.php
https://www.php.net/manual/en/migration73.incompatible.php
Dedicated server customers can request that we upgrade their servers to PHP v7.3 at any time; they do not have to wait for November. Additionally, dedicated server customers running PHP 7.1 can request that their servers be upgraded to PHP 7.2 instead of PHP 7.3, if they need more time for compatibility with 7.3. However, note that PHP 7.2 will reach its own end of life on December 1st, 2020 (see https://www.php.net/supported-versions.php) ... so everyone left using PHP 7.2 will be upgraded by LuxSci to PHP 7.3 or PHP 7.4 in November of 2020.
There is no option to continue to use PHP 7.1 after December 1st, 2019. To do so would be to leave your web site open to attackers.
Customers whose servers are running PHP v7.2 are not affected by this maintenance; however, they can also request an upgrade to PHP v7.3 if that is desirable for them. If you have questions about how this upgrade may affect you, please contact LuxSci support.
Posted on Jul 2, 13:00 EDT
After December 1st, 2019, PHP v7.1 will no longer be supported by the PHP development community and will no longer be receiving security updates. As such, using PHP v7.1 after November, 2019 is not an option for security reasons.
If you are on a server that is currently running PHP v7.1 and you are unsure if your web site fully supports PHP v7.2 or 7.3, we recommend that you review your site and verify support during the coming months, so that when the software on your server is updated, your site will keep on chugging along. If you are unsure if your server is running PHP v7.1, please contact LuxSci support. See also the list of backwards-incompatible changes to PHP:
https://www.php.net/manual/en/migration72.incompatible.php
https://www.php.net/manual/en/migration73.incompatible.php
Dedicated server customers can request that we upgrade their servers to PHP v7.3 at any time; they do not have to wait for November. Additionally, dedicated server customers running PHP 7.1 can request that their servers be upgraded to PHP 7.2 instead of PHP 7.3, if they need more time for compatibility with 7.3. However, note that PHP 7.2 will reach its own end of life on December 1st, 2020 (see https://www.php.net/supported-versions.php) ... so everyone left using PHP 7.2 will be upgraded by LuxSci to PHP 7.3 or PHP 7.4 in November of 2020.
There is no option to continue to use PHP 7.1 after December 1st, 2019. To do so would be to leave your web site open to attackers.
Customers whose servers are running PHP v7.2 are not affected by this maintenance; however, they can also request an upgrade to PHP v7.3 if that is desirable for them. If you have questions about how this upgrade may affect you, please contact LuxSci support.
Posted on Jul 2, 13:00 EDT
Upgrade all Systems to support only TLS v1.2+
Jan 1, 00:00-01:00 EDT
Update June 17th, 2019: LuxSci has pushed back the general date of the transition to TLS 1.2 only support to January 1st, 2020. This matches the timeline set my most browser vendors and others for abandoning the old versions of TLS and gives existing customers more time to upgrade their systems. However, new dedicated LuxSci customers will be placed on servers that support only TLS 1.2+ starting this week. The rolling update window is now January 1st through January 31st, 2020.
That said, LuxSci will still be transitioning to requiring TLS 1.2+ support for email transmission ("Forced TLS") during the July-August, 2019 window.
Additionally, any dedicated customer that would like to transition to TLS 1.2+ sooner, may do so at any time my asking LuxSci support.
See the original blog post: LuxSci to upgrade all Systems to support only TLS v1.2+ only
---------------------------------------------
LuxSci will be removing support for TLS v1.0 and TLS v1.1 from its services starting July 1st, 2019. This update will be a rolling change to all servers that will take place between July 1st and August 31st, 2019.
TLS v1.0 and TLS v1.1 are very old transport security protocols that have been succeeded by the much more secure TLS v1.2, which came out way back in 2008. All major web browsers released in the last 6+ years support TLS 1.2. Older web browsers may or may not support it (check your browser - https://www.projectdatasphere.org/projectdatasphere/html/tls/faq); however, less than 1% of web traffic across the world actually use the older protocols TLS 1.0 and 1.1.
TLS 1.0 and 1.1 are showing their age and security weaknesses have been cropping up for a while. Requirements for PCI compliance have mandated using TLS 1.2+ only since last summer and NIST best practices for TLS usage suggest moving away from older versions of TLS soon. LuxSci has been locking down dedicated customers that require use of only TLS 1.2+ for some time as well. In 2020, most major web browser vendors will be completely dropping support for TLS 1.0 and 1.1 as well. See: https://www.bleepingcomputer.com/news/security/tls-10-and-tls-11-being-retired-in-2020-by-all-major-browsers/
So, it really is time to give up the ghost. During the rolling maintenance period of July and August, LuxSci will be removing TLS 1.0 and 1.1 support on all dedicated and shared servers. This change affects:
* Web site hosting (i.e., what TLS versions your LuxSci-hosted web site will accept).
* Email sending via SMTP
* Email checking via POP and IMAP
* LuxSci's WebMail and administration portals
* LuxSci's Spotlight Mailer interface
* LuxSci's SecureForm for posting services
* Connections to LuxSci's APIs
* Email open and click tracking
* SMTP Forced TLS. We will only support forced outbound TLS with SMTP servers that support TLS v1.2+. We may still support opportunistic TLS with legacy SMTP servers; however, we will no longer consider such communications to be secure enough for compliance.
In general, most customers will not notice any difference. However, if you use old, legacy systems, you will want to be sure that you either (a) upgrade your systems, or (b) ensure that your systems will support TLS 1.2 for connections to LuxSci's servers.
For customers with dedicated servers that do not have specific compliance requirements (i.e., HIPAA or PCI), LuxSci can leave your server supporting TLS 1.0 and 1.1 through December 31st , 2019. If you require this extension, please contact LuxSci technical support.
Posted on Apr 8, 13:36 EDT
That said, LuxSci will still be transitioning to requiring TLS 1.2+ support for email transmission ("Forced TLS") during the July-August, 2019 window.
Additionally, any dedicated customer that would like to transition to TLS 1.2+ sooner, may do so at any time my asking LuxSci support.
See the original blog post: LuxSci to upgrade all Systems to support only TLS v1.2+ only
---------------------------------------------
LuxSci will be removing support for TLS v1.0 and TLS v1.1 from its services starting July 1st, 2019. This update will be a rolling change to all servers that will take place between July 1st and August 31st, 2019.
TLS v1.0 and TLS v1.1 are very old transport security protocols that have been succeeded by the much more secure TLS v1.2, which came out way back in 2008. All major web browsers released in the last 6+ years support TLS 1.2. Older web browsers may or may not support it (check your browser - https://www.projectdatasphere.org/projectdatasphere/html/tls/faq); however, less than 1% of web traffic across the world actually use the older protocols TLS 1.0 and 1.1.
TLS 1.0 and 1.1 are showing their age and security weaknesses have been cropping up for a while. Requirements for PCI compliance have mandated using TLS 1.2+ only since last summer and NIST best practices for TLS usage suggest moving away from older versions of TLS soon. LuxSci has been locking down dedicated customers that require use of only TLS 1.2+ for some time as well. In 2020, most major web browser vendors will be completely dropping support for TLS 1.0 and 1.1 as well. See: https://www.bleepingcomputer.com/news/security/tls-10-and-tls-11-being-retired-in-2020-by-all-major-browsers/
So, it really is time to give up the ghost. During the rolling maintenance period of July and August, LuxSci will be removing TLS 1.0 and 1.1 support on all dedicated and shared servers. This change affects:
* Web site hosting (i.e., what TLS versions your LuxSci-hosted web site will accept).
* Email sending via SMTP
* Email checking via POP and IMAP
* LuxSci's WebMail and administration portals
* LuxSci's Spotlight Mailer interface
* LuxSci's SecureForm for posting services
* Connections to LuxSci's APIs
* Email open and click tracking
* SMTP Forced TLS. We will only support forced outbound TLS with SMTP servers that support TLS v1.2+. We may still support opportunistic TLS with legacy SMTP servers; however, we will no longer consider such communications to be secure enough for compliance.
In general, most customers will not notice any difference. However, if you use old, legacy systems, you will want to be sure that you either (a) upgrade your systems, or (b) ensure that your systems will support TLS 1.2 for connections to LuxSci's servers.
For customers with dedicated servers that do not have specific compliance requirements (i.e., HIPAA or PCI), LuxSci can leave your server supporting TLS 1.0 and 1.1 through December 31st , 2019. If you require this extension, please contact LuxSci technical support.
Posted on Apr 8, 13:36 EDT