[Aug 24, 2008, 11:31 PM] enso Maintenance Completed
The shadow drive swap for enso is complete. Downtime was less than 10 minutes.

[Aug 24, 2008, 10:31 PM] enso Planned Maintenance

enso (www152) will be taken down shortly to replace a failing shadow drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Aug 24, 2008, 12:26 PM] ijen Downtime

ijen (www404) experienced high load and became unresponsive, requiring a reset. Downtime was under 10 minutes. We will continue monitoring this server.

[Aug 24, 2008, 5:18 AM] ijen Downtime

ijen (www404) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 24, 2008, 2:49 AM] ijen Downtime

ijen (www404) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 23, 2008, 3:24 PM] bganat Downtime

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

[Aug 23, 2008, 9:55 AM] anga Downtime

anga (www47) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 23, 2008, 9:52 AM] wawrra Maintenance Completed

wawrra (www109) is now a Pentium 4 3.00GHz with 3.5GB of RAM. Total downtime was about 25 minutes.

[Aug 23, 2008, 9:18 AM] wawrra Emergency Maintenance

wawrra (www109) is showing signs of an imminent hardware failure, so it will be taken down immediately for a chassis swap. An additional notice will be posted when the maintenance has been completed.

[Aug 23, 2008, 8:36 AM] wawrra Downtime

wawrra (www109) became unresponsive while in server and was reset. Downtime was 5 minutes.

[Aug 23, 2008, 8:33 AM] aveu Downtime

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

[Aug 23, 2008, 7:35 AM] aveu Downtime

aveu (www192) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 23, 2008, 6:56 AM] jera Downtime

jera (www142) became unresponsive while in service and had to be rebooted. Downtime was about 5 minutes.

[Aug 22, 2008, 11:16 PM] eeoth Downtime

eeoth (www85) was reset to clear an error condition. Downtime was less than 5 minutes.

[Aug 22, 2008, 3:57 PM] neko Downtime

neko (www356) became unresponsive while under high load and was reset. Downtime was 10 minutes.

[Aug 22, 2008, 8:12 AM] nezumi Downtime

nezumi (www337) encountered an error and was reset. Total downtime was about 5 minutes.

[Aug 22, 2008, 2:53 AM] taatu, sama Maintenance Completed

The drive upgrades for taatu and sama are complete. taatu now has a 120GB drive. sama now has a 160GB drive. Downtime for each server was about 5 minutes.

[Aug 22, 2008, 1:46 AM] taatu, sama Planned Maintenance

taatu (www165) and sama (www340) 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.

[Aug 21, 2008, 8:17 AM] kappa Downtime

kappa (www6) became unresponsive and was rebooted. Downtime was 10 minutes.

[Aug 21, 2008, 1:44 AM] zhun Downtime

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

[Aug 21, 2008, 1:04 AM] talang Maintenance Completed

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

[Aug 21, 2008, 12:46 AM] talang Emergency Maintenance

talang (www391) 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.

[Aug 20, 2008, 6:15 PM] enso Emergency Maintenance

enso (www152) experienced a primary drive failure and was swapped to the shadow drive. The primary drive is now 200GB. Downtime was about 30 minutes.

[Aug 20, 2008, 10:56 AM] gozaimasu Emergency Maintenance

gozaimasu (www486) had a primary drive failure and was swapped to the ShadowDrive. Downtime was about 30 minutes. Both primary and Shadow drives are now 250GB.

[Aug 20, 2008, 10:06 AM] yanta Downtime

yanta (www67) experienced high load, was reset, and required a manual disk check. Downtime was under 20 minutes.

[Aug 20, 2008, 8:40 AM] lambe Downtime

lambe (www63) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 19, 2008, 3:11 PM] uusu Emergency Maintenance

The drive swap on uusu (www412) has been completed. The primary drive is now 160G. Downtime was under 10 minutes.

[Aug 19, 2008, 11:59 AM] uusu Emergency Maintenance

uusu (www412) will be taken down shortly to perform a drive swap. A second notice will be posted once the maintenance is complete.

[Aug 19, 2008, 4:53 AM] itonami Downtime

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

[Aug 18, 2008, 10:37 PM] wanote, vilya Maintenance Completed

The shadow drive swaps for wanote and vilya are complete. Downtime for each was less than 10 minutes.

[Aug 18, 2008, 10:04 PM] wanote, vilya Planned Maintenance

wanote (www284) and vilya (www60) will be taken down shortly to replace failing shadow drives. Downtime for each should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Aug 18, 2008, 8:10 PM] kanat Downtime

