[Jul 12, 2008, 1:31 AM] cuzea Downtime
cuzea (www94) encountered an error and reset. Downtime was less than 10 minutes.

[Jul 12, 2008, 12:48 AM] nish Downtime

nish (www92) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 11, 2008, 11:20 PM] kuroi Downtime

kuroi (www354) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 11, 2008, 8:38 PM] hwesta Downtime

hwesta (www51) crashed and was rebooted. Downtime was under 5 minutes.

[Jul 11, 2008, 3:27 PM] emra Downtime

emra (www183) crashed due to high load and was reset. Downtime was about 15 minutes.

[Jul 11, 2008, 3:21 PM] tisibo Downtime

tisibo (www265) became unresponsive while in service and was rebooted. Total downtime was less than 10 minutes.

[Jul 11, 2008, 11:14 AM] tisibo Downtime

tisibo (www265) became unresponsive while in service and was rebooted. Total downtime was less than 10 minutes.

[Jul 11, 2008, 10:48 AM] wokkil Downtime and RAM Upgrade

wokkil (www249) ran out of swap space and needed to be reset. While the server was down, 1GB of RAM was added to server, bringing it up to a total of 2GB RAM. Total downtime was about 20 minutes.

[Jul 11, 2008, 6:03 AM] kappa Downtime

kappa (www6) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 11, 2008, 4:26 AM] cuzea Downtime

cuzea (www94) encountered and error and was reset. Downtime was about 10 minutes.

[Jul 11, 2008, 12:24 AM] flunn Downtime

flunn (www123) crashed and had to be rebooted. While the server was down a manual check had to be done on the hard drive. Downtime was about 15 minutes.

[Jul 10, 2008, 9:03 PM] azuma Downtime

azuma (www414) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jul 10, 2008, 4:17 PM] namt Downtime

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

[Jul 10, 2008, 2:59 AM] emra, vinke, ipre, talang Maintenance Completed

Today's maintenance is complete. emra, vinke, ipre, and talang each now have a 160GB drive. Downtime for each server was about 5 minutes.

[Jul 10, 2008, 12:03 AM] emra, vinke, ipre, talang Planned Maintenance

emra (www183), vinke (www470), ipre (www181), and talang (www391) will be taken down shortly for drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 9, 2008, 11:52 PM] itonami Downtime

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

[Jul 9, 2008, 8:45 PM] terfideu Downtime

terfideu (www271) was reset to clear an error condition. Downtime was about a minute.

[Jul 9, 2008, 6:09 PM] omicron Downtime

omicron (www9) encountered an error and was reset. Downtime was under 10 minutes.

[Jul 9, 2008, 12:40 PM] arda Downtime

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

[Jul 9, 2008, 10:58 AM] zirx Downtime

zirx (www106) crashed due to high load and was reset. Downtime was about 10 minutes.

[Jul 9, 2008, 10:13 AM] iruvul Downtime

iruvul (www239) became unresponsive while in service and was rebooted. Total downtime was less than 15 minutes.

[Jul 9, 2008, 6:22 AM] kwarcu, emra, terfideu Maintenance Completed

Today's maintenance is complete. kwarcu now has a 120GB drive. terfideu now has a 160GB drive. Downtime for each server was about 5 minutes. The upgrade for emra will be pushed back to a later date.

[Jul 9, 2008, 3:10 AM] iruvul Downtime

iruvul (www239) encountered an error while in service and was reset. Downtime was about 5 minutes.

[Jul 9, 2008, 2:27 AM] kwarcu, emra, terfideu Planned Maintenance

kwarcu (www293), emra (www183), and terfideu (www271) will be taken down shortly for drive upgrades. Downtime for each server should be about 5 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 8, 2008, 4:50 PM] talang Downtime

talang (www391) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 8, 2008, 8:45 AM] emra Downtime

emra (www183) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 8, 2008, 2:32 AM] azuma Downtime

azuma (www414) encountered an error and was reset. Downtime was about 15 minutes.

[Jul 8, 2008, 1:15 AM] oomur Planned Maintenance

oomur (www209) will be taken down shortly to correct an error condition. Downtime should be under 10 minutes.

[Jul 7, 2008, 10:13 PM] iruvul Downtime

iruvul (www239) encountered an error and was rebooted. Downtime was less than 10 minutes.

[Jul 7, 2008, 11:41 AM] emra Downtime

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

[Jul 7, 2008, 9:00 AM] thuule Downtime

thuule (www49) encountered an error while in service and was reset. Downtime was about 5 minutes.

[Jul 6, 2008, 1:28 PM] duwo Downtime

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

[Jul 6, 2008, 12:49 PM] anga Downtime

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

[Jul 6, 2008, 5:30 AM] thenge Downtime

thenge (www270) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 6, 2008, 5:07 AM] arda Downtime

arda (www62) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Jul 5, 2008, 10:15 PM] vert Downtime

vert (www102) crashed and was rebooted. Downtime was under 5 minutes.

[Jul 5, 2008, 3:59 PM] db6 Maintenance Completed

The chassis swap on db6.pair.com has been completed. It is now an Athlon XP 3000+ with 1GB of RAM. Total downtime was about 30 minutes.

[Jul 5, 2008, 3:19 PM] db6 Emergency Maintenance

The db6.pair.com database server will be taken down in order to swap out a failing chassis. Another notice will be posted upon completion of the maintenance.

[Jul 4, 2008, 3:19 PM] oynos Downtime

oynos (www218) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 4, 2008, 7:58 AM] bellat Downtime

bellat (www101) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 3, 2008, 9:43 PM] bunepi Downtime

bunepi (www318) will be reset to clear an error condition. Downtime will be approximately 5 minutes.

[Jul 3, 2008, 9:43 PM] tebba Downtime

tebba (www160) encountered an error and was reset. Downtime was under 5 minutes.

[Jul 3, 2008, 11:48 AM] otaku Downtime

otaku (www338) ran out of swap space and needed to be rebooted. Total downtime was about 20 minutes.

[Jul 3, 2008, 2:31 AM] naam, qiorre, kwarcu Maintenance Completed

Tonight's maintenance is complete. naam and qiorre now have 160GB drives. A new shadow drive has been installed in kwarcu. Downtime for each server was about 5 minutes.

[Jul 3, 2008, 12:25 AM] naam, qiorre, kwarcu Planned Maintenance

naam (www114) and qiorre (www482) will be taken down shortly for drive upgrades. kwarcu will be taken down for a shadow drive upgrade. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 2, 2008, 9:46 AM] auddo Downtime

auddo (www253) became unresponsive while in service and was rebooted. Total downtime was 15 minutes.

[Jul 2, 2008, 8:35 AM] arda Downtime

arda (www62) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 2, 2008, 7:29 AM] rho Downtime

rho (www11) crashed due to a high load and was rebooted. The total downtime from this was under 10 minutes.

[Jul 2, 2008, 3:09 AM] cuzea Downtime

cuzea (www94) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 1, 2008, 8:59 PM] paell Maintenance Completed

The maintenance for paell (www153) has been completed. The server is now a Core 2 Duo E6420 with 2GB DDR2 RAM. Downtime was approximately 15 minutes.

[Jul 1, 2008, 8:33 PM] paell Emergency Maintenance

paell (www153) is being taken down to perform an emergency chassis swap. An additional notice will be posted with the swap is complete.

[Jul 1, 2008, 10:55 AM] ruis Downtime

The server ruis(www27) crashed due to a high load and was rebooted. The total downtime from this was under 10 minutes.

[Jul 1, 2008, 6:00 AM] aster, dallol, zirx, nish Maintenance Completed

Today's upgrades are complete. aster now has a 120GB drive. dallol and nish now have 200GB drives. zirx has a 160GB drive. Downtime for each server was under 10 minutes.

[Jul 1, 2008, 1:52 AM] aster, dallol, zirx, nish Planned Maintenance

aster (www96), dallol (www379), zirx (www106), and nish (www92) will be taken down shortly for drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jun 30, 2008, 5:18 PM] nuumen Downtime

nuumen (www55) encountered high load and was reset. Downtime was under 10 minutes.

[Jun 30, 2008, 6:03 AM] iruvul Downtime

iruvul (www239) encountered and error and was reset. Downtime was about 5 minutes.

[Jun 29, 2008, 4:13 PM] paell Downtime

paell (www153) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Jun 29, 2008, 11:59 AM] aqquz Downtime

The server aqquz(www248) crashed due to a high load and was rebooted. The total downtime was under 15 minutes.

[Jun 29, 2008, 4:45 AM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 28, 2008, 10:59 PM] aqquz Downtime

aqquz (www248) crashed and required a manual file system check. Downtime was under 15 minutes.

[Jun 28, 2008, 7:28 PM] hakone Downtime

hakone (www415) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 28, 2008, 4:16 PM] aveu Emergency Maintenance

aveu (www192) suffered a hardware failure and was given a chassis swap. It is now an Athlon XP 2800+ with 2GB of RAM. Downtime was about 50 minutes.

[Jun 28, 2008, 12:46 PM] theta Downtime

theta (www4) became unresponsive under load and was reset. Downtime was about 10 minutes.

[Jun 28, 2008, 12:10 PM] aqquz Downtime

aqquz (www248) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Jun 26, 2008, 6:06 PM] kanat Downtime

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

[Jun 26, 2008, 4:49 PM] paell Downtime

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

[Jun 26, 2008, 3:00 PM] salak Downtime

salak (www397) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Jun 26, 2008, 2:04 PM] paell Downtime

paell (www153) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Jun 26, 2008, 9:21 AM] kanat Downtime

kanat (www128) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Jun 26, 2008, 4:59 AM] neled Downtime

neled (www127) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 26, 2008, 3:25 AM] muin Downtime

muin (www23) crashed while in service and had to be rebooted. Downtime was about 10 minutes.

[Jun 26, 2008, 2:10 AM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 25, 2008, 9:10 PM] caseta Downtime

caseta (www448) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Jun 25, 2008, 6:55 PM] itonami Downtime

itonami (www333) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Jun 25, 2008, 4:55 PM] Network Problems Resolved

AT&T was able to route our traffic around the fiber cut, and our circuit resumed service at approximately 4:30 PM Eastern. We have been advised there is a chance the circuit will go down again, during or after AT&T's emergency maintenance. We have plenty of extra capacity on our other providers to handle such an outage.

[Jun 25, 2008, 4:23 PM] Network Problems

