Perl software updated to fix security bug

We’ve updated our servers with a Perl security bug fix. This won’t affect most customers, but read on if you know you use Perl scripts on your site.

Read the rest of this entry »

DDoS attack on fry server (resolved)

The “fry” server was the victim of a high-bandwidth Distributed Denial of Service (DDoS) attack beginning at 3:11 AM Pacific time this morning. On that server, Web pages were intermittently slow to load or generated timeout errors. (Other servers were not affected.)

We’ve blocked the large number of IP addresses from the “botnet” attacking the server, and the issue was completely resolved by 4:19 AM Pacific time. Please accept our apologies if you noticed any problems with your site loading slowly during this period.

Brief maintenance on Mailman Web interface and archives (completed)

We’ll be performing brief maintenance on the Web server that runs the Mailman list interface and archives tonight (June 9, 2011) between 10:00 PM and 11:00 PM Pacific time.

Read the rest of this entry »

FrontPage support ending September 1, 2011

Microsoft FrontPage was once a popular Web design program. Microsoft stopped selling FrontPage in 2006, though, and we’ve been warning about the end of FrontPage support for a while now (on both our support pages and our blog).

That time has now arrived. Our FrontPage support for new sites will end on September 1, 2011, and support for existing sites will end a year after that.

Read the rest of this entry »

World IPv6 Day

World IPv6 Day is now in progress (it started at midnight UTC, which was 5:00 PM Pacific time). For the next 24 hours, many sites on the Internet, including our own www.tigertech.net, are fully IPv6-enabled.

If you have trouble connecting to www.tigertech.net, check other sites like Google, Yahoo and Bing. If you have problems with any of those, you should test your IPv6 connection and notify your ISP or network administrator about any problems.

For more information about IPv6 (and how sites hosted with us can participate), see our previous post: Now We Are Six: IPv6 support.

Comcast routing problems (resolved)

Some Comcast users in California had trouble connecting to some of our servers beginning at around 7 AM Pacific May 21, 2011. Non-Comcast users were not affected at all, and even people who were affected were able to reach some of our servers with no trouble.

This was caused by a technical problem at Comcast, and not related to us specifically. It appears Comcast was incorrectly filtering some combinations of IP addresses and ports in one of their California network routers, preventing their customers from reaching some sites.

The issue was apparently resolved by Comcast at 10:07 AM Pacific time, and we are not aware of any ongoing problems. As always, don’t hesitate to contact us if you have any trouble.

Sites on “farnsworth” server moved to “zapp”

All Web sites on the “farnsworth” Web server have been moved to a new server named “zapp”.

This change was made for reliability; our monitoring systems detected potential hardware problems with the “farnsworth” server earlier today, and the sites were moved so it can be replaced before it causes any problems.

This doesn’t cause any downtime, and customers shouldn’t notice any change — but as always, don’t hesitate to contact us if you have any questions.

Brief scheduled maintenance on pazuzu server (completed)

At approximately 11:00 PM Pacific time tonight, May 14, the “pazuzu” Web server will be restarted.

As a result, for customers on the “pazuzu” server (only), Web site service and the ability to read incoming e-mail will be unavailable for approximately five minutes. Customers on other servers will not be affected.

Read the rest of this entry »

High packet loss for some connections (resolved)

A router failure at an upstream Internet “peer” that we connect to caused high packet loss for some Internet connections between 5:18 PM and 5:28 PM Pacific time.

The packet loss grew worse through that period until it exceeded 25%, which is enough to cause pages to fail to load within a browser’s timeout period if your connection was one of the affected ones. (Connections that go through different routers were not affected.)

Network engineers have routed all connections around the failed hardware until it’s replaced, so the problem is resolved. If your part of the Internet was one of the affected ones, please accept our apologies for the problem.

Service outage May 6, 2011 (resolved)

May 6, 4:43 AM Pacific time: An outage at our primary data center caused a complete service interruption for all customers.

Update 5:08 AM: All services have been restored and are working normally.

Read the rest of this entry »