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 posted to the "pair.notices" newsgroup on our customer news server, and 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

[Oct 11, 2008, 12:44 PM] khin Downtime

khin (www184) became unresponsive while in service and needed to be rebooted. Total downtime was 10 minutes.

[Oct 11, 2008, 10:18 AM] idouei Downtime

idouei (www292) became unresponsive due to high load and was reset. Downtime was about 15 minutes.

[Oct 11, 2008, 8:15 AM] aveu Downtime

aveu (www192) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 9, 2008, 9:51 PM] naam, klesh Maintenance Completed

Tonight's maintenance is complete. A new shadow drive has been installed in naam. During the drive upgrade for klesh a problem was discovered with the chassis. It has also received a chassis swap in addition to the drive upgrade. It is now a P4 3.0 with 2GB of RAM and a 120GB drive. Downtime was about 15 minutes.

[Oct 9, 2008, 8:01 PM] naam, klesh Planned Maintenance

klesh (www200) will be taken down shortly for a drive upgrade. naam (www114) will be taken down to swap out a failing shadow drive. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Oct 9, 2008, 6:35 PM] soputan Downtime

soputan (www408) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Oct 9, 2008, 11:47 AM] tama Emergency Maintenance

tame (www70) experienced a hardware failure and was given an emergency chassis swap. The server is now a Core 2 6400 with 2GB of RAM. Downtime was about 15 minutes.

[Oct 9, 2008, 11:32 AM] beith Emergency Maintenance

beith (www17) suffered a primary drive failure earlier this morning (at about 10:08am EDT), and was swapped to the shadow drive. User files were current as of 5:20am Eastern time today, and mail files were current as of 8:40am Eastern today. Total downtime for the maintenance was approximately 25 minutes.

[Oct 9, 2008, 11:04 AM] amse Downtime

amse (www210) became unresponsive while in service and needed to be rebooted. The cause of the crash was found to be failing RAM, so 1GB of new RAM was swapped into the server. Total downtime for the server was about 35 minutes.

[Oct 9, 2008, 10:04 AM] beith Downtime

beith (www17) became unresponsive while in service and needed to be rebooted. Total downtime was less than 15 minutes.

[Oct 8, 2008, 10:14 PM] manam, abej, cuzea Maintenance Completed

Tonight's maintenance is complete. A new shadow drive has been installed in manam. abej is now a Core2 E7200 with 2GB of RAM. cuzea is now a Core2 E6550 with 2GB of RAM. Downtime was under 10 minutes for each server.

[Oct 8, 2008, 8:17 PM] manam, abej, cuzea Planned Maintenance

manam (www428) will be taken down shortly to replace a failing shadow drive. abej (www464) and cuzea (www94) will be taken down for chassis upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the maintenance is complete.

[Oct 8, 2008, 6:07 PM] abej Downtime

abej (www464) reset itself and was online within a few minutes.

[Oct 8, 2008, 4:19 PM] abej Downtime

abej (www464) became unresponsive while in service and required a reboot. Downtime was 10 minutes.

[Oct 8, 2008, 1:25 PM] cuzea Downtime

cuzea (www94) became unresponsive while in service and required a reboot. Downtime was 5 minutes.

[Oct 7, 2008, 9:08 PM] wutare Downtime

wutare (www277) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 7, 2008, 6:29 PM] cuzea Downtime

cuzea (www94)became unresponsive while in service and required a reboot. Downtime was 15 minutes.

[Oct 7, 2008, 4:09 PM] cuzea Downtime

cuzea (www94) reset itself and was online within a few minutes.

[Oct 7, 2008, 4:07 PM] cuzea Downtime

cuzea (www94) became unresponsive while in service and required a reboot. Downtime was 10 minutes.

[Oct 7, 2008, 3:23 PM] karkar Downtime

karkar (www429) became unresponsive while in service and required a reboot. Downtime was 15 minutes.

[Oct 6, 2008, 8:28 PM] abej Downtime

abej (www464) became unresponsive while in service and required a reboot. Downtime was about 15 minutes.

[Oct 6, 2008, 3:08 PM] amutka Downtime

amutka (www369) became unresponsive while in service and required a reboot. Downtime was 10 minutes.

[Oct 6, 2008, 10:41 AM] kappa Downtime

kappa (www6) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Oct 6, 2008, 9:56 AM] or Downtime

or (www34) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 6, 2008, 3:03 AM] hyarmen Downtime

hyarmen (www66) became unresponsive during service and was reset. Downtime was about 5 minutes.

[Oct 5, 2008, 11:33 PM] gyaku Downtime

gyaku (www351) encountered an error and rebooted itself. Downtime was less then 5 minutes.

[Oct 5, 2008, 9:09 PM] thenge Downtime

thenge (www270) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 5, 2008, 8:57 PM] bganat Downtime

bganat (www481)became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 5, 2008, 5:51 PM] poict Maintenance Completed

The drive upgrade on yotoy has been completed. The primary drive is now 160GB. Downtime for the upgrade was about 15 minutes.

[Oct 5, 2008, 4:03 PM] poict Planned Maintenance

Later today, poict (www195) will be taken down for a drive swap. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is complete.

[Oct 5, 2008, 8:55 AM] udumti Downtime

udumti (www312) encountered an error and rebooted itself. Downtime was less then 5 minutes.

[Oct 5, 2008, 6:17 AM] udumti Downtime

udumti (www312) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 4, 2008, 11:08 PM] thesel Emergency Maintenance

thesel (www99) crashed a second time and was given an emergency chassis swap. The server remains a Core 2 6400 with 2GB of RAM. Downtime was about 15 minutes.

[Oct 4, 2008, 10:07 PM] thesel Downtime

