The most current information available about outages, maintenance, or other known problems is always posted here first. Important articles of a timely nature are also posted here for as long as they are relevant.

You may sign up to receive these notices via e-mail; this assures that you will see each notice as soon as it is posted. The notices are also available as an RSS feed.

Mail Server Upgrade Announcement - we are upgrading our IMAP and POP e-mail systems

MySQL 4.1.x to 5.0.x Upgrade Announcement - we are upgrading all shared database servers currently running MySQL 4.1.x

Security Notices - Security vulnerabilities in commonly used packages are reported here.

FreeBSD 6.2 Upgrade Announcement - we are currently upgrading remaining dedicated servers

E-Mail Form Vulnerabilities - we are seeing a large number of exploits against e-mail gateway forms.
PHP Configuration Change - we made a change to our PHP configuration in July 2004

[Jul 3, 2009, 6:36 PM] mae, qatlh Planned Maintenance

Tonight we will be taking mae (www349) down for a drive upgrade, and qatlh (www342) down to swap out a failing Shadow Drive. Downtime for each server should not exceed 10 minutes. And additional notice will be posted once the maintenance is complete.

[Jul 3, 2009, 5:40 PM] saakal Downtime

saakal (www264) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 3, 2009, 5:09 PM] dieci Downtime

dieci (www231) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 3, 2009, 2:14 AM] padaya Downtime

padaya (www385) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 3, 2009, 1:38 AM] thuule Downtime

thuule (www49) encountered an error and reset. Downtime was about 10 minutes.

[Jul 2, 2009, 7:49 PM] delsi Downtime

delsi (www206) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 2, 2009, 10:27 AM] sali Downtime

sali (www454) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 10 minutes.

[Jul 2, 2009, 9:42 AM] sali Downtime

sali (www454) became unresponsive under high load and needed to be rebooted. Total downtime was 10 minutes.

[Jul 1, 2009, 12:40 PM] aerre Downtime

aerre (www185) crashed due to an error and was reset. Downtime was about 5 minutes.

[Jul 1, 2009, 11:00 AM] zhun Downtime

zhun (www107) crashed due to high load and was reset. Downtime was about 5 minutes.

[Jul 1, 2009, 6:23 AM] akutan Downtime

akutan (www361) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 1, 2009, 5:17 AM] gamma Downtime

The server gamma (www2) encountered an error, became unresponsive, and was reset. Downtime was less than ten minutes.

[Jun 30, 2009, 8:00 PM] poict Maintenance Completed

The shadow drive swap for poict is complete. Downtime was about 5 minutes.

[Jun 30, 2009, 7:29 PM] poict Emergency Maintenance

poict (www195) will be taken down shortly to swap out a failed shadow drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Jun 30, 2009, 5:26 PM] patru Downtime

The server patru (www232) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Jun 30, 2009, 3:06 PM] sirung Downtime

sirung (www409) Became unresponsive and required a reset. Downtime was less than 5 minutes.

[Jun 30, 2009, 8:46 AM] flaid Downtime

flaid (www91) encountered an error and was reset. Downtime was under 15 minutes.

[Jun 30, 2009, 7:36 AM] kesa Downtime

kesa (www479) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 30, 2009, 12:49 AM] amutka Downtime

amutka (www369) encountered an error and reset. Downtime was about 10 minutes.

[Jun 29, 2009, 3:28 PM] mildh Downtime

The server mildh (www87) encountered an error and was reset. Downtime was less than 10 minutes.

[Jun 29, 2009, 2:23 PM] peulik Downtime

peulik (www360) became unresponsive while in service and was reset. Downtime was less than 5 minutes.

[Jun 29, 2009, 5:17 AM] tama Downtime

tama (www70) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 29, 2009, 12:23 AM] zirx Downtime

zirx (www106) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 29, 2009, 12:21 AM] or Downtime

or (www34) encountered an error and was reset. Downtime was less than 5 minutes.

[Jun 28, 2009, 7:43 AM] aedde Downtime

aedde (www84) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 28, 2009, 7:32 AM] or Downtime

or (www34) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 28, 2009, 5:28 AM] ghiq Downtime

ghiq (www324) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 27, 2009, 4:09 PM] okmok Downtime

okmok (www362) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 27, 2009, 6:59 AM] gamma Downtime

gamma (www2) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 27, 2009, 5:40 AM] qaske Downtime

qaske (www250) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 27, 2009, 12:16 AM] yuki Downtime

yuki (www493) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 26, 2009, 4:10 PM] mirozo Downtime

mirozo (www257) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 26, 2009, 2:41 PM] ur Downtime

ur (www30) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 26, 2009, 11:35 AM] Network Problems Resolved

The Level(3) and Verizon outage was traced to an OC-192 bundle in Virginia, where the problem has been resolved. We will be moving our Level(3) circuit to an alternate POP within the next week, in order to avoid any possibility of this simultaneous outage recurring. We apologize for the disruptions during this 20-minute incident.

[Jun 26, 2009, 10:51 AM] Network Problems Resolved

At 10:38am Eastern, our Verizon and Level(3) circuits returned to service. We do not yet have any explanation of the problem. Each circuit rides a different path to a different POP and terminates on a different router on either end, so the problem is quite surprising. We will post further information as it becomes available.

[Jun 26, 2009, 10:32 AM] Network Problems