At approximately 4:15 PM Eastern, our AT&T gigabit circuit went out of service. Traffic switched over automatically to our other providers, with no loss of service.

We have been advised by our vendor that a fiber cut has caused the outage; however, there is currently no estimated time to repair. We'll post more information as it becomes available.

[Jun 25, 2008, 10:28 AM] oynos Downtime

oynos (www218) crashed due to high load and was reset. Downtime was under 10 minutes.

[Jun 25, 2008, 8:58 AM] dukoni Downtime

dukoni (www305) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 25, 2008, 8:23 AM] aqquz Downtime

aqquz (www248) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 24, 2008, 11:24 PM] ansuz Maintenance Completed

The Primary Hard Drive swap has been completed for server ansuz. Downtime was under 15 minutes.

[Jun 24, 2008, 10:33 PM] ansuz Planned Maintenance

ansuz (www137) will be taken down shortly to replace a failing primary drive. A second notice will be posted once the maintenance is complete.

[Jun 24, 2008, 3:15 PM] rilwi Downtime

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

[Jun 24, 2008, 12:26 PM] Network Maintenance

We have been informed that the problems with our Sprint circuit (which we took offline on June 15) have been traced to a bad router interface where the circuit was handed off to us. This interface has been replaced.

This afternoon as of approximately 12:25 PM Eastern, we have returned the Sprint circuit to service. If you were having any difficulty reaching your site prior to the circuit being disabled, please notify us immediately if you see any new problems. We will again be proactively contacting customers who have opened tickets on this topic, as well.

[Jun 24, 2008, 9:37 AM] kanat Downtime

kanat (www128) crashed while in service and was reset. Downtime was less than 10 minutes.

[Jun 24, 2008, 1:42 AM] zirx Downtime

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

[Jun 23, 2008, 11:02 PM] beith Maintenance Completed

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

[Jun 23, 2008, 10:25 PM] beith Emergency Maintenance

beith (www17) will be taken down shortly to swap out a failing shadow drive. Downtime should be about 5 minutes. An additional notice will be posted when the swap is complete.

[Jun 23, 2008, 12:43 PM] glikk Downtime

The server glikk(www119) crashed due to a high load and was rebooted. The total downtime was under 15 minutes.

[Jun 23, 2008, 11:55 AM] zirx Downtime

The server zirx(www106) crashed due to a high load and was rebooted. The total downtime for this server was 10 minutes.

[Jun 22, 2008, 6:34 PM] omega Downtime

omega (www16) encountered high load and was reset. Downtime was under 15 minutes.

[Jun 22, 2008, 3:13 AM] beith Downtime

beith (www17) crashed and had to be rebooted. Downtime was about 10 minutes.

[Jun 21, 2008, 10:46 PM] duwo Downtime

duwo (www219) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 21, 2008, 6:00 PM] tyungwa Downtime

tyungwa (www311) became unresponsive under high load and was reset. Downtime was about 10 minutes.

[Jun 21, 2008, 2:34 PM] soputan Downtime

soputan (www408) ran out of swap space and needed to be rebooted. Total downtime was 15 minutes.

[Jun 20, 2008, 10:35 AM] chi Downtime

chi (www14) became unresponsive while in service and was rebooted. Total downtime was 10 minutes.

[Jun 20, 2008, 4:24 AM] nish Downtime

nish (www92) crashed due to high load and had to be rebooted. Downtime was about 5 minutes.

[Jun 19, 2008, 11:00 PM] otaku Maintenance Completed

The shadow drive swap for otaku is complete. Downtime was about 10 minutes.

[Jun 19, 2008, 10:40 PM] otaku Emergency Maintenance

otaku (www338) will be taken down shortly to swap out a failing shadow drive. Downtime should be about 5 minutes. An additional notice will be posted when the swap is complete.

[Jun 19, 2008, 5:43 PM] cuzea Maintenance Completed

The drive swap for cuzea is complete. The server still has a 250GB drive. Downtime was about 5 minutes.

[Jun 19, 2008, 4:27 PM] cuzea Emergency Maintenance

cuzea (www94) will be taken down shortly to swap out a failing drive. Downtime should be about 5 minutes. An additional notice will be posted when the swap is complete.

[Jun 19, 2008, 3:22 PM] anca Downtime

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

[Jun 18, 2008, 10:12 PM] vilya Maintenance Completed

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

[Jun 18, 2008, 9:54 PM] vilya Emergency Maintenance

vilya (www60) will be taken down shortly to swap out a failing shadow drive. Downtime should be about 5 minutes. An additional notice will be posted when the swap is complete.

[Jun 18, 2008, 9:48 PM] pi Emergency Maintenance

pi (www10) became unresponsive while in service and was given a chassis swap. It is now a Core2 6420 with 2GB of RAM. Downtime was approximately 25 minutes.

[Jun 18, 2008, 7:03 PM] or Downtime

or (www34) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jun 18, 2008, 5:24 PM] pi Downtime

pi (www10) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Jun 18, 2008, 4:02 PM] zirx Downtime

zirx (www106) encountered high load and was reset. Downtime was under 10 minutes.

[Jun 18, 2008, 10:04 AM] pi Downtime

pi (www10) encountered an error and reset. Total downtime was less than 5 minutes.

[Jun 18, 2008, 9:55 AM] gebo Downtime

gebo (www139) encountered an error and needed to be rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was 25 minutes.

[Jun 18, 2008, 4:20 AM] eeoth Downtime

eeoth (www85) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 18, 2008, 3:16 AM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 17, 2008, 11:44 PM] paell Downtime

paell (www153) encountered an error and was rebooted. Downtime was less than 10 minutes.

[Jun 17, 2008, 11:06 PM] gao Downtime

gao (www111) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jun 17, 2008, 4:20 PM] paat Downtime

paat (www100) encountered high load and was reset. Downtime was under 10 minutes.

[Jun 17, 2008, 3:33 PM] biont Downtime

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

[Jun 17, 2008, 3:15 PM] ciot Downtime

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

[Jun 17, 2008, 1:21 PM] namt Downtime

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

[Jun 17, 2008, 1:19 PM] zirx Downtime

zirx (www106) became unresponsive while in service and required a manual filesystem check before being brought back online. Downtime was 15 minutes.

[Jun 16, 2008, 10:17 PM] pi Downtime

pi (www10) encountered and error and was rebooted. Downtime was less than 5 minutes.

[Jun 16, 2008, 1:18 PM] uinus Downtime

uinus (www228) encountered an error and had to be restarted. Downtime was about 10 minutes.

[Jun 16, 2008, 1:06 PM] mamono Downtime

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

[Jun 16, 2008, 9:41 AM] tinne Maintenance Completed

The Shadow Drive swap on tinne (www21) has been completed. Downtime was under 10 minutes.

[Jun 16, 2008, 9:25 AM] tinne Planned Maintenance

tinne (www21) will be taken down shortly to swap out a failing Shadow Drive. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is completed.

[Jun 16, 2008, 5:06 AM] ciot Downtime

ciot (www161) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 16, 2008, 4:51 AM] alilos Downtime

alilos (www296) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jun 16, 2008, 3:28 AM] dhabat Downtime

dhabat (www105) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 15, 2008, 2:11 PM] Network Maintenance

Due to ongoing trouble reports which may or may not be related to service problems with our Sprint circuit, we have temporarily disabled the circuit so that customers with connectivity problems to pair can determine if those problems are resolved as a result.

If you have had any difficulty reaching your site over the past few days, please notify us if this issue has or has not improved. We will also be proactively contacting customers who have opened tickets on this topic.

We have plenty of surplus capacity to operate our network without Sprint, for as long as this test is necessary.

[Jun 15, 2008, 4:16 AM] terfideu Downtime

terfideu (www271) became unresponsive during service and was reset. Downtime was about 5 minutes.

[Jun 14, 2008, 11:51 PM] xebte Downtime

xebte (www230) was rebooted to clear an error condition. Downtime was under 5 minutes.

[Jun 14, 2008, 11:41 PM] kappa Downtime

kappa (www6) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 14, 2008, 8:22 PM] talang Downtime

talang (www391) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 14, 2008, 6:43 PM] talang Downtime

talang (www391) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 14, 2008, 4:34 PM] quan Downtime

quan (www120) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 14, 2008, 2:46 PM] tyungwa Downtime

tyungwa (www311) ran out of swap space and needed to be rebooted. Total downtime was under 20 minutes.

[Jun 14, 2008, 7:38 AM] duwo Downtime

duwo (www219) encountered an error while in service and had to be rebooted. Downtime was less than 5 minutes.

[Jun 14, 2008, 6:30 AM] tyungwa Downtime

tyungwa (www311) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jun 14, 2008, 2:51 AM] tyungwa Downtime

tyungwa (www311) encountered a high load and was reset. Downtime was about 10 minutes.

[Jun 13, 2008, 5:35 PM] soputan Downtime

soputan (www408) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 13, 2008, 5:04 PM] pi Downtime

pi (www10) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 13, 2008, 5:57 AM] zirx Downtime

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

[Jun 12, 2008, 4:49 AM] paell Downtime

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

[Jun 12, 2008, 2:36 AM] zirx Downtime

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

[Jun 11, 2008, 10:26 PM] ageng Maintenance Completed

The Shadow Drive swap on ageng (www403) has been completed. Downtime was under 5 minutes.

[Jun 11, 2008, 10:03 PM] ageng Planned Maintenance

ageng (www403) will be taken down shortly to swap out a failing Shadow Drive. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is completed.

[Jun 11, 2008, 8:54 PM] gao Downtime

gao (www111) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 11, 2008, 3:29 PM] fithwor Downtime

fithwor (www222) encountered high load and was reset. Downtime was under 10 minutes.

[Jun 11, 2008, 12:09 PM] zirx Downtime

zirx (www106) became unresponsive and was reset. Downtime was about 10 minutes.

[Jun 11, 2008, 11:56 AM] alilos Downtime

alilos (www296) became unresponsive and was reset. Downtime was about 5 minutes.

[Jun 11, 2008, 5:35 AM] zirx Downtime

zirx (www106) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 11, 2008, 3:52 AM] halla Downtime

halla (www68) needed a new primary hard drive due to failure. Shadow drive was upgraded to 200 GB. Downtime was about 10 minutes.

[Jun 10, 2008, 2:50 PM] kesa Downtime

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

[Jun 10, 2008, 1:07 PM] zirx Downtime

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

[Jun 10, 2008, 9:48 AM] uinus Downtime