kanat (www128) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Aug 18, 2008, 12:59 PM] karkar Downtime

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

[Aug 18, 2008, 5:45 AM] paat Downtime

paat (www100) became unresponsive and was rebooted. Downtime was 10 minutes.

[Aug 17, 2008, 5:56 PM] sowilu Downtime

sowilu (www145) became unresponsive and was rebooted. Downtime was 10 minutes.

[Aug 16, 2008, 5:06 PM] kanat Downtime

kanat (www128) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 15, 2008, 9:03 PM] Network Problems Resolved

Global Crossing has acknowledged a problem with a router in Los Angeles and has routed traffic around it. Traffic through that location has returned to normal.

[Aug 15, 2008, 8:05 PM] wanote Downtime

wanote (www284) was reset to clear an error condition. Downtime was less than 5 minutes.

[Aug 15, 2008, 5:42 PM] Network Problems

We are currently seeing packet loss on some traffic passing through our Global Crossing circuit, possibly centering on routes that pass through Los Angeles, CA. We have opened a ticket with our vendor and are currently awaiting an explanation of the problem and an estimated time to resolution.

[Aug 15, 2008, 11:36 AM] Database Server Upgrade Announcement

We have announced a plan to upgrade shared database servers running MySQL 4.1.x to the MySQL 5.0.x series. Details are available at:

http://www.pair.com/support/notices/dbupgrades.html

MySQL 5.0.x has been running on database servers db107.pair.com and up since they were brought online.

[Aug 15, 2008, 10:01 AM] kappa Downtime

kappa (www6) became unresponsive while in service and needed to be rebooted. Total downtime was about 15 minutes.

[Aug 15, 2008, 4:30 AM] wanote, okkod, ocha, ciot Maintenance Completed

Today's upgrades are complete. wanote is now a P4 3.4 with 2GB of RAM. okkod, ocha, and ciot are now P4 3.0's with 2GB of RAM. Downtime for each server was under 10 minutes.

[Aug 15, 2008, 4:07 AM] kappa Downtime

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

[Aug 15, 2008, 2:48 AM] wanote, okkod, ocha, ciot Planned Maintenance

wanote (www284), okkod (www235), ocha (www355), and ciot (www161) will be taken down shortly for chassis upgrades. Downtime for each server should be about 10 minutes. An additional notice will be posted when the upgrades are complete.

[Aug 15, 2008, 1:47 AM] lepen Maintenance Completed

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

[Aug 15, 2008, 1:11 AM] lepen Emergency Maintenance

lepen (www129) 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.

[Aug 14, 2008, 2:45 PM] itonami Downtime

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

[Aug 14, 2008, 10:50 AM] kappa Downtime

kappa (www6) became unresponsive under high load and needed to be rebooted. Total downtime was less than 15 minutes.

[Aug 14, 2008, 6:39 AM] mokpa, thesel, nallav, zais Maintenance Completed

Today's upgrades are complete. mokpa now has a 200GB drive. thesel, nallav, and zais now have 200GB drives. Downtime for each server was about 5 minutes.

[Aug 14, 2008, 3:52 AM] kappa Downtime

kappa (www6) crashed while in service and had to be rebooted. Downtime was about 5 minutes.

[Aug 14, 2008, 12:48 AM] mokpa, thesel, nallav, zais Planned Maintenance

mokpa (www303), thesel (www99), nallav (www237), and zais (www89) 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.

[Aug 13, 2008, 10:19 AM] tisibo Downtime

tisibo (www265) crashed due to high load and was reset. Downtime was under 10 minutes.

[Aug 13, 2008, 8:21 AM] yotoy Downtime

yotoy (www461) experienced high load and was reset. Downtime was under 15 minutes.

[Aug 13, 2008, 7:15 AM] thenge Downtime

thenge (www270) became unresponsive while in service and required a reboot. Downtime was less than 10 minutes.

[Aug 13, 2008, 3:18 AM] eiga, fimfi, tyungwa, taatu Maintenance Completed

Today's upgrades are complete. eiga now has a 120GB drive. fimfi and tyungwa now have 160GB drives. A new shadow drive has been installed in taatu. Downtime for each server was about 5 minutes.

[Aug 13, 2008, 12:36 AM] eiga, fimfi, tyungwa, taatu Planned Maintenance

eiga (www326), fimfi (www223), and tyungwa (www311) will be taken down shortly for drive upgrades. taatu (www165) 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.

