Update 9:30 PM Pacific time: the problem described below is resolved, as Amazon is no longer sending data through the problematic route to our servers.
Original post: Our monitoring systems are showing that this evening, there have been short periods of network failures between our data center and some Amazon Web Services (AWS) data centers on the US East Coast. This appears to be due to a problem Amazon is having connecting to an intermediate “Internet backbone” connection in Virginia run by a third party.
This isn’t affecting other connections, so most of our customers are unaffected, and we see no overall drop in traffic.
Read the rest of this entry »
We’ve updated the SSL/TLS security settings on our servers to match current “best practices” for security, disabling the long-obsolete, insecure “SSLv3” in all cases.
Our customers shouldn’t notice any changes. We made this change on our own websites a long time ago with no reports of problems, and nearly all of the largest sites on the Internet have done the same. We’re just mentioning this so that people know to contact us in the unlikely event they do have any trouble.
That said, if you do have any trouble, it’s probably because you’re using a long-outdated, insecure web browser that you should update. You can check your browser by visiting www.howsmyssl.com. If you can’t update it, using a different browser on your computer will probably help.
Update 11:22 PM Pacific time Dec. 1: The maintenance described below has been completed and all services are running normally.
Between 10:00 PM and 11:59 PM Pacific time on Saturday, December 1, 2018, the MySQL database software on some hosting servers will be updated. This will cause an approximately two minute interruption of service on each MySQL-using customer Web site (including WordPress sites) at some point during this period.
Specifically, this will affect servers ending in digits 0, 1, 2 and 3, such as “web01” and “web10”. (All other servers were previously updated on November 17 or November 24.)
Read the rest of this entry »
Update 10:39 PM Pacific time Nov. 24: The maintenance described below has been completed and all services are running normally.
Between 10:00 PM and 11:59 PM Pacific time on Saturday, November 24, 2018, the MySQL database software on some hosting servers will be updated. This will cause an approximately two minute interruption of service on each MySQL-using customer Web site (including WordPress sites) at some point during this period.
Specifically, this will affect servers ending in digits 4, 5 and 6, such as “web04” and “web14”. Servers ending in digits 0-3 are not affected now and will be updated later; servers ending with digits 7-9 were previously updated.
Read the rest of this entry »
Update 10:46 PM Pacific time Nov. 17: The maintenance described below has been completed and all services are running normally.
Between 10:00 PM and 11:59 PM Pacific time on Saturday, November 17, 2018, the MySQL database software on some hosting servers will be updated. This will cause an approximately two minute interruption of service on each MySQL-using customer Web site (including WordPress sites) at some point during this period.
Specifically, this will affect servers ending in digits 7, 8 and 9, such as “web07” and “web08”. Servers ending in digits 0-6 are not affected now and will be updated later this month.
Read the rest of this entry »
Between 10:00 PM and 11:59 PM Pacific time on Saturday, October 27, 2018, each of our hosting servers will be restarted. This will cause a brief interruption of service (less than 5 minutes) for each site at some point during this period.
Read the rest of this entry »
Update 3:50 AM Pacific time October 23: According to AVG, the problem described below has been resolved, and the AVG software is no longer incorrectly blocking our webmail site and other sites.
We’ve received reports from a couple of customers today (Monday, October 22, 2018) that their AVG (Avast) Antivirus software is wrongly flagging our mail.tigertech.net webmail servers as a potential “phishing” site, on the basis that it’s asking for your email username and password.
Read the rest of this entry »
Between 10:58 and 11:09 AM Pacific time today (October 19, 2018), the “web03” server experienced an outage that led to an interruption in service for some customer websites and email.
The problem has now been resolved, and other servers were not affected. We apologize for the inconvenience this caused our customers.
We’re investigating the root cause (a Linux “kernel panic”) to ensure it does not recur.
We’ve improved how our “My Account” control panel rejection of email addresses works.
Previously, if you added an e-mail address to the reject list, the “Return-Path” (aka bounce address) header of each incoming message was checked for matches. This was sufficient for most messages, but some messages use a different address in the “Return-Path” header and the “From” address header, which could be confusing.
As of today, both headers (the “Return-Path” header and the “From” address header) are checked when matching reject list entries, making it more reliable.
As always, don’t hesitate to contact us if you have any trouble or questions.
The authors of the Mailman mailing list software we provide for customers have recently released version 2.1.29 to fix several bugs.
We’ve upgraded the Mailman software on our servers as a result.
Users of Mailman lists shouldn’t notice any changes, but as always, don’t hesitate to contact us if you have any questions or see any problems.