thesel (www99) crashed and was rebooted. Downtime was under 10 minutes.

[Oct 4, 2008, 10:22 AM] suoh Downtime

suoh (www396) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 4, 2008, 9:49 AM] qaske Downtime

qaske (www250) became unresponsive due to high load and was reset. Downtime was 20 minutes.

[Oct 4, 2008, 4:24 AM] bganat Downtime

bganat (www481) crashed while in service and had to be rebooted. Downtime was less than 10 minutes.

[Oct 4, 2008, 4:16 AM] yotoy Maintenance Completed

The drive upgrade on yotoy has been completed. The primary drive is now 160GB. Downtime for the upgrade was about 5 minutes.

[Oct 4, 2008, 12:40 AM] muin Downtime

muin (www23) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 3, 2008, 10:36 PM] yotoy Planned Maintenance

Later tonight, yotoy (www461) will be taken down for a drive swap. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is complete.

[Oct 3, 2008, 7:00 PM] epsilon Downtime

epsilon (www3) was rebooted to to clear an error condition. Downtime was under 10 minutes. We are monitoring this server closely.

[Oct 3, 2008, 5:47 PM] epsilon Downtime

epsilon (www3) was rebooted to to clear an error condition. Downtime was under 5 minutes.

[Oct 3, 2008, 4:58 PM] tama Downtime

tama (www70) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 3, 2008, 2:49 PM] aedde Downtime

aedde (www84) became unresponsive while in service and required a reboot. Downtime was 15 minutes.

[Oct 3, 2008, 2:48 PM] yiwen Downtime

yiwen (www246) became unresponsive while in service and required a reboot. Downtime was 15 minutes.

[Oct 3, 2008, 12:20 AM] muin Downtime

muin (www23) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 2, 2008, 10:43 PM] alilos Downtime

alilos (www296) crashed and was rebooted. Downtime was under 10 minutes.

[Oct 2, 2008, 3:37 PM] epsilon Downtime

epsilon (www3) was rebooted to to clear an error condition. Downtime was under 5 minutes.

[Oct 2, 2008, 1:38 PM] Call Center Outage

For approximately ten minutes, starting at about 1:20 PM Eastern, our phone system reported that the Support line was closed, and did not allow calls through. This has been corrected. We apologize for the inconvenience.

[Oct 2, 2008, 7:37 AM] jera Downtime

jera (www142) encountered an error and was reset. Downtime was under 5 minutes.

[Oct 2, 2008, 1:22 AM] sirung Maintenance Completed

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

[Oct 2, 2008, 12:51 AM] sirung Emergency Maintenance

sirung (www409) 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.

[Oct 1, 2008, 11:08 PM] vsael Downtime

vsael (www173) encountered an error and was reset. Downtime was less than 5 minutes.

[Oct 1, 2008, 6:30 PM] cuzea Downtime

cuzea (www94) became unresponsive while in service and was reset. Downtime was about 15 minutes.

[Oct 1, 2008, 10:22 AM] xoopi Downtime

xoopi (www266) crashed due to high load and was reset. Downtime was about 5 minutes.

[Oct 1, 2008, 9:54 AM] bganat Downtime

bganat (www481) encountered an error and was reset. Downtime was under 20 minutes.

[Oct 1, 2008, 9:16 AM] tinne Downtime

tinne (www21) encountered an error and was reset. Downtime was under 15 minutes.

[Oct 1, 2008, 8:07 AM] tinne Downtime

tinne (www21) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 1, 2008, 5:07 AM] kappa Downtime

kappa (www6) Encountered an error during operation and was reset. Downtime was about 5 minutes.

[Oct 1, 2008, 3:45 AM] kappa, wokkil, zirx, epsilon Maintenance Completed

Today's maintenance is complete. kappa, wokkil, and zirx are now Core2 E6400's with 2GB of RAM. epsilon now has a 160GB drive. Downtime for each server was under 10 minutes.

[Oct 1, 2008, 12:52 AM] rho Downtime

rho (www11) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 1, 2008, 12:27 AM] kappa, wokkil, zirx, epsilon Planned Maintenance

kappa (www6), wokkil (www249), and zirx (www106) will be taken down shortly for chassis upgrades. epsilon (www3) will be taken down for a drive upgrade. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Sep 30, 2008, 8:30 PM] kappa Downtime

kappa (www6) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Sep 30, 2008, 4:39 PM] ur Downtime

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

[Sep 30, 2008, 2:26 PM] uinus Downtime

uinus (www228) became unresponsive while in service and required a reboot. Downtime was 5 minutes.

[Sep 30, 2008, 2:25 PM] enso Downtime

enso (www152) became unresponsive while in service and required a reboot. Downtime was 15 minutes.

[Sep 30, 2008, 11:23 AM] sali Downtime

sali (www454) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Sep 30, 2008, 9:39 AM] auma Downtime

auma (www86) encountered high load and was reset. Downtime was under five minutes.

[Sep 30, 2008, 2:52 AM] oku Maintenance Completed

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

[Sep 30, 2008, 2:07 AM] oku Emergency Maintenance

oku (www374) 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.

[Sep 30, 2008, 12:48 AM] mildh Downtime

mildh (www87) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 28, 2008, 7:29 PM] soputan Downtime

soputan (www408) became unresponsive while in service and was reset. Downtime was about 15 minutes.

[Sep 27, 2008, 11:57 PM] namt Downtime

namt (www196) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 27, 2008, 11:31 PM] tama Downtime

tama (www70) was rebooted to clear an error condition. Downtime was under 10 minutes.

[Sep 27, 2008, 11:11 PM] cuzea Downtime

cuzea (www94) crashed and was rebooted. Downtime was under 10 minutes.

View Older Notices