[Aug 12, 2008, 5:01 PM] manam Downtime

manam (www428) became unresponsive while in service and required a reboot. Downtime was less than 10 minutes.

[Aug 11, 2008, 6:14 PM] duwo Downtime

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

[Aug 11, 2008, 1:27 PM] seyyav Downtime

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

[Aug 10, 2008, 5:56 PM] tisibo Downtime

tisibo (www265) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Aug 10, 2008, 5:38 PM] sether Downtime

sether (www95) became unresponsive and was rebooted. Downtime was 5 minutes.

[Aug 9, 2008, 7:45 AM] manam Downtime

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

[Aug 9, 2008, 2:48 AM] iruvul Maintenance Completed

The chassis upgrade for iruvul (www239) has been completed. It is now a Core2 6400 with 2GB of RAM. Downtime was about 10 minutes.

[Aug 9, 2008, 1:54 AM] iruvul Planned Maintenance

iruvul (www239) will be taken down shortly for a chassis upgrade. Total downtime should be about 10 minutes. An additional notice will be posted when the upgrade is complete.

[Aug 8, 2008, 10:30 PM] otaku Downtime

otaku (www338) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 8, 2008, 3:39 PM] thenge Downtime

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

[Aug 8, 2008, 1:28 PM] tinne Downtime

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

[Aug 8, 2008, 12:52 PM] iruvul Downtime

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

[Aug 8, 2008, 5:05 AM] kxoese, virre, agho Maintenance Completed

Today's upgrades are complete. kxoese and virre now have 120GB drives. agho now has a 160GB drive. Downtime for each server was under 10 minutes.

[Aug 8, 2008, 12:46 AM] kxoese, virre, agho Planned Maintenance

kxoese (www320), virre (www193), and agho (www187) 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.

[Aug 7, 2008, 8:24 PM] fiann Downtime

fiann (www188) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 7, 2008, 4:41 PM] iruvul Downtime

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

[Aug 7, 2008, 4:16 PM] siyazi Downtime

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

[Aug 7, 2008, 2:01 PM] kappa Downtime

kappa (www6) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Aug 7, 2008, 11:18 AM] iruvul Emergency Maintenance

iruvul (www239) became unresponsive while in service and was given an emergency RAM swap. The server now has 2GB of RAM. Total downtime was 10 minutes.

[Aug 7, 2008, 4:11 AM] aoujw, vash, eiga, fimfi Maintenance Completed

Today's upgrades are complete. New shadow drives have been installed in eiga and fimfi. aoujw now has a 160GB drive. vash now has a 120GB drive. Downtime for each server was under 10 minutes.

[Aug 7, 2008, 12:34 AM] kappa Downtime

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

[Aug 7, 2008, 12:31 AM] aoujw, vash, eiga, fimfi Planned Maintenance

aoujw (www366) and vash (www368) will be taken down shortly for drive upgrades. eiga (www326) and fimfi (www223) will be taken down for shadow drive upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Aug 6, 2008, 9:55 PM] otaku Downtime

otaku (www338) crashed while in service and was rebooted. Downtime was under 10 minutes.

[Aug 6, 2008, 6:35 AM] shen Downtime

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

[Aug 6, 2008, 3:30 AM] vinke Downtime

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

[Aug 6, 2008, 2:14 AM] chanas, enda, orvni Maintenance Completed

Today's upgrades are complete. chanas, enda, and orvni now have 160GB drives. Downtime for each server was about 5 minutes.

[Aug 6, 2008, 12:46 AM] chanas, enda, orvni Planned Maintenance

chanas (www321), enda (www80), and orvni (www205) 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.

[Aug 5, 2008, 1:42 PM] otaku Downtime

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

[Aug 5, 2008, 10:28 AM] iruvul Downtime

iruvul (www239) encountered an error and required a reset. Downtime was under 10 minutes.

[Aug 5, 2008, 9:49 AM] thenge Downtime

thenge (www270) encountered high load and was reset. Downtime was under 10 minutes.

[Aug 5, 2008, 8:41 AM] aedde Downtime

aedde (www84) encountered high load and was reset. Downtime was under 5 minutes.

[Aug 5, 2008, 5:06 AM] kerinci, lambe Maintenance Completed

Today's upgrades are complete. kerinci now has a 200GB drive. lambe has a 160GB drive. Downtime for each server was about 5 minutes.

[Aug 5, 2008, 2:10 AM] kerinci, lambe Planned Maintenance

kerinci (www392) and lambe (www63) 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.