uinus (www228) crashed due to a high load and was rebooted. The total downtime was 10 minutes.

[Jun 10, 2008, 4:20 AM] zirx Downtime

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

[Jun 9, 2008, 10:27 AM] elhaz Downtime

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

[Jun 9, 2008, 10:27 AM] tehun Downtime

The server tehun(www226) crashed due to a high load and was rebooted. Downtime was under 10 minutes.

[Jun 9, 2008, 6:52 AM] nish Downtime

nish (www92) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 9, 2008, 6:13 AM] wutare Downtime

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

[Jun 9, 2008, 12:38 AM] jera Downtime

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

[Jun 8, 2008, 9:58 PM] uttu Downtime

uttu (www456) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jun 8, 2008, 3:54 PM] olonto Downtime

olonto (www460) became unresponsive while under high load and was reset. Downtime was 5 minutes.

[Jun 8, 2008, 12:07 PM] harma Emergency Maintenance

harma (www50) required a chassis swap due to failed hardware. It is now an Intel Core2 6420 with 2GB of RAM. Total downtime was about 25 minutes.

[Jun 8, 2008, 9:28 AM] ocha Downtime

ocha (www355) became unresponsive due to high load and was reset. Downtime was 20 minutes.

[Jun 8, 2008, 6:19 AM] muin Downtime

muin (www23) Encountered an error and needed to be reset. Downtime was about ten minutes.

[Jun 7, 2008, 9:04 AM] saakal Downtime

saakal (www264) became unresponsive while in server and was reset. Downtime was 10 minutes.

[Jun 7, 2008, 7:57 AM] jera Downtime

jera (www142) encountered an error and was reset. Downtime was less than 10 minutes.

[Jun 7, 2008, 7:55 AM] aerre Downtime

aerre (www185) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 7, 2008, 5:06 AM] kanat Downtime

kanat (www128) encountered an error and was reset. Downtime was less than 10 minutes.

[Jun 7, 2008, 1:56 AM] ynilo Downtime

ynilo (www166) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jun 6, 2008, 3:43 PM] iruvul Downtime

iruvul (www239) became unresponsive and was reset. Downtime was 10 minutes.

[Jun 6, 2008, 11:54 AM] otok Downtime

otok (www131) required a reboot to clear an error condition. Downtime was 5 minutes.

[Jun 6, 2008, 11:28 AM] xebte Emergency Maintenance

xebte (www230) became unresponsive while in service and was given a chassis swap. It is now an Intel Core2 6420 with 2GB of RAM. Total downtime was about 35 minutes.

[Jun 6, 2008, 11:13 AM] ynilo Downtime

ynilo (www166) became unresponsive while in service and required a reboot. Downtime was 20 minutes.

[Jun 6, 2008, 11:01 AM] onn Downtime

onn (www29) became unresponsive and was reset. Downtime was 10 minutes.

[Jun 6, 2008, 8:31 AM] xebte Downtime

xebte (www230) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jun 6, 2008, 7:46 AM] mirozo Downtime

mirozo (www257) encountered a high load and was reset. Downtime was about 10 minutes.

[Jun 6, 2008, 7:44 AM] ynilo Downtime

ynilo (www166) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 6, 2008, 5:48 AM] zirx Downtime

zirx (www106) became unresponsive and had to be reset. Downtime was less than 10 minutes.

[Jun 6, 2008, 4:09 AM] xebte Downtime

xebte (www230) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Jun 6, 2008, 12:14 AM] mu Downtime

mu (www7) crashed and required a manual file system check. Downtime was under 15 minutes.

[Jun 5, 2008, 11:44 PM] mu Downtime

mu (www7) crashed and was rebooted. Downtime was under 5 minutes.

[Jun 5, 2008, 9:05 PM] wokkil Downtime

wokkil (www249) became unresponsive and was reset. Downtime was about 5 minutes.

[Jun 5, 2008, 5:58 PM] londaste Downtime

londaste (www177) was rebooted to clear an error condition. Downtime was under 5 minutes.

[Jun 5, 2008, 3:48 PM] huath Downtime

huath (www19) require a reboot to clear an error condition. Downtime was 5 minutes.

[Jun 5, 2008, 1:49 PM] eeoth Downtime

The server eeoth(www85) crashed due to a high load and was rebooted. The total downtime was under 15 minutes.

[Jun 5, 2008, 4:40 AM] zirx Downtime

became unresponsive and was rebooted. Downtime was less than 15 minutes.

[Jun 4, 2008, 11:11 PM] kikai Downtime

kikai (www417) became unresponsive and was reset. Downtime was about 5 minutes.

[Jun 4, 2008, 11:05 PM] aster, colima, whury Maintenance Completed

Tonight's maintenance is complete. colima and whury now have 160GB drives. A new shadow drive has been installed in aster. Downtime for each server was under 10 minutes.

[Jun 4, 2008, 8:43 PM] kikai Downtime

kikai (www417) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 4, 2008, 8:43 PM] aster, colima, whury Planned Maintenance

aster (www96) will be taken down shortly for a shadow drive upgrade. colima (www423) and whury (www179) will be taken down for drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jun 4, 2008, 11:06 AM] tama Downtime

tama (www70) crashed due to high load and was reset. Downtime was about 5 minutes.

[Jun 3, 2008, 4:23 PM] kappa Downtime

kappa (www6) encountered high load and required a reset along with a manual file system check. Downtime was approximately 15 minutes.

[Jun 3, 2008, 3:27 PM] kesa Downtime

kesa (www479) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Jun 3, 2008, 1:55 PM] rilwi Downtime

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

[Jun 3, 2008, 8:47 AM] merau Downtime

merau (www245) experienced an error and was reset. Downtime was about 10 minutes.

[Jun 2, 2008, 5:38 PM] Network Problems Resolved

Over the past eleven days, we have observed intermittent traffic drops on our Sprint circuit. We have attempted to escalate the issue with Sprint but have seen no improvement nor any admission that there may have been a problem. Earlier today, we rerouted traffic destined to Verizon customers (primarily, we believe, FiOS users) through AT&T, and since that time, we have observed no further problems.

It is our belief that there may be unresolved connectivity problems between Sprint and Verizon, but we have only indirect empirical evidence. In any case, this rerouting appears to avoid the problem for our customers. We apologize for the intermittent disruptions this caused for some customers up until this point.

[Jun 2, 2008, 3:27 PM] onn Downtime

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

[Jun 2, 2008, 3:14 PM] PHP 5.2.6

All servers will be upgraded to PHP 5.2.6 today. This version patches some security issues with PHP 5.2.5. For a full list of changes, please see the PHP 5.2.6 Release Announcement at http://www.php.net/releases/5_2_6.php. Please contact support@pair.com with any questions.

[Jun 2, 2008, 2:02 PM] iruvul Downtime

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

[Jun 2, 2008, 9:28 AM] zirx Downtime

zirx (www106) crashed while in service and was reset. Downtime was about 10 minutes.

[Jun 1, 2008, 11:31 PM] elhaz Downtime

elhaz (www144) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jun 1, 2008, 12:18 AM] noldo Downtime

noldo (www56) experienced an error and was reset. Downtime was about 10 minutes.

[May 31, 2008, 9:01 PM] fearn Downtime

fearn (www40) was rebooted to clear an error condition. Downtime was under 5 minutes.

[May 31, 2008, 8:27 PM] chi Downtime

chi (www14) crashed and was rebooted. Downtime was under 5 minutes.

[May 31, 2008, 4:45 AM] noldo Downtime

noldo (www56) crashed while in service and had to be rebooted. Downtime was about 10 minutes.

[May 31, 2008, 1:34 AM] elhaz Downtime

elhaz (www144) encountered an error and was reset. Downtime was about 10 minutes.

[May 30, 2008, 6:21 PM] flure Downtime

flure (www75) encountered an error and was reset. Downtime was about 5 minutes.

[May 30, 2008, 4:28 AM] zirx Downtime

zirx (www106) encountered an error while in service and had to be rebooted. Downtime was about 5 minutes.

[May 30, 2008, 1:19 AM] flunn Downtime

flunn (www123) encountered an error and was reset. Downtime was about 15 minutes.

[May 29, 2008, 9:15 PM] vinke Maintenance Completed

The shadow drive swap for vinke is complete. Downtime was under 5 minutes.

[May 29, 2008, 8:59 PM] vinke Emergency Maintenance

vinke (www470) will be taken down shortly to replace a failed shadow drive. Downtime should be about 5 minutes. An additional notice will be posted when the swap is complete.

[May 29, 2008, 2:50 PM] gief Downtime

The server gief(www178) crashed due to a high load and was rebooted. The total downtime for this server was approximately 10 minutes.

[May 29, 2008, 2:06 PM] tisibo Downtime

The server tisibo(www265) crashed due to a high load and was rebooted. The total downtime for this server was under 10 minutes.

[May 29, 2008, 5:26 AM] paell Emergency Maintenance

paell (www153) lost network connectivity due to a failing piece of hardware which has been replaced. Downtime was about 15 minutes.

[May 28, 2008, 5:17 PM] seyyav Downtime

seyyav (www238) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 28, 2008, 3:13 PM] duwo Downtime

The server duwo(www219) crashed due to a high load and was rebooted. The total downtime was 10 minutes.

[May 28, 2008, 1:48 PM] batur Downtime

The server batur(www401) crashed due to a high load and was rebooted. The total downtime for this server was under 15 minutes.

[May 28, 2008, 11:12 AM] elhaz Downtime

elhaz (www144) encountered an error and was reset. Downtime was under 10 minutes.

[May 27, 2008, 9:20 PM] batur Downtime

batur (www401) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 27, 2008, 8:44 PM] tiwaz Downtime

tiwaz (www146) encountered an error and was rebooted. Downtime was less than 10 minutes.

[May 27, 2008, 6:17 PM] namt Downtime

namt (www196) encountered high load and was reset. Downtime was under 10 minutes.

[May 26, 2008, 12:00 AM] tyungwa Downtime

tyungwa (www311) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 25, 2008, 6:23 PM] batur Downtime

batur (www401) experienced high load and required a reset. Downtime was under five minutes.

[May 25, 2008, 4:09 PM] huila Downtime

huila (www452) became unresponsive and was reset. Downtime was 5 minutes.

[May 25, 2008, 11:26 AM] bhoth Downtime

bhoth (www163) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 25, 2008, 8:58 AM] jera Downtime

jera (www142) became unresponsive while in service and was reset. Downtime was 5 minutes.