Presently, our Verizon and Level(3) circuits are completely out of service. We are awaiting information as to the cause of the outage. We are carrying customer traffic on Sprint and Global Crossing; there will be routing instabilities as circuits go up and down during the repair window. We will post further information as it becomes available.

[Jun 26, 2009, 10:12 AM] Network Problems

We are seeing problems in Verizon's network, with intermittent drops of up to 70% of customer traffic on that circuit. We have opened a ticket to investigate the cause, which appears to be isolated to Verizon.

[Jun 26, 2009, 4:02 AM] linato Downtime

linato (www186) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 26, 2009, 4:01 AM] gessire Downtime

gessire (www273) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 25, 2009, 8:58 PM] muin Maintenance Completed

The drive swap for muin is complete. It now has a 160GB drive. Downtime was about 5 minutes.

[Jun 25, 2009, 8:26 PM] muin Emergency Maintenance

muin (www23) will be taken down shortly to swap out a failing drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Jun 25, 2009, 6:27 PM] muin Downtime

muin (www23) became unresponsive under high load and was reset. A manual file check was performed before bringing the server online. Downtime was less than 10 minutes.

[Jun 25, 2009, 6:09 PM] eltsi Downtime

eltsi (www459) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 25, 2009, 2:10 PM] fearn Downtime

fearn (www40) crashed and was rebooted. Downtime was under 5 minutes.

[Jun 25, 2009, 11:55 AM] ailm Downtime

ailm (www28) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 25, 2009, 6:47 AM] eite Downtime

eite (www38) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Jun 25, 2009, 12:35 AM] zirx Downtime

zirx (www106) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jun 24, 2009, 10:19 PM] ocha, vert Maintenance Completed

We have completed the maintenance on these servers. ocha (www355) now has a 250GB hard drive, and vert (www102) has a 160GB hard drive. Downtime for each was about 10 minutes.

[Jun 24, 2009, 8:12 PM] ocha, vert Planned Maintenance

Later tonight we will be taking ocha (www355) and vert (www102) down for drive swaps. Downtime for each server should not exceed 10 minutes. An additional notice will be posted once the maintenance is complete.

[Jun 24, 2009, 5:13 PM] itonami Downtime

itonami (www333) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 24, 2009, 3:34 PM] nish Downtime

The server nish (www92) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Jun 24, 2009, 11:21 AM] vuae Downtime

vuae (www93) encountered an error and reset. Downtime was about 5 minutes.

[Jun 24, 2009, 10:23 AM] glikk Downtime

glikk (www119) crashed and was reset. Downtime was about 5 minutes.

[Jun 24, 2009, 2:13 AM] bganat Downtime

bganat (www481) encountered an error and had to be reset. Downtime was less than 5 minutes.

[Jun 23, 2009, 11:33 AM] cele Downtime

The server cele (www73) encountered an error and was reset. Downtime was under 10 minutes.

[Jun 23, 2009, 11:28 AM] kesa Downtime

kesa (www479) became unresponsive and was reset. Downtime was under 10 minutes.

[Jun 23, 2009, 11:20 AM] vsael Downtime

vsael (www173) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jun 23, 2009, 2:09 AM] dsumaui Downtime

dsumaui (www275) encountered an error and had to be reset. Downtime was less than 5 minutes.

[Jun 22, 2009, 8:16 PM] aedde Downtime

aedde (www84) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 22, 2009, 7:43 PM] siyazi Maintenance Completed

siyazi (www251) now has a 160GB drive. Downtime was about 10 minutes.

[Jun 22, 2009, 7:27 PM] siyazi Emergency Maintenance

siyazi (www251) crashed while in service. During this downtime, the primary drive was replaced.

[Jun 22, 2009, 6:43 PM] siyazi Downtime

siyazi (www251) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Jun 22, 2009, 5:59 PM] Server Reboots

Over the next few hours, we will be rebooting all shared user account servers as part of regular operating system maintenance. Downtime should be 5-10 minutes or less for each machine. We will post another notice when this maintenance is complete.

[Jun 22, 2009, 5:33 PM] siyazi Downtime

The server siyazi (www251) ran out of swap space and was rebooted. The total downtime for this server was approximately 10 minutes.

[Jun 22, 2009, 10:43 AM] cenena Downtime

cenena (www469) encountered an error and was reset. Downtime was under 10 minutes.

[Jun 22, 2009, 9:28 AM] ohayou Downtime

ohayou (www477) encountered an error and was reset. Downtime was under 10 minutes.

[Jun 22, 2009, 12:35 AM] nwalme Downtime

nwalme (www57) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 21, 2009, 8:57 PM] dieci Downtime

dieci (www231) crashed and was rebooted. Downtime was about 15 minutes.

[Jun 21, 2009, 4:06 AM] xomi Downtime

xomi (www169) encountered an error and had to be rebooted. Downtime was less than 5 minutes.

[Jun 20, 2009, 11:15 AM] dieci Downtime

dieci (www231) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 20, 2009, 10:41 AM] chi Downtime

chi (www14) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 20, 2009, 8:12 AM] hachi Downtime

hachi (www344) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 20, 2009, 4:32 AM] roomen Downtime

roomen (www61) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 20, 2009, 12:20 AM] karkar Downtime

karkar (www429) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 20, 2009, 12:19 AM] parma Downtime

parma (www42) encountered an error and was reset. Downtime was about 10 minutes.

View Older Notices