[Aug 3, 2008, 7:47 PM] xi Downtime

xi (www8) came under high load and was rebooted. Downtime was less than 10 minutes.

[Aug 3, 2008, 7:18 PM] dair Downtime

dair (www20) became unresponsive and was rebooted. Downtime was 10 minutes.

[Aug 3, 2008, 8:20 AM] thenge Downtime

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

[Aug 3, 2008, 6:46 AM] otaku Downtime

otaku (www338) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 3, 2008, 1:36 AM] iruvul Downtime

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

[Aug 1, 2008, 11:51 PM] isris Downtime

isris (www194) became unresponsive under load and was reset. Downtime was about 5 minutes.

[Aug 1, 2008, 11:37 PM] niwun Downtime

niwun (www225) became unresponsive under load and was reset. Downtime was about 5 minutes.

[Aug 1, 2008, 4:49 PM] thenge Downtime

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

[Aug 1, 2008, 4:29 AM] sali Downtime

sali (www454) crashed and had to be rebooted. Downtime was about 5 minutes.

[Jul 31, 2008, 11:19 PM] nuumen Downtime

nuumen (www55) crashed while in service and was rebooted. Downtime was under 10 minutes.

[Jul 31, 2008, 4:21 PM] nezumi Downtime

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

[Jul 31, 2008, 3:08 PM] sali Downtime

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

[Jul 31, 2008, 2:35 PM] emra Downtime

emra (www183) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 31, 2008, 9:50 AM] akutan, peulik, vash Downtime

akutan (www361), peulik (www360), and vash (www368) were affected by a power outage. Measures have been taken to ensure that this does not happen again. Total downtime for each server was 10 minutes or less.

[Jul 31, 2008, 12:51 AM] lissa Downtime

lissa (www72) crashed after running out of swap space. Downtime was about 5 minutes.

[Jul 30, 2008, 11:50 PM] lissa Downtime

lissa (www72) became unresponsive while in service and was reset. Downtime was less than 10 minutes.

[Jul 30, 2008, 2:07 PM] gyaku Downtime

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

[Jul 30, 2008, 8:43 AM] nish Downtime

nish (www92) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 30, 2008, 2:37 AM] waianae, silme Maintenance Completed

The drive swaps for waianae and silme are complete. waianae now has a 250GB drive. A new shadow drive has been installed in silme. Downtime for each server was about 5 minutes.

[Jul 30, 2008, 1:45 AM] silme Emergency Maintenance

silme (www64) will be taken down shortly to replace a failing shadow drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Jul 30, 2008, 12:54 AM] bellat Downtime

bellat (www101) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 30, 2008, 12:43 AM] waianae Emergency Maintenance

waianae (www388) 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.

[Jul 29, 2008, 1:10 PM] cuzea Downtime

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

[Jul 29, 2008, 10:09 AM] anca Downtime

anca (www53) encountered an error and was reset. Downtime was under 15 minutes.

[Jul 29, 2008, 8:00 AM] thenge Downtime

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

[Jul 29, 2008, 7:09 AM] tisibo Downtime

tisibo (www265) experienced high load and was reset. Downtime was under 5 minutes.

[Jul 29, 2008, 7:01 AM] omicron Downtime

omicron (www9) became unresponsive and had to be reset. Downtime was less than 5 minutes.

[Jul 29, 2008, 5:31 AM] daas, kelut, rilwi Maintenance Completed

daas (www376) shadow drive has been replaced. kelut (www400) and rilwi (www347) now have 160GB drives. Downtime for each server was about 5 minutes.

[Jul 29, 2008, 1:24 AM] kelut, rilwi Planned Maintenance

kelut (www400) and rilwi (www347) 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 29, 2008, 12:12 AM] daas Emergency Maintenance

daas (www376) 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.

[Jul 28, 2008, 5:05 PM] masilma Downtime

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

[Jul 28, 2008, 12:20 PM] Ruby 1.8.7

All shared and current QS servers have been upgraded to Ruby 1.8.7 and RubyGems 1.2.0. Please contact support if you have any questions.

[Jul 28, 2008, 10:54 AM] eeoth Downtime

eeoth (www85) experienced high load and was reset. Downtime was under 10 minutes.

[Jul 27, 2008, 8:55 PM] iruvul Downtime

iruvul (www239) became unresponsive and had to be rebooted. Downtime was less than 5 minutes

[Jul 26, 2008, 6:49 AM] kanat Downtime

kanat (www128) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Jul 25, 2008, 2:35 PM] gort Emergency Maintenance