[May 25, 2008, 3:40 AM] iyaaku Emergency Maintenance

iyaaku (www310) encountered an error and was rebooted. Due to the recent hardware issues with this server it has been swapped with a new chassis. It is now a P4 3.0GHz with 2GB RAM. Total downtime for the swap was about 15 minutes.

[May 25, 2008, 1:01 AM] iyaaku Downtime

iyaaku (www310) encountered an error while in service and had to be rebooted. Downtime was about 20 minutes. We apologize for any inconvenience this may have caused.

[May 24, 2008, 11:36 PM] batur Downtime

batur (www401) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 24, 2008, 9:53 PM] Network Testing

Between approximately 6:00 PM and 9:15 PM Eastern this evening, Sprint took down our gigabit circuit to perform testing in response to the problems reported on Thursday and Friday. During this time, traffic flowed over our other providers with no loss of service.

At this point, Sprint does not have an explanation for the issues. They will continue to monitor the circuit, and, of course, we will do the same.

[May 24, 2008, 9:44 PM] huila Downtime

huila (www452) became unresponsive and was rebooted. Downtime was 10 minutes.

[May 24, 2008, 6:26 PM] fayev Downtime

fayev (www365) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 24, 2008, 12:47 PM] Network Maintenance Completed

We have completed our router maintenance, and our HE.net gigabit circuit has been returned to service. It was down for less than 10 minutes, and during that time traffic flowed over our other providers.

[May 24, 2008, 12:26 PM] Network Maintenance

We will be taking down our HE.net gigabit circuit shortly, in order to perform maintenance on the router. We expect to return it to service within 15 minutes. Another notice will be posted when the maintenance is complete.

[May 24, 2008, 6:45 AM] iyaaku Downtime

iyaaku (www310) encountered an error while in service and had to be rebooted. Downtime was less than 5 minutes.

[May 24, 2008, 3:36 AM] ruis Downtime

ruis (www27) encountered an error and was reset. Downtime was about 10 minutes.

[May 23, 2008, 7:55 PM] batur Emergency Maintenance

batur (www401) became unresponsive while in service and was given a chassis swap. It is now an Intel Core2 6420 with 2GB of RAM. Downtime was less than 10 minutes.

[May 23, 2008, 4:37 PM] batur Downtime

batur (www401) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 23, 2008, 3:51 PM] Network Problems

The problems reported earlier with Sprint have again resolved themselves for most customers, but we have not yet received an answer from Sprint as to the problem. We have been switched to the "protect path" for this circuit, and Sprint will be doing complete testing on our primary path in an attempt to find the cause of the problem.

[May 23, 2008, 12:19 PM] omicron Downtime

omicron (www9) became unresponsive while in service and required a reboot. Downtime was 20 minutes.

[May 23, 2008, 11:32 AM] Network Problems

Between approximately 9:50 AM Eastern and 10:50 AM, we again saw a reduction in our traffic through Sprint. Additionally, we've received reports of customers experiencing packet loss, possibly involving the Verizon network. We are currently working to diagnose these issues, and will post more information as available.

[May 23, 2008, 9:20 AM] ocha Downtime

ocha (www355) became unresponsive under high load and was reset. Downtime was 25 minutes.

[May 23, 2008, 2:51 AM] gaccin Downtime

gaccin (www315) became unresponsive while in service and had to be rebooted. Downtime was about 10 minutes.

[May 23, 2008, 12:36 AM] ailm Emergency Maintenance

ailm (www28) suffered a chassis failure, and was given an emergency chassis swap. It is now an Intel Core 2 6400 with 2GB of RAM. Downtime was about 45 minutes.

[May 22, 2008, 11:15 PM] neter Downtime

neter (www132) crashed while in service and was rebooted. Downtime was under 10 minutes.

[May 22, 2008, 10:11 PM] aqquz Downtime

aqquz (www248) crashed while in service and was rebooted. Downtime was under 10 minutes.

[May 22, 2008, 9:12 PM] yiwen Downtime

yiwen (www246) was reset to clear an error condition. Downtime was less than 5 minutes.

[May 22, 2008, 8:50 PM] batur Downtime

batur (www401) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[May 22, 2008, 8:41 PM] yuzz Maintenance Completed

We have completed the drive swap on yuzz (www117). It now has a 160GB primary drive. Downtime was under 10 minutes.

[May 22, 2008, 8:11 PM] yuzz Planned Maintenance

We will be performing a drive swap on yuzz (www117) this evening to swap out a failing drive. An additional notice will be posted once the maintenance is completed.

[May 22, 2008, 2:57 PM] Network Problems Resolved

Our Sprint traffic levels returned to normal around 1:30 PM Eastern and have stayed normal since. We are still awaiting a final explanation for the cause of this outage from the vendor. We will, of course, continue to monitor it closely.

[May 22, 2008, 1:39 PM] kaarei Downtime

kaarei (www300) became unresponsive under high load and was rebooted. A manual file system check was required to bring the server back online. Downtime was 25 minutes

[May 22, 2008, 1:35 PM] Network Problems

We are currently investigating multiple customer reports of packet loss reaching our network. This corresponds with an as-yet unexplained drop in traffic on our Sprint gigabit line, which seems to be returning to normal. We are in contact with our vendors and will post updates as available.

[May 22, 2008, 9:50 AM] batur Downtime

batur (www401) became unresponsive while in service and was rebooted. Total downtime was 10 minutes.

[May 22, 2008, 9:00 AM] zirx Downtime

zirx (www106) became unresponsive while in service and was rebooted. Total downtime was under 15 minutes.

[May 22, 2008, 8:00 AM] batur Downtime

batur (www401) came under high load and was rebooted. Downtime was 5 minutes.

[May 22, 2008, 7:46 AM] eeoth Downtime

eeoth (www85) was rebooted to clear an error condition. Downtime was 10 minutes.

[May 22, 2008, 7:05 AM] ailm Downtime

ailm (www28) became unresponsive and was reset. Downtime was about 15 minutes.

[May 22, 2008, 5:18 AM] batur Downtime

batur (www401) was rebooted to clear an error condition. Downtime was 10 minutes.

[May 21, 2008, 5:14 PM] diaf Web Logs

The web server access log on diaf (www215) was inadvertently truncated. We have restored the portion of logs present on the ShadowDrive, but today's log will be missing hits between approximately 3:30 AM and 5:10 PM Eastern. We apologize for the inconvenience.

[May 21, 2008, 4:12 PM] misilay Downtime

misilay (www282) came under high load and was rebooted. Downtime was 5 minutes.

[May 21, 2008, 2:25 PM] aveu Downtime

aveu (www192) was rebooted to clear an error condition. Downtime was 10 minutes.

[May 21, 2008, 6:49 AM] kanat Downtime

kanat (www128) encountered and error and reset. Downtime was about 10 minutes.

[May 21, 2008, 6:08 AM] maborym Downtime

maborym (www204) encountered a high load and was reset. Downtime was about 10 minutes.

[May 21, 2008, 1:05 AM] eeoth Downtime

eeoth (www85) encountered an error and was reset. Downtime was under 10 minutes.

[May 20, 2008, 11:06 PM] batur Downtime

batur (www401) crashed a second time this evening. Downtime was under 5 minutes.

[May 20, 2008, 10:43 PM] duwo Downtime

duwo (www219) crashed while in service and was rebooted. Downtime was under 5 minutes.

[May 20, 2008, 10:33 PM] zortzi Maintenance Completed

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

[May 20, 2008, 10:16 PM] batur Downtime

batur (www401) crashed while in service and was rebooted. Downtime was under 5 minutes.

[May 20, 2008, 10:12 PM] zortzi Planned Maintenance

zortzi (www243) will be taken down shortly for a drive upgrade. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[May 20, 2008, 7:12 PM] saghotta Downtime

saghotta (www259) encountered an error and was reset. Downtime was under 15 minutes.

[May 20, 2008, 3:02 PM] eeoth Downtime

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

[May 20, 2008, 12:15 AM] soputan Downtime

soputan (www408) encountered and error and reset. Downtime was about 10 minutes.

[May 19, 2008, 11:10 PM] nish Downtime

nish (www92) crashed while in service and was rebooted. Downtime was under 5 minutes.

[May 19, 2008, 9:43 PM] batur Downtime

batur (www401) crashed while in service and was rebooted. Downtime was under 10 minutes.

[May 19, 2008, 3:11 PM] ijen Downtime

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

[May 19, 2008, 2:00 PM] gebo Downtime

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

[May 19, 2008, 10:31 AM] soputan Downtime

The server soputan(www408) crashed due to a high load and was rebooted. The total downtime for this server was approximately 15 minutes.

[May 19, 2008, 8:33 AM] tyungwa Downtime

tyungwa (www311) became unresponsive and was reset. Downtime was about 10 minutes.

[May 17, 2008, 3:54 PM] zhun Downtime

zhun (www107) became unresponsive under high load and needed to be rebooted. Total downtime was 15 minutes.

[May 17, 2008, 1:22 AM] alilos Downtime

alilos (www296) became unresponsive and was reset. Downtime was about 10 minutes.

[May 17, 2008, 1:08 AM] paat Downtime

paat (www100) encountered an error and was reset. Downtime was about 10 minutes.

[May 16, 2008, 7:48 PM] calma Downtime

calma (www43) encountered an error and was reset. Downtime was less than 5 minutes.

[May 16, 2008, 11:05 AM] ninin Downtime and RAM Upgrade

ninin (www322) ran out of swap space and was rebooted. While the server was down, 1GB of RAM was added to it for a total of 2GB. Total downtime was 15 minutes.

[May 16, 2008, 8:57 AM] aerre Downtime

aerre (www185) became unresponsive while in service and was rebooted. Total downtime was under 15 minutes.

[May 15, 2008, 8:55 AM] paell Downtime

paell (www153) became unresponsive under high load and was rebooted. Total downtime was about 10 minutes.

[May 15, 2008, 5:38 AM] oshima Downtime

oshima (www416) encountered an error and was reset. Downtime was about 10 minutes.

[May 15, 2008, 5:13 AM] eeoth Downtime

eeoth (www85) became unresponsive while in service and had to be rebooted. Downtime was about 10 minutes.

[May 14, 2008, 3:43 PM] nuumen Downtime

nuumen (www55) experienced high disk activity and became unresponsive and was reset. Downtime was under 10 minutes.

[May 13, 2008, 6:02 PM] aveu Downtime

aveu (www192) encountered an error and was reset. Downtime was under five minutes.

