Temporary web14 load problem (resolved)

7:11 AM Pacific time: Our technicians are investigating a possible outage on the “web14” server.

Final update: We found the source of the problem — there were a couple of short load spikes over a period of 10 minutes. We have taken steps so that it doesn’t happen again.

We know that uptime is critical for our customers, and we apologize for the inconvenience caused by this event.

Routing problem for some East Coast users (resolved)

We have gotten quite a few reports from users on the East Coast that they cannot connect to their Web sites on our servers, to our Web site, or to our e-mail servers.

Analysis shows that the problem is with a network called nlayer.net which is between them and our servers. When you make a connection to a remote server, the connection travels from your ISP, through several different intermediary networks, and finally to the destination network and server. Each of these networks needs to properly “route” the connection to the next closest node to the destination. The current problem seems to be that the data packets are getting lost within the nlayer.net network.

You can verify this by running the command “tracert www.tigertech.net” on Windows, or “traceroute www.tigertech.net” on Mac (Terminal). You’ll see that your packets can get through your ISP, but after they get handed off to nlayer.net the packets get lost. (A line that ends with *** is a failure.)

While you may have a problem in the network route between your computer and our servers, most other people on the Internet use different routes and can continue getting to your site just fine. You can also verify this with third-party sites, such as checksite.us.

This sort of problem is not uncommon, but is usually resolved within a few minutes. It’s up to nlayer.net to fix their routing; we presume they are working on it.

Update 9:56 AM (Pacific time): It looks like nlayer.net has fixed their problem. We see that customers who had been having problems can now reach their Web sites (and our site) successfully. Please note that no incoming e-mail was lost during this. Any incoming e-mail would have queued up for later delivery, and will get redelivered to our mail servers (soon, if not already).

Even though the cause of this problem was out of our hands, we certainly regret the inconvenience that it caused those who were affected.

Brief scheduled maintenance June 7, 2014 (completed)

Between 10:00 PM and 11:59 PM Pacific time on Saturday, June 7, each of our hosting servers will be restarted. This will cause a brief interruption of service (less than 10 minutes) for each site at some point during this 2 hour period.

Read the rest of this entry »

Networking issues June 4 2014 (resolved)

2:49 AM Pacific time: We’re receiving scattered reports of intermittent problems when connecting to our servers from Europe, although all services on our end are working normally.

3:30 AM Pacific time: This issue appears to be a problem within the network of one of our upstream providers. We have temporarily disabled routing network traffic through that provider, and the trouble is resolved.

PHP 5.4.29 and 5.5.13

The PHP developers recently released versions 5.4.29 and 5.5.13 that fix several bugs. We’ve updated PHP 5.4 and 5.5 on our servers as a result.

Read the rest of this entry »

Avoiding DMARC mail bounces with Contact Form 7

We recently explained how to avoid DMARC mail delivery problems with the “Gravity Forms” WordPress plugin.

We’ve added a support article explaining how to avoid DMARC mail delivery problems with the similar “Contact Form 7” plugin, too.

If you use either of these plugins and you’re seeing mail rejected with errors about “DMARC”, the links above will help you fix it.