gort (www24) became unresponsive while in service and required a chassis upgrade before being brought back online. It is now a dual-core Xeon 3060 with 2 GB of RAM. Downtime was 20 minutes.

[Jul 25, 2008, 1:34 PM] gort Downtime

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

[Jul 25, 2008, 8:24 AM] kappa Downtime

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

[Jul 25, 2008, 5:14 AM] meru, abotye, djalbat, othala Maintenance Completed

Today's upgrades are complete. meru, djalbat, and othala now have 160GB drives. abotye has a 250GB drive. Downtime for each server was about 5 minutes.

[Jul 25, 2008, 3:53 AM] vilya Downtime

vilya (www60) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 25, 2008, 2:40 AM] gort Downtime

gort (www24) encountered an error and was reset. Downtime was about 15 minutes.

[Jul 25, 2008, 1:11 AM] meru, abotye, djalbat, othala Planned Maintenance

meru (www438), abotye (www298), djalbat (www313), and othala (www150) 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 24, 2008, 8:36 PM] mhoh Downtime

mhoh (www191) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 24, 2008, 6:00 PM] kappa Downtime

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

[Jul 24, 2008, 5:33 PM] lissa Downtime

lissa (www72) was reset to clear an error condition. Downtime was less than 1 minute.

[Jul 24, 2008, 1:50 PM] ando Downtime

ando (www45) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 24, 2008, 1:04 PM] cuzea Downtime

cuzea (www94) ran out of swap space and needed to be reset. Downtime was 10 minutes.

[Jul 24, 2008, 10:55 AM] eeoth Downtime

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

[Jul 24, 2008, 10:03 AM] allatu Downtime

allatu (www197) became unresponsive under high load and needed to be rebooted. A manual filesystem check was needed in order to return the server back to service. Total downtime was 20 minutes.

[Jul 24, 2008, 6:26 AM] eeoth Downtime

eeoth (www85) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jul 24, 2008, 5:56 AM] lissa, kanat, oppo, kelut Maintenance Completed

Today's maintenance is complete. lissa, kanat, and oppo now have 160GB drives. A new shadow drive has been installed in kelut. Downtime for each server was about 5 minutes.

[Jul 24, 2008, 1:22 AM] lissa, kanat, oppo, kelut Planned Maintenance

lissa (www72), kanat (www128), and oppo (www455) will be taken down shortly for drive upgrades. kelut (www400) will be taken down to install a larger shadow drive. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 24, 2008, 12:07 AM] atsui Downtime

atsui (www480) encountered an error and reset. Downtime was about 10 minutes.

[Jul 23, 2008, 6:19 PM] itonami Downtime

itonami (www333) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jul 23, 2008, 4:28 PM] atsui Downtime

erver atsui(www480) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Jul 23, 2008, 3:57 PM] atsui Downtime

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

[Jul 23, 2008, 1:55 PM] mirozo Downtime

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

[Jul 23, 2008, 2:52 AM] gnaaste, petora, edad Maintenance Completed

Today's upgrades are complete. gnaaste now has a 120GB drive. petora and edad now have 160GB drives. Downtime for each server was about 5 minutes.

[Jul 23, 2008, 12:47 AM] gnaaste, petora, edad Planned Maintenance

gnaaste (www79), petora (www229), and edad (www31) 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 22, 2008, 10:51 PM] eeoth Downtime

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

[Jul 22, 2008, 7:43 PM] kappa Downtime

kappa (www6) became unresponsive and was rebooted. Downtime was 5 minutes.

[Jul 22, 2008, 2:37 PM] raitax Downtime

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

[Jul 22, 2008, 2:27 PM] fayev Downtime

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

[Jul 22, 2008, 12:46 PM] karkar Downtime

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

[Jul 22, 2008, 12:45 PM] eeoth Downtime

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

[Jul 22, 2008, 12:31 PM] fayev Downtime

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

[Jul 22, 2008, 11:25 AM] CGIWrap 4.1

CGIWrap (including PHP-CGIWrap) has been upgraded to CGIWrap 4.1. This was necessary to patch a cross-site scripting vulnerability in the error page handling. Please contact support with any questions or concerns.

[Jul 22, 2008, 8:49 AM] otaku Downtime

otaku (www338) encountered high load and was reset. Downtime was under five minutes.

[Jul 22, 2008, 2:17 AM] tiwaz, linato Maintenance Completed

Today's maintenance is complete. tiwaz is now a Core2 E6420 with 2GB of RAM. linato now has a 160GB drive. Downtime for each server was about 5 minutes.