[May 13, 2008, 3:48 AM] nyartu Maintenance Completed

The drive swap on nyartu (www254) has been completed. It now has a 160GB primary drive. Downtime was about 5 minutes.

[May 13, 2008, 3:03 AM] nyartu Emergency Maintenance

nyartu (www254) will be taken down shortly to swap out a failing drive. Downtime should be less than 5 minutes. An additional notice will be posted when this has been completed.

[May 12, 2008, 6:00 AM] mhoh Downtime

mhoh (www191) encountered an error and was reset. Downtime was about 10 minutes.

[May 10, 2008, 11:55 PM] oshima Downtime

oshima (www416) crashed and was rebooted. Downtime was under 5 minutes.

[May 10, 2008, 3:14 PM] beeoro Downtime

beeoro (www69) became unresponsive under high load was rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was approximately 25 minutes.

[May 10, 2008, 3:53 AM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was about 10 minutes.

[May 9, 2008, 5:13 PM] alayta Downtime

alayta (www380) became unresponsive under high load and was reset. Downtime was 25 minutes.

[May 9, 2008, 11:49 AM] ocha Downtime

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

[May 9, 2008, 5:50 AM] wanote, zais Maintenance Completed

Tonight's maintenance has been completed. zais (www89) is now an Intel Core 2 6400 with 2GB of RAM, and wanote (www284) now has a 160GB primary drive. Downtime for each server was under 10 minutes.

[May 9, 2008, 3:44 AM] wanote, zais Planned Maintenance

wanote (www284) will be taken down shortly for a drive upgrade. zais (www89) will be taken down for a chassis upgrade. Downtime should be less than 10 minutes per server. An additional notice will be posted when the upgrades are complete.

[May 9, 2008, 12:19 AM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was about 10 minutes.

[May 8, 2008, 11:20 PM] ulwar Downtime

ulwar (www82) was reset to clear an error condition. Downtime was about 1 minute.

[May 8, 2008, 8:26 PM] hyaku Downtime

hyaku (www345) was reset to clear an error condition. Downtime was about 1 minute.

[May 8, 2008, 7:17 PM] zais Downtime

zais (www89) encountered an error and was reset. Downtime was about 5 minutes.

[May 8, 2008, 12:15 PM] savo Downtime

savo (www436) became unresponsive under high load and was rebooted. Total downtime was 5 minutes.

[May 8, 2008, 6:40 AM] paell Downtime

paell (www153) encountered an error and reset. Downtime was less than 5 minutes.

[May 8, 2008, 5:35 AM] siyazi, kuwae, misilay, yiwen Maintenance Completed

Tonight's upgrades have been completed. kuwae, misilay, and yiwen now have 160G primary drives, and siyazi now has a 120G primary drive. Downtime for each server was under 5 minutes. The upgrade on wanote has been postponed until a later date.

[May 8, 2008, 2:11 AM] siyazi, wanote, kuwae, misilay, yiwen Planned Maintenance

siyazi (www251), wanote (www284), kuwae (www446), misilay (www282), and yiwen (www246) will be taken down shortly for drive upgrades. Downtime for each server should be less than 5 minutes. An additional notice will be posted when the upgrades have been completed.

[May 8, 2008, 12:01 AM] gwind Emergency Maintenance

gwind (www74) crashed while in service and was given a chassis swap. It is now an Intel Core2 6400 with 2GB of RAM. Downtime was less than 10 minutes.

[May 7, 2008, 3:47 PM] straif Downtime

straif (www26) experienced high load and was reset. Downtime was under 15 minutes.

[May 7, 2008, 2:09 PM] duwo Downtime

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

[May 7, 2008, 11:44 AM] straif Downtime

straif (www26) became unresponsive and was reset. Downtime was about 10 minutes.

[May 6, 2008, 11:50 PM] oynos, kirlian Downtime

oynos (www218) and kirlian (www110) both came under high load and needed to be rebooted. Downtime for each was less than 10 minutes.

[May 6, 2008, 11:29 PM] seyyav Downtime

seyyav (www238) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 6, 2008, 5:52 PM] fiann Downtime

fiann (www188) was taken down again to make a configuration change to the ShadowDrive. The server also required a manual file check. Total downtime was 10 minutes.

[May 6, 2008, 4:48 PM] fiann Maintenance Completed

The chassis swap in fiann (www188) has been completed. It is now a Core2 E4500 with 1GB of RAM. Total downtime was 15 minutes.

[May 6, 2008, 4:12 PM] fiann Emergency Maintenance

fiann (www188) will be taken down shortly to perform a chassis swap. An additional notice will be posted when this is complete.

[May 6, 2008, 2:19 PM] fiann Downtime

fiann (www188) became unresponsive while in service and required a manual file-system check before being brought back online. Downtime was 15 minutes.

[May 6, 2008, 1:46 PM] straif Downtime

straif (www26) became unresponsive while in service and required a manual file-system check before being brought back online. Downtime was 20 minutes.

[May 6, 2008, 8:40 AM] fiann Downtime

fiann (www188) encountered an error and reset. Downtime was less than 5 minutes.

[May 6, 2008, 5:27 AM] lliamna, fiann, nyartu Maintenance Completed

Tonight's maintenance has been completed. lliamna (www358) now has a 160GB primary drive, and fiann (www188) was given a new ShadowDrive. Additionally, nyartu (www254) had it's primary drive cable swapped. Downtime for each server was under 5 minutes.

[May 6, 2008, 4:28 AM] lliamna, fiann, nyartu Planned Maintenance

lliamna (www358) will be taken down shortly for a drive upgrade. fiann (www188) will be taken down for a ShadowDrive upgrade, and nyartu (www254) will be taken down to have the primary drive cable swapped. Downtime for each server should be less than 5 minutes. An additional notice will be posted when this has been completed.

[May 5, 2008, 4:47 AM] zhiri Downtime

zhiri (www290) became unresponsive and was reset. Downtime was about 10 minutes.

[May 5, 2008, 1:36 AM] ohayou Downtime

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

[May 4, 2008, 7:58 PM] namt Downtime

namt (www196) became unresponsive and was rebooted. Downtime was 5 minutes.

[May 4, 2008, 10:05 AM] gwind Downtime

[May 4, 2008, 6:42 AM] paell Downtime

paell (www153) encountered an error and reset. Downtime was about 10 minutes.

[May 4, 2008, 5:20 AM] douzo Downtime

douzo (www332) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 2, 2008, 3:16 PM] duwo Downtime

duwo (www219) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 2, 2008, 12:05 PM] canlaon Downtime

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

[May 2, 2008, 11:33 AM] tiwaz Downtime

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

[May 2, 2008, 5:57 AM] hyaku Maintenance Completed

The drive swap on hyaku (www345) has been completed. It now has a 160GB primary drive. Downtime was about 5 minutes.

[May 2, 2008, 5:09 AM] hyaku Emergency Maintenance

hyaku (www345) will be taken down shortly to swap out a failing drive. Downtime should be less than 5 minutes. An additional notice will be posted when this has been completed.

[May 2, 2008, 1:45 AM] paell Downtime

paell (www153) encountered an error and reset. Downtime was about 10 minutes.

[May 1, 2008, 2:05 PM] kesa Maintenance Completed

The drive swap for kesa (www479) has now been completed. Downtime was approximately 10 minutes.

[May 1, 2008, 10:29 AM] kesa Emergency Maintenance

kesa (www479) will be taken down shortly to replace the primary drive. Downtime is expected to be under 10 minutes. An additional notice will be posted once the maintenance has been completed.

[May 1, 2008, 3:07 AM] sariga Emergency Maintenance

sariga (www420) will be taken down shortly to swap out a failing ShadowDrive. Total downtime should be less than 5 minutes.

[Apr 30, 2008, 5:06 PM] klesh Downtime

klesh (www200) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Apr 30, 2008, 11:13 AM] guguun Downtime

guguun (www419) became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 30, 2008, 6:45 AM] iruvul Downtime

iruvul (www239) encountered an error and was reset. Downtime was approximately 5 minutes.

[Apr 30, 2008, 4:00 AM] sitkin Maintenance Completed

The chassis upgrade on sitkin (www373) has been completed. It is now an Intel Core 2 6400 with 2GB of RAM. Total downtime was under 10 minutes.

[Apr 30, 2008, 3:28 AM] zortzi Downtime

zortzi (www243) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 30, 2008, 3:21 AM] sitkin Planned Maintenance

sitkin (www373) will be taken down shortly for a chassis upgrade. Downtime should be less than 10 minutes. An additional notice will be posted when the upgrade has been completed.

[Apr 29, 2008, 4:30 PM] kohala Downtime

kohala (www389) experienced high load and required a reset. Downtime was approximately 5 minutes.

[Apr 29, 2008, 3:42 PM] gebo Downtime

gebo (www139) became unresponsive while in service and required a manual file system check before being brought back online. Downtime was 15 minutes.

[Apr 29, 2008, 5:54 AM] sitkin, gamsi Maintenance Completed

Tonight's maintenance on gamsi (www289) has been completed. It is now an Intel Core2 6400 with 2GB of RAM. Downtime was about 10 minutes. The chassis upgrade for sitkin (www373) has been postponed to a later date this week.

[Apr 29, 2008, 2:20 AM] sitkin, gamsi Planned Maintenance

sitkin (www373) and gamsi (www289) will be taken down shortly for chassis upgrades. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Apr 28, 2008, 5:04 PM] otaku Downtime

otaku (www338) became unresponsive and was rebooted. Downtime was 10 minutes.

[Apr 28, 2008, 3:52 PM] mirozo Downtime

mirozo (www257) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Apr 28, 2008, 3:46 PM] arda Downtime

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

[Apr 28, 2008, 8:00 AM] gamsi Downtime

gamsi (www289) encountered an error and was reset. Downtime was under 10 minutes.

[Apr 28, 2008, 2:46 AM] sether Downtime

sether (www95) encountered an error and was reset. Downtime was under 10 minutes.

[Apr 27, 2008, 6:55 PM] neled Downtime

neled (www127) encountered high load and was reset. Downtime was under 5 minutes.

[Apr 27, 2008, 6:31 PM] gamsi Downtime

gamsi (www289) encountered an error and was reset. Downtime was under 10 minutes.

[Apr 27, 2008, 11:55 AM] kishou Downtime

The server kishou(www335) crashed and required a manual file system check. The total downtime for this server was approximately 15 minutes.

[Apr 27, 2008, 9:24 AM] khin Downtime

khin (www184) became unresponsive under high load and was reset. Downtime was less then 10 minutes.

[Apr 27, 2008, 8:23 AM] khin Downtime

khin (www184) became unresponsive under high load and was reset. Downtime was 10 minutes.

[Apr 26, 2008, 8:37 PM] oshima Downtime

oshima (www416) crashed and was rebooted. Downtime was under 5 minutes.

[Apr 26, 2008, 3:36 PM] irazu Emergency Maintenance

irazu (www377) crashed during service and was given a chassis swap. It is now an Intel Core2 6400 with 2GB RAM. Downtime was about 15 minutes.

[Apr 26, 2008, 12:11 AM] nyartu Maintenance Completed

The maintenance on nyartu has been completed. It is now an Intel Core2 6400 with 2GB RAM. The primary hard drive has also been upgraded to 120GB. Downtime was about 35 minutes.

[Apr 25, 2008, 9:51 PM] nyartu Planned Maintenance

nyartu (www254) will be going down shortly to perform a chassis swap. A notice will be posted once the maintenance is completed.

[Apr 25, 2008, 2:06 PM] aerre Downtime

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

[Apr 25, 2008, 1:41 PM] ocha Downtime

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

[Apr 25, 2008, 11:02 AM] eena Downtime

eena (www463) became unresponsive under high load and was rebooted. Total downtime was less than 15 minutes.

[Apr 25, 2008, 10:38 AM] irazu Downtime

irazu (www377) became unresponsive while in service and was rebooted. Total downtime was about 5 minutes.

[Apr 25, 2008, 9:50 AM] Network Problems Resolved

The Global Crossing fiber cut reported yesterday was repaired at about 10:00 PM Eastern that evening. We've been monitoring the line since for further signs of trouble, but it has remained stable.

[Apr 25, 2008, 8:34 AM] gamsi Downtime

gamsi (www289) became unresponsive while in service and was rebooted. Total downtime was 10 minutes.

[Apr 25, 2008, 4:15 AM] ansuz Planned Maintenance

ansuz (www137) will be taken down shortly to replace a failing shadow drive. Downtime should be less than 10 minutes.

[Apr 25, 2008, 1:27 AM] iruvul Downtime

iruvul (www239) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 24, 2008, 11:09 PM] paell Downtime

paell (www153) crashed and was rebooted. Downtime was under 5 minutes.

[Apr 24, 2008, 5:52 PM] Network Problems

We've been advised by our vendor that Global Crossing is currently working to repair a fiber cut between Michigan and Indiana which has caused problems throughout their network. There is currently no estimated time to restoration, but we're told that work is in progress.

We've also received reports from some customers that the delays they were seeing have been resolved, which may stem from other measures Global Crossing has taken during this outage.

[Apr 24, 2008, 3:47 PM] vedra Downtime

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

[Apr 24, 2008, 3:22 PM] Network Problems

Beginning around 2:00 PM Eastern, we have been receiving reports of increased latency for some customers who reach us through our Global Crossing gigabit circuit.

We have not observed a loss of overall traffic except for a short-lived drop in Global Crossing traffic at the beginning of the event. However, some people reaching our network via Global Crossing may experience slower network speeds or time outs.

We are currently awaiting a diagnosis and a time to resolution from our vendors. More information will be posted as it is available.

[Apr 24, 2008, 3:25 AM] aveu Downtime

aveu (www192) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 23, 2008, 10:52 PM] oynos Emergency Maintenance

oynos (www218) crashed while in service and was given a chassis swap. It is now and Intel Core2 6400 with 2GB RAM. Downtime was about 15 minutes.

[Apr 23, 2008, 2:24 AM] oshima Downtime

oshima (www416) encountered a high load and was reset. Downtime was about 10 minutes.

[Apr 22, 2008, 3:56 PM] oynos Downtime

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

[Apr 21, 2008, 3:29 PM] irazu Downtime

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

[Apr 20, 2008, 3:47 AM] parma Downtime

parma (www42) encountered an error while in service and had to be rebooted. Downtime was less than 5 minutes.

[Apr 19, 2008, 11:06 PM] omsano Emergency Maintenance

omsano (www164) crashed while in service and was given a chassis swap. It is now and Intel Core2 6400 with 2GB RAM. Downtime was about 15 minutes.

[Apr 19, 2008, 6:27 PM] vroo Downtime

vroo (www125) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 19, 2008, 4:10 PM] berkano Downtime

berkano (www147) became unresponsive while in service and was rebooted. Total downtime was approximately 10 minutes.

[Apr 18, 2008, 10:40 PM] omsano Downtime

omsano (www164) encountered an error and was reset. Downtime was less than 5 minutes.

[Apr 18, 2008, 2:53 PM] ansuz Downtime

ansuz (www137) became unresponsive while in servers and required a manual file system check. Downtime was 20 minutes.

[Apr 18, 2008, 11:38 AM] peulik Downtime

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

[Apr 17, 2008, 7:16 PM] quesse Downtime

quesse (www44) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Apr 17, 2008, 6:44 PM] uumor Downtime

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

[Apr 17, 2008, 3:36 AM] virre Emergency Maintenance

virre (www193) will be taken down shortly to swap out a failing shadow drive. Downtime should be less than 5 minutes.

[Apr 16, 2008, 1:13 AM] thenge Downtime

thenge (www270) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 15, 2008, 9:52 PM] kanat Downtime

kanat (www128) became unresponsive and was rebooted. Downtime was 5 minutes.

[Apr 15, 2008, 1:49 PM] tehun Downtime

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

[Apr 15, 2008, 10:17 AM] kanat Downtime

The server kanat(www128) crashed due to a high load and was rebooted. The total downtime for this server was under 10 minutes.

[Apr 14, 2008, 2:21 PM] tehun Downtime

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

[Apr 14, 2008, 5:11 AM] murifwae Emergency Maintenance

murifwae (www279) crashed while in service and was given a chassis swap. It is now an Intel Core2 6400 with 2GB RAM. Total downtime was approximately 30 minutes.

[Apr 14, 2008, 4:40 AM] murifwae Downtime

murifwae (www279) became unresponsive and required a reboot. Downtime was less than 10 minutes.

[Apr 14, 2008, 2:46 AM] irazu Downtime

irazu(www377) encountered an error and required to be reset. Downtime was less than 15 minutes.

[Apr 13, 2008, 6:03 PM] gyaku Downtime

gyaku (www351) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 12, 2008, 9:36 PM] auddo Downtime

auddo (www253) was rebooted to clear an error condition. Downtime was under 5 minutes.

[Apr 12, 2008, 3:36 PM] vuae Downtime

vuae (www93) became unresponsive while in service and needed to be rebooted. Total downtime was 15 minutes.

[Apr 11, 2008, 8:55 AM] niwun Downtime and RAM Upgrade

niwun (www225) became unresponsive under load and was rebooted. While the server was down, 1GB of RAM was added to it for a total of 2GB. Total downtime was less than 20 minutes.

[Apr 11, 2008, 7:33 AM] iruvul Downtime

iruvul (www239) became unresponsive and required a reboot. Downtime was less than 10 minutes.

[Apr 10, 2008, 10:05 AM] djole Downtime

djole (www314) became unresponsive due to high load and was rebooted. We are monitoring this server very closely. Total downtime was less than 10 minutes.

[Apr 10, 2008, 8:30 AM] djole Downtime

djole (www314) became unresponsive under high load and was rebooted. Total downtime was less than 15 minutes.

[Apr 10, 2008, 7:39 AM] djole Downtime

djole (www314) was taken down to replace a failing drive cable. Downtime was less than 15 minutes.

[Apr 10, 2008, 5:27 AM] suoh Maintenance Completed

The drive swap on suoh has been completed. It now has a new 120G primary drive. Downtime was about 5 minutes.

[Apr 10, 2008, 5:24 AM] roomen Downtime

roomen (www61) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Apr 10, 2008, 5:00 AM] auddo Downtime

auddo (www253) became unresponsive and had to be rebooted. Downtime was less than 5 minutes.

[Apr 10, 2008, 4:43 AM] suoh Emergency Maintenance

suoh (www396) will be taken down shortly to replace a failing drive. Downtime should be about 5 minutes. An additional notice will be posted when this has been completed.

[Apr 9, 2008, 3:33 PM] iruvul Downtime

iruvul (www239) encountered an error and was reset. Downtime was under 10 minutes.

[Apr 9, 2008, 3:39 AM] dsumaui Downtime

dsumaui (www275) encountered an error and reset. Downtime was less than 10 minutes.

[Apr 9, 2008, 2:47 AM] merau Downtime

merau(www245) encountered an error and reset. Downtime was less than 10 minutes.

[Apr 8, 2008, 8:56 PM] tehun Downtime

tehun (www226) encountered an error and was rebooted. Downtime was 5 minutes.

[Apr 8, 2008, 8:29 PM] wawrra Downtime

wawrra (www109) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Apr 8, 2008, 7:20 PM] savo Downtime

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

[Apr 8, 2008, 5:02 PM] tehun Downtime

tehun (www226) encountered high load and was reset. Downtime was under 10 minutes.

[Apr 8, 2008, 3:42 AM] talang Emergency Maintenance

talang (www391) will be taken down shortly to swap out a failing shadow drive. Downtime should be less than 10 minutes.

[Apr 7, 2008, 9:35 PM] talang Downtime

talang (www391) encountered an error and was rebooted. Downtime was less than 10 minutes.

[Apr 7, 2008, 3:49 PM] flure Downtime

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

[Apr 7, 2008, 2:13 PM] flure Downtime

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

[Apr 7, 2008, 12:58 AM] gessire Emergency Maintenance

gessire (www273) crashed while in service and was given a chassis swap. It is now an Intel Core2 E4500 with 1GB RAM and a 160GB primary drive. Total downtime was 30 minutes.

[Apr 6, 2008, 11:25 PM] tehun Downtime

tehun (www226) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Apr 6, 2008, 11:06 PM] gamsi Downtime

gamsi (www289) became unresponsive and was rebooted. Downtime was 5 minutes.

[Apr 6, 2008, 9:37 PM] fayev Downtime

fayev (www365) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Apr 6, 2008, 8:23 PM] gessire Downtime

gessire (www273) encountered an error and was rebooted. Downtime was 5 minutes.

[Apr 5, 2008, 4:54 AM] talang Emergency Maintenance

talang (www391) was taken down to replace a failing drive cable. Downtime was less than 15 minutes.