[Jul 22, 2008, 1:00 AM] linato, tiwaz Planned Maintenance

linato (www186) will be taken down shortly for a drive upgrade. tiwaz (www146) will be taken down for a chassis upgrade. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 21, 2008, 11:46 PM] okathi Maintenance Completed

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

[Jul 21, 2008, 11:14 PM] okathi Emergency Maintenance

okathi (www411) 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.

[Jul 21, 2008, 3:39 PM] auma Downtime

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

[Jul 21, 2008, 10:14 AM] canlaon Downtime

canlaon (www434) encountered high load and was reset. Downtime was under 10 minutes.

[Jul 21, 2008, 7:34 AM] biont Downtime

biont (www174) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 20, 2008, 10:18 AM] nuin Downtime

nuin (www18) because unresponsive due to high load and was reset. Total downtime was 15 minutes.

[Jul 20, 2008, 10:13 AM] eeoth Downtime

eeoth (www85) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 19, 2008, 4:14 AM] tinne Downtime

tinne (www21) ran out of swap space and had to be rebooted. Downtime was about 10 minutes.

[Jul 18, 2008, 4:19 AM] arda Maintenance Completed

The upgrades for arda are complete. It is now a Core2 E6420 with 2GB of RAM and a 200GB drive. Total downtime was about 10 minutes.

[Jul 17, 2008, 8:18 PM] arda Planned Maintenance

arda (www62) will be taken down shortly for a chassis upgrade, as well as a shadow drive upgrade. It will be taken down a second time to perform a drive upgrade. Total downtime should be about 10 minutes. An additional notice will be posted when the upgrades are complete.

[Jul 17, 2008, 3:18 PM] emra Downtime

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

[Jul 17, 2008, 10:20 AM] marapi Maintenance Completed

The emergency maintenance on marapi (www390) has been completed. It is now an Intel Core2 6400 with 2GB of RAM. Total downtime was under 40 minutes.

[Jul 17, 2008, 9:52 AM] marapi Emergency Maintenance

marapi (www390) will be taken down immediately to replace a failing chassis. Another notice will be posted when the maintenance has been completed.

[Jul 17, 2008, 6:58 AM] haebrath, arda, gnaaste Maintenance Completed

haebrath (www156) now has a 120 GB drive. A new shadow drive has been installed for gnaaste (www79). The drive upgrade for arda (www62) will be complete during the next maintenance window.

[Jul 17, 2008, 12:02 AM] haebrath, arda, gnaaste Planned Maintenance

haebrath (www156) and arda (www62) will be taken down shortly for drive upgrades. gnaaste (www79) 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 maintenance is complete.

[Jul 16, 2008, 2:51 PM] abej Downtime

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

[Jul 16, 2008, 1:54 PM] emra Downtime

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

[Jul 16, 2008, 5:37 AM] haebrath, londaste, abej Maintenance Completed

Today's maintenance is complete. A new shadow drive has been installed in haebrath. londaste and abej now have 160GB drives. Downtime for each server was about 5 minutes.

[Jul 16, 2008, 2:07 AM] haebrath, londaste, abej Planned Maintenance

haebrath (www156) will be taken down shortly for a shadow drive upgrade. londaste (www177) and abej (www464) 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.

[Jul 15, 2008, 7:30 PM] itonami Downtime

itonami (www333) experienced high load and was reset. Downtime was under five minutes.

[Jul 15, 2008, 5:26 PM] itonami Downtime

itonami (www333) encountered high load and was reset. Downtime was under 10 minutes.

[Jul 15, 2008, 11:31 AM] arda Downtime

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

[Jul 15, 2008, 9:42 AM] yanta Downtime

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

[Jul 15, 2008, 2:14 AM] lehhdi Maintenance Completed

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

[Jul 15, 2008, 1:43 AM] lehhdi Emergency Maintenance

lehhdi (www267) 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.

[Jul 14, 2008, 1:57 PM] karkar Downtime

karkar (www429) crashed due to high load and was reset. Downtime was about 10 minutes.

[Jul 13, 2008, 10:31 PM] nwalme Downtime

nwalme (www57) became unresponsive and was rebooted. Downtime was 10 minutes.

[Jul 12, 2008, 9:38 AM] arda Downtime

arda (www62) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Jul 12, 2008, 9:03 AM] wredhor Downtime

wredhor (www76) became unresponsive while in service and was reset. Downtime was 10 minutes.

[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