[Apr 3, 2008, 6:15 PM] gao Downtime

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

[Apr 3, 2008, 10:23 AM] hachi Downtime

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

[Apr 3, 2008, 7:41 AM] jera Downtime

jera (www142) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Apr 3, 2008, 5:38 AM] korovin, auua, dukoni, roomen, izalc, talang Maintenance Completed

Tonight's maintenance has been completed. korovin, auua, and roomen now have 160G drives, and dukoni and izalc now have 120G drives. Additionally, talang was given a new ShadowDrive. Downtime for each server was under 10 minutes.

[Apr 3, 2008, 2:57 AM] korovin, auua, dukoni, roomen, izalc, talang Planned Maintenance

korovin (www371), auua (www458), dukoni (www305), roomen (www61), and izalc (www378) will be taken down shortly for drive upgrades. talang (www391) will be taken down for a ShadowDrive upgrade. Downtime for each server should be less than 10 minutes. An additional notice will be posted when the upgrades are complete.

[Apr 2, 2008, 10:31 PM] flunn Downtime

flunn (www123) encountered high load and was reset. Downtime was under 10 minutes.

[Apr 2, 2008, 9:18 AM] terfideu Downtime

terfideu (www271) became unresponsive under high load and needed to be rebooted. Total downtime was about 15 minutes.

[Apr 2, 2008, 7:22 AM] terfideu Downtime

terfideu(www271) encountered an error and required a reboot. Downtime was less than 15 minutes.

[Apr 2, 2008, 2:20 AM] sitkin Maintenance Completed

The ShadowDrive swap for sitkin (www373) has been completed. Downtime was less than 10 minutes.

[Apr 2, 2008, 1:53 AM] sitkin Emergency Maintenance

sitkin (www373) will be taken down shortly to swap a failing ShadowDrive. Downtime should be less than 5 minutes. An additional notice will be posted when the maintenance has been completed.

[Apr 2, 2008, 12:07 AM] savo Downtime

savo(www436) encountered an error and required a reboot. Downtime was less than 10 minutes.

[Apr 1, 2008, 4:48 PM] flunn Downtime

flunn (www123) encountered high load and was reset. Downtime was under 10 minutes.

[Apr 1, 2008, 4:26 PM] savo Downtime

savo (www436) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Apr 1, 2008, 6:13 AM] petora Downtime

petora(www229) encountered an error and required a reset. Downtime was less then 15 minutes.

[Apr 1, 2008, 3:05 AM] petora Downtime

petora (www229) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 31, 2008, 6:45 PM] berkano Downtime

berkano (www147) encountered high load and was reset. Downtime was under 15 minutes.

[Mar 31, 2008, 4:23 PM] parma Downtime

parma (www42) encountered high load and required a reset. Downtime was under 10 minutes.

[Mar 31, 2008, 8:24 AM] siyazi Downtime

siyazi(www251) encountered an error and required a reboot. Downtime was less than 20 minutes.

[Mar 31, 2008, 8:24 AM] qaske Downtime

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

[Mar 31, 2008, 7:31 AM] siyazi Downtime

siyazi(www251) encountered an error and was reset. Downtime was less then 15 minutes.

[Mar 30, 2008, 11:30 PM] petora Downtime

petora (www229) became unresponsive and was rebooted. Downtime was 5 minutes.

[Mar 30, 2008, 4:38 PM] tinne Downtime

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

[Mar 30, 2008, 2:22 PM] petora Downtime

petora (www229) became unresponsive under high load and was reset. Downtime was 10 minutes.

[Mar 30, 2008, 3:54 AM] erraj Downtime

erraj(www213) encountered an error and required a reboot. Downtime was less than 10 minutes.

[Mar 29, 2008, 8:18 PM] isris Downtime

isris (www194) crashed under high load and was rebooted. Downtime was under 5 minutes.

[Mar 29, 2008, 9:16 AM] fayev Downtime

fayev (www365) became unresponsive under high load and needed to be rebooted. Downtime was 15 minutes.

[Mar 29, 2008, 3:24 AM] ocha Maintenance Completed

The ShadowDrive swap on ocha (www355) has been completed. Downtime was about 5 minutes.

[Mar 29, 2008, 2:45 AM] ocha Emergency Maintenance

ocha (www355) will be going down shortly to replace a failing ShadowDrive. An additional notice will be posted once the maintenance is complete.

[Mar 29, 2008, 2:06 AM] vroo Emergency Maintenance

The drive swap on vroo (www125) has been completed. vroo has a new 250GB primary hard drive. Downtime was less than 10 minutes.

[Mar 29, 2008, 1:20 AM] vroo Emergency Maintenance

vroo (www125) will be taken down shortly to replace the primary hard drive. Downtime is expected to be under 10 minutes. An additional notice will be posted once the maintenance has been completed.

[Mar 28, 2008, 8:49 PM] ocha Maintenance Completed

The drive swap on ocha (www355) has been completed. ocha now has a 120GB primary drive. Downtime was about 5 minutes.

[Mar 28, 2008, 8:11 PM] ocha Emergency Maintenance

ocha (www355) will be taken down shortly to replace the primary hard drive. Downtime is expected to be under 10 minutes. An additional notice will be posted once the maintenance has been completed.

[Mar 28, 2008, 5:29 PM] bhoth Downtime

bhoth (www163) crashed while in service and was rebooted. Downtime was under 10 minutes.

[Mar 28, 2008, 4:09 PM] paell Downtime

paell (153) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 28, 2008, 2:50 PM] namt Downtime

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

[Mar 28, 2008, 1:55 PM] nallav Downtime

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

[Mar 28, 2008, 11:27 AM] soputan Downtime

soputan (www408) became unresponsive under high load and needed to be rebooted. Total downtime was 15 minutes.

[Mar 28, 2008, 4:25 AM] vroo Emergency Maintenance

vroo (www125) was taken down to swap a failing drive cable. Downtime was less than 5 minutes.

[Mar 27, 2008, 10:41 PM] ocha Maintenance Completed

The ShadowDrive swap for ocha (www355) has been completed. Downtime was about 5 minutes.

[Mar 27, 2008, 10:30 PM] peulik Downtime

peulik (www360) froze while in service and was rebooted. Downtime was under 5 minutes. We are monitoring this server closely.

[Mar 27, 2008, 10:23 PM] ocha Emergency Maintenance

ocha (www355) will be going down shortly to replace the ShadowDrive. An additional notice will be posted once the maintenance is complete.

[Mar 27, 2008, 9:59 PM] sariga Downtime

sariga (www420) crashed and rebooted. Downtime was under 5 minutes.

[Mar 27, 2008, 5:23 PM] okkod Downtime

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

[Mar 27, 2008, 5:08 PM] peulik Downtime

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

[Mar 26, 2008, 5:01 PM] bhoth Downtime

bhoth (www163) encountered an error and was reset. Downtime was under 10 minutes.

[Mar 26, 2008, 3:09 PM] iski Downtime

iski (www242) encountered an error and was reset. Downtime was under five minutes.

[Mar 26, 2008, 1:44 PM] thesel Downtime

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

[Mar 26, 2008, 3:15 AM] beeoro Downtime

beeoro (www69) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 25, 2008, 10:20 PM] paell Downtime

paell (www153) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Mar 25, 2008, 2:44 PM] douzo Downtime

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

[Mar 25, 2008, 4:30 AM] kanat Downtime

kanat (www128) encountered an error and was rebooted. Downtime was about 5 minutes.

[Mar 25, 2008, 1:45 AM] ulwar Emergency Maintenance

The drive swap for ulwar is complete. ulwar now has a 160GB primary drive and a 250GB shadow drive. Downtime was about 10 minutes.

[Mar 25, 2008, 12:39 AM] ulwar Emergency Maintenance

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

[Mar 24, 2008, 11:47 PM] huath Downtime

huath (www19) encountered an error and was rebooted. Downtime was about 5 minutes.

[Mar 24, 2008, 4:39 PM] gao Downtime

gao (www111) became unresponsive while in service and had to be rebooted. Downtime was about 15 minutes.

[Mar 24, 2008, 9:56 AM] nuin Downtime

nuin(www18) encountered an error and required a reboot. Downtime was less than 10 minutes.

[Mar 24, 2008, 9:55 AM] oynos Downtime

oynos(www218) encountered an error and required a reboot. Downtime was less than 10 minutes.

[Mar 23, 2008, 8:56 AM] gamsi Downtime

gamsi (www289) encountered an error and was reset. Downtime was 10 minutes.

[Mar 23, 2008, 3:52 AM] tiwaz Downtime

tiwaz (www146) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 22, 2008, 6:16 PM] erraj Downtime

erraj (www213) crashed while in service and was reset. Downtime was under 5 minutes.

[Mar 22, 2008, 5:14 PM] tuzuba Downtime

tuzuba (www256) crashed and was rebooted. Downtime was under 5 minutes.

[Mar 22, 2008, 4:08 PM] kanat Downtime

kanat (www128) crashed while in service and was rebooted. Downtime was under 10 minutes.

[Mar 22, 2008, 10:44 AM] ghiq Downtime

ghiq (www324) encountered an error and was reset. Downtime was under 10 minutes.

[Mar 22, 2008, 10:26 AM] erraj Downtime

erraj (www213) was reset while in service. Downtime was 5 minutes.

[Mar 21, 2008, 2:35 PM] upsilon Downtime

upsilon (www13) became unresponsive and was rebooted. Downtime was approximately 10 minutes.

[Mar 21, 2008, 12:12 PM] psi Downtime

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

[Mar 21, 2008, 12:00 PM] wawrra Downtime

wawrra (www109) became unresponsive while in service and required a reboot. Downtime was under 10 minutes.

[Mar 21, 2008, 10:39 AM] cuzea Downtime

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

[Mar 21, 2008, 2:52 AM] ando Downtime

ando (www45) crashed under heavy load and had to be rebooted. Downtime was under 10 minutes.

[Mar 20, 2008, 6:02 PM] cuzea Downtime

cuzea (www94) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 20, 2008, 3:03 PM] ipre Downtime

ipre (www181) encountered an error and was reset. Downtime was 5 minutes.

[Mar 20, 2008, 2:58 PM] psi Downtime

psi (www15) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 20, 2008, 1:15 PM] tama Downtime

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

[Mar 20, 2008, 2:11 AM] erraj Downtime

erraj(www213) encountered an error and was reset. Downtime was less than 20 minutes.

[Mar 19, 2008, 10:56 PM] tiwaz Downtime

tiwaz (www146) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Mar 19, 2008, 10:17 PM] patru Downtime

patru (www232) encountered an error and was reset. Downtime was less than 10 minutes.

[Mar 19, 2008, 4:55 PM] gwind Downtime

gwind (www74) encountered high load and was reset. Downtime was under 10 minutes.

[Mar 19, 2008, 3:33 PM] aster Downtime

aster (www96) encountered an error and was reset. Downtime was under 5 minutes.

[Mar 19, 2008, 6:12 AM] lissa Downtime

lissa (www72) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Mar 18, 2008, 11:31 PM] lissa Downtime

lissa (www72) became unresponsive and was rebooted. Downtime was less than 10 minutes.

[Mar 18, 2008, 11:18 PM] sogbe Downtime

sogbe (www274) encountered an error and was rebooted. Downtime was 5 minutes.

[Mar 18, 2008, 7:19 PM] neled Downtime

neled (www127) experienced high load and was reset. Downtime was under 10 minutes.

[Mar 18, 2008, 1:00 PM] jaane Downtime

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

[Mar 18, 2008, 4:16 AM] vroo, sekweta Maintenance Completed

The drives swaps for vroo and sekweta are complete. vroo now has a 160GB drive. sekweta now has a 200GB drive. Downtime for each server was under 10 minutes.

[Mar 18, 2008, 1:57 AM] vroo, sekweta Emergency Maintenance

vroo (www125) and sekweta (www258) will be taken down shortly to swap out failing drives. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Mar 18, 2008, 1:42 AM] tuzuba Downtime

tuzuba (www256) encountered an error and was reset. Downtime was about 15 minutes.

[Mar 17, 2008, 8:35 PM] auma Downtime

auma (www86) encountered an error and was reset. Downtime was under 5 minutes.

[Mar 17, 2008, 8:11 PM] wokkil Downtime

wokkil (www249) became unresponsive and was rebooted. Downtime was 5 minutes.

[Mar 17, 2008, 3:37 PM] perthro Downtime

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

[Mar 17, 2008, 11:51 AM] zais Downtime

The server zais(www89) crashed due to a high load and was rebooted. The total downtime for this server was approximately 10 minutes.

[Mar 16, 2008, 3:09 PM] ittsui Downtime

ittsui (www323) became unresponsive under high load and needed to be rebooted. Down time was 10 minutes.

[Mar 16, 2008, 9:15 AM] sekweta Downtime

sekweta (www258) became unresponsive while in service and required a manual file system check. Downtime was 20 minutes.

[Mar 16, 2008, 7:23 AM] saghotta Emergency Maintenance

saghotta (www259) crashed while in service and was given a chassis swap. It is now an Intel Core2 6400 with 2GB RAM. Total downtime was approximately 30 minutes.

[Mar 16, 2008, 4:47 AM] saghotta Downtime

saghotta (www259) was rebooted to clear up an error condition. Downtime was about 25 minutes. We apologize for any inconvenience this may have caused.

[Mar 14, 2008, 11:37 PM] vash Downtime

vash (www368) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Mar 14, 2008, 6:32 PM] paell Downtime

paell (www153) encountered an error and was reset. Downtime was under 10 minutes.

[Mar 14, 2008, 5:37 PM] gamsi Downtime

gamsi (www289) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 14, 2008, 1:17 PM] chi Downtime

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

[Mar 14, 2008, 8:17 AM] lliamna Emergency Maintenance

lliamna (www358) became unresponsive and was given a chassis swap. It is now a Intel Core2 6400 with 2GB RAM. Total downtime was approximately 25 minutes.

[Mar 13, 2008, 11:07 PM] uruz Downtime

uruz (www135) crashed and required a manual file system check. Downtime was about 15 minutes.

[Mar 13, 2008, 12:48 PM] edad Emergency Maintenance

edad (www31) became unresponsive again and was promptly given a chassis swap. It is now a Pentium 4, 3.0GHz with 2GB of RAM. Total downtime was approximately 35 minutes. We apologize for any inconveniences this may have caused.

[Mar 13, 2008, 11:31 AM] edad Downtime

edad (www31) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 20 minutes.

[Mar 12, 2008, 7:45 PM] oynos, lliamna Downtime

oynos (www218) and lliamna (www358) both crashed and were rebooted. Downtime for each server was under 10 minutes.

[Mar 12, 2008, 3:21 PM] psi Downtime

psi (www15) became unresponsive and was rebooted. Downtime was 5 minutes.

[Mar 12, 2008, 3:11 PM] poict Downtime

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

[Mar 12, 2008, 11:17 AM] onn Downtime

onn (www29) became unresponsive and was reset. Downtime was about 10 minutes.

[Mar 12, 2008, 5:47 AM] gamsi Downtime

gamsi (www289) encountered an error and was reset. Downtime was less than 5 minutes.

[Mar 12, 2008, 4:55 AM] tiwaz Downtime

tiwaz (www146) encountered an error and was reset. Downtime was less than 10 minutes.

[Mar 12, 2008, 1:16 AM] sramet Maintenance Completed

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

[Mar 12, 2008, 12:36 AM] sramet Planned Maintenance

sramet (www399) will be taken down shortly for a drive upgrade. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[Mar 11, 2008, 11:08 PM] vepar Downtime

vepar (www201) encountered an error and rebooted itself. Downtime was 5 minutes.

[Mar 11, 2008, 8:35 PM] ceirt Downtime

ceirt (www39) became unresponsive and was rebooted. Downtime was 5 minutes.

[Mar 11, 2008, 6:59 PM] maborym Downtime

mayborym (www204) encountered high load and was reset. Downtime was under five minutes.

[Mar 11, 2008, 1:00 PM] dhaame Downtime

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

[Mar 11, 2008, 12:05 PM] tuzuba Downtime

The server tuzuba(www256) crashed due to a high load and was rebooted. The total downtime for this server was under 10 minutes.

[Mar 11, 2008, 4:55 AM] straif, hakone, sramet Maintenance Completed

The drive upgrades for straif, hakone, and sramet are complete. straif and hakone now have 160GB drives. A new shadow drive was installed into sramet, and it will receive a drive upgrade at a later time. Downtime for each server was about 5 minutes.

[Mar 11, 2008, 4:51 AM] kanat Downtime

kanat (www128) encountered an error and was reset. Downtime was less than 10 minutes.

[Mar 11, 2008, 4:22 AM] gamsi Downtime

gamsi(www289) encountered an error and reset. Downtime was less than 10 minutes.

[Mar 11, 2008, 12:32 AM] straif, hakone, sramet Planned Maintenance

straif (www26), hakone (www415), sramet (www399) will be taken down shortly for drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Mar 10, 2008, 11:00 PM] gamsi Downtime

gamsi (www289) became unresponsive and was rebooted. Downtime was 5 minutes.

[Mar 10, 2008, 3:46 PM] muin Downtime

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

[Mar 10, 2008, 2:35 PM] klesh Downtime

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

[Mar 10, 2008, 1:50 PM] kaarei Downtime

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

[Mar 10, 2008, 1:27 PM] djole Downtime

The server djole(www314) ran out of swap space and was rebooted. The total downtime from this server was under 10 minutes.

[Mar 10, 2008, 1:26 PM] athani Downtime

The server athani(www157) crashed due to a high load and was rebooted. The total downtime for this server was approximately 15 minutes.

[Mar 10, 2008, 10:40 AM] fearn Downtime

The server fearn(www40) crashed due to a high load and was rebooted. The total downtime of the server was approximately 10 minutes.

[Mar 10, 2008, 3:28 AM] gamsi Downtime

gamsi(www289) encountered an error and reset. Downtime was less than 10 minutes.

[Mar 9, 2008, 10:48 PM] ingwaz Downtime

ingwaz (www149) experienced an error and required a chassis swap. It is now a Core2 E6400 with 2GB of RAM. Downtime was less than 30 minutes.

[Mar 9, 2008, 8:17 AM] ur Downtime

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

[Mar 9, 2008, 12:54 AM] vilya Downtime

vilya (www60) encountered an error while in service and had to be rebooted. Downtime was about 15 minutes.

[Mar 8, 2008, 8:01 PM] klesh Downtime

klesh (www200) became unresponsive while in service and was reset. Downtime was less than 15 minutes.

[Mar 8, 2008, 5:04 PM] tyllur Downtime

tyllur (www285) became unresponsive while in service and was reset. The server required a manual file check after reboot. Downtime was about about 30 minutes.

[Mar 8, 2008, 1:25 PM] ingwaz Downtime

ingwaz (www149) ran out of swap space and needed to be rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was approximately 25 minutes.

[Mar 8, 2008, 12:56 PM] cele Downtime

cele (www73) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Mar 8, 2008, 11:22 AM] irazu Downtime

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

[Mar 8, 2008, 7:10 AM] iruvul Downtime

iruvul(www239) encountered an error and rebooted. Downtime was less than 20 minutes.

[Mar 7, 2008, 12:57 PM] beith Downtime

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

[Mar 7, 2008, 6:04 AM] egmont, bunepi, sali Maintenance Completed

The drive upgrades for egmont, bunepi, and sali is complete. egmont and sali now have 160GB drives. A problem was discovered with the bunepi chassis during the upgrade. In addition to the drive upgrade it also received a chassis swap. It is now a Core2 E6400 with 2GB of RAM and a 120GB drive. Downtime for bunepi was about 25 minutes. Downtime for egmont and sali was about 5 minutes.

[Mar 7, 2008, 2:12 AM] egmont, bunepi, sali Planned Maintenance

egmont (www449), bunepi (www318), and sali (www454) will be taken down shortly for drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Mar 6, 2008, 11:24 PM] Network Problems Resolved

The repairs on our HE.net gigabit circuit have been completed, and the circuit returned to normal service at approximately 9:30 PM Eastern. Throughout the outage, traffic flowed normally over our other providers.

[Mar 6, 2008, 9:21 PM] flaid Downtime

flaid (www91) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 6, 2008, 8:48 PM] Network Maintenance

We have been advised by our network carrier that maintenance to repair the damage in Cleveland, which is affecting our HE.net GigE circuit, began around 7:30pm Eastern time. Because of the seriousness of the damage, we still do not have a good estimate of how long repairs will take. In the meantime, we continue to have plenty of spare capacity and customer traffic should not be affected.

[Mar 6, 2008, 12:18 PM] Network Problems

We've received word that o