[Nov 9, 2009, 12:57 AM] jionor Downtime
jionor (www491) encountered an error and was reset. Downtime was about 5 minutes.

[Nov 8, 2009, 6:45 AM] oshima Maintenance Completed

The maintenance for oshima (www416) is now complete. Downtime was about 5 minutes.

[Nov 8, 2009, 6:30 AM] oshima Emergency Maintenance

oshima (www416) will be taken down momentarily to swap out a failing Shadow Drive. Another notice will be posted once maintenance is complete.

[Nov 8, 2009, 12:23 AM] zirx Downtime

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

[Nov 7, 2009, 4:08 AM] nezumi Downtime

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

[Nov 6, 2009, 12:37 PM] kesa Maintenance Completed

The maintenance on kesa (www479) has been completed. Downtime was about 10 minutes.

[Nov 6, 2009, 11:25 AM] kesa Emergency Maintenance

kesa (www479) will be taken down shortly to replace a failing primary drive. Another notice will be posted once maintenance is complete.

[Nov 6, 2009, 6:57 AM] gessire Downtime

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

[Nov 6, 2009, 6:14 AM] flunn Downtime

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

[Nov 6, 2009, 12:30 AM] ootanei Downtime

ootanei (www467) was taken down briefly to fix a filesystem error. Downtime was about 15 minutes.

[Nov 5, 2009, 8:36 PM] ndiccaa, ootanei Emergency Maintenance

This maintenance has been completed. ndiccaa (www317) now has a 140GB primary drive, and ootanei (www467) has a 200GB drive. Downtime for each server was under 10 minutes.

[Nov 5, 2009, 6:43 PM] ndiccaa, ootanei Planned Maintenance

Tonight after 8PM Easter, ndiccaa (www317) and ootanei (www467) will be taken down to swap out failing hard drives. Downtime should not exceed 15 minutes for each server. An additional notice will be posted once the maintenance is complete.

[Nov 5, 2009, 3:55 PM] ungwe, falku, voot, whury, akket, yiwen, gamsi, ghiq, izalc, kaba, taupo, auua, ohayou, kesa, atsui Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Nov 5, 2009, 2:09 PM] ungwe, falku, voot, whury, akket, yiwen, gamsi, ghiq, izalc, kaba, taupo, auua, ohayou, kesa, atsui Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

ungwe (www48)
falku (www98)
voot (www154)
whury (www179)
akket (www211)
yiwen (www246)
gamsi (www289)
ghiq (www324)
izalc (www378)
kaba (www394)
taupo (www426)
auua (www458)
ohayou (www477)
kesa (www479)
atsui (www480)

An additional notice will be posted once all upgrades have been completed.

[Nov 5, 2009, 5:11 AM] senwi, derba, iwote Maintenance Completed

Tonight's upgrades have been completed. senwi (www325) now has a 250GB primary drive, and iwote (www413) and derba (www104) were both given new shadow drives. Downtime for each server was less than 10 minutes.

[Nov 5, 2009, 2:07 AM] senwi, derba, iwote Planned Maintenance

senwi (www325) will be taken down shortly for a drive upgrade. iwote (www413) and derba (www104) will be taken down to replace failing shadow drives. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Nov 4, 2009, 4:58 PM] calma, tama, maor, enso, emra, oomur, wokkil, ezera, kunatri, nezumi, daas, batur, meru, inyo, bganat Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Nov 4, 2009, 2:27 PM] amse Downtime

amse (www210) encountered an error and was reset. Downtime was about 10 minutes.

[Nov 4, 2009, 2:16 PM] emra Downtime

emra (www183) was taken down to perform a manual file system check. Downtime was about 20 minutes.

[Nov 4, 2009, 1:37 PM] emra Downtime

emra (www183) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Nov 4, 2009, 1:20 PM] calma, tama, maor, enso, emra, oomur, wokkil, ezera, kunatri, nezumi, daas, batur, meru, inyo, bganat Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

calma (www43)
tama (www70)
maor (www113)
enso (www152)
emra (www183)
oomur (www209)
wokkil (www249)
ezera (www281)
kunatri (www316)
nezumi (www337)
daas (www376)
batur (www401)
meru (www438)
inyo (www453)
bganat (www481)

An additional notice will be posted once all upgrades have been completed.

[Nov 4, 2009, 10:06 AM] aoujw Downtime

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

[Nov 4, 2009, 5:18 AM] pyyl, loihi, karkar, kagamil, iwote, gyaku Maintenance Completed

Tonight's upgrades have been completed. loihi and gyaku now have 250GB drives, karkar and kagamil now have 200GB drives, and iwote now has a 160GB drive. Also, pyyl is now a Pentium 4 3.00GHz with 2GB of RAM. Downtime for each server was less than 10 minutes.

[Nov 4, 2009, 4:51 AM] dukoni Downtime

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

[Nov 4, 2009, 1:58 AM] pyyl, loihi, karkar, kagamil, iwote, gyaku Planned Maintenance

loihi (www387), karkar (www429), kagamil (www370), iwote (www413), and gyaku (www351) will be taken down shortly for drive upgrades. pyyl (www97) will be taken down for a chassis upgrade. Downtime for each server should be less than 10 minutes. An additional notice will be posted when these have been completed.

[Nov 4, 2009, 12:51 AM] gief Downtime

gief (www178) encountered an error and was reset. Downtime was about 10 minutes.

[Nov 3, 2009, 10:01 PM] maborym Downtime

maborym (www4) encountered an error and was reset. Downtime was about 10 minutes.

[Nov 3, 2009, 8:32 PM] wokkil Downtime

wokkil (www249) became unresponsive and required a reset. Downtime was less then 15 minutes.

[Nov 3, 2009, 7:33 PM] wokkil Downtime

wokkil (www249) became unresponsive and required a reset. Downtime was less then 5 minutes.

[Nov 3, 2009, 6:59 PM] jera Downtime

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

[Nov 3, 2009, 4:53 PM] wredhor, yuzz, tiwaz, zulle, maym, xamsa, xoopi, mokpa, itonami, peulik, salak, manam, kuwae, qiorre, wedhans Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Nov 3, 2009, 4:08 PM] pyyl Downtime

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

[Nov 3, 2009, 1:36 PM] wredhor, yuzz, tiwaz, zulle, maym, xamsa, xoopi, mokpa, itonami, peulik, salak, manam, kuwae, qiorre, wedhans Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

wredhor (www76)
yuzz (www117)
tiwaz (www146)
zulle (www175)
maym (www202)
xamsa (www244)
xoopi (www266)
mokpa (www303)
itonami (www333)
peulik (www360)
salak (www397)
manam (www428)
kuwae (www446)
qiorre (www482)
wedhans (www483)

An additional notice will be posted once all upgrades have been completed.

[Nov 3, 2009, 12:37 PM] xamsa Downtime

xamsa (www244) became unresponsive and required a reset. Downtime was less then 5 minutes.

[Nov 3, 2009, 11:45 AM] lopevi Downtime

lopevi (www445) encountered an error and was reset. Downtime was under 15 minutes.

[Nov 3, 2009, 9:41 AM] mokpa Downtime

mokpa (www303) encountered an error and was reset. Downtime was under 10 minutes.

[Nov 3, 2009, 8:44 AM] tyungwa Downtime

tyungwa (www311) encountered an error and was reset. Downtime was under 15 minutes.

[Nov 3, 2009, 4:56 AM] pyyl Downtime

pyyl (www97) encountered an error and was reset. Downtime was about 5 minutes.

[Nov 3, 2009, 1:56 AM] vetyle Downtime

vetyle (www381) encountered an error and was reset. Downtime was about 5 minutes.

[Nov 3, 2009, 12:21 AM] wokkil Downtime

wokkil (www249) encountered an error and was reset. Downtime was about 5 minutes.

[Nov 3, 2009, 12:20 AM] fayev Downtime

fayev (www365) encountered an error and was reset. Downtime was about 5 minutes.

[Nov 2, 2009, 8:55 PM] zortzi Downtime

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

[Nov 2, 2009, 3:58 PM] omega, mildh, reit, enek, bhoth, poict, uinus, saghotta, idouei, ittsui, ocha, loihi, agrihan, ambym, genki Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Nov 2, 2009, 3:09 PM] borro Downtime

borro (www489) encountered an error and was reset. Downtime was about 20 minutes.

[Nov 2, 2009, 2:48 PM] omega, mildh, reit, enek, bhoth, poict, uinus, saghotta, idouei, ittsui, ocha, loihi, agrihan, ambym, genki Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

omega (www16)
mildh (www87)
reit (www108)
enek (www130)
bhoth (www163)
poict (www195)
uinus (www228)
saghotta (www259)
idouei (www292)
ittsui (www323)
ocha (www355)
loihi (www387)
agrihan (www418)
ambym (www444)
genki (www484)

An additional notice will be posted once all upgrades have been completed.

[Nov 2, 2009, 8:14 AM] pyyl Downtime

pyyl (www97) encountered an error and reset. Downtime was less than 5 minutes.

[Nov 1, 2009, 8:08 PM] pyyl Downtime

pyyl (www97) encountered an error and was reset. A manual file system check was required. Downtime was about 10 minutes.

[Nov 1, 2009, 2:37 AM] migi Downtime

migi (www327) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 31, 2009, 4:27 PM] pyyl Downtime

pyyl (www97) encountered an error and was reset. Downtime was less than 5 minutes.

[Oct 31, 2009, 12:18 AM] or Downtime

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

[Oct 30, 2009, 12:49 PM] saakal Downtime

saakal (www264) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 10 minutes.

[Oct 30, 2009, 6:43 AM] merull Downtime

merull (www180) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 30, 2009, 6:30 AM] ansuz Downtime

ansuz (www137) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 30, 2009, 2:37 AM] mu Downtime

mu (www7) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 29, 2009, 9:05 PM] pyyl Downtime

pyyl (www97) encountered an error and was reset. A manual file system check was required. Downtime was about 15 minutes.

[Oct 29, 2009, 3:33 PM] gort, anca, yanta, gao, kanat, vsael, duwo, rendu, sekweta, midhae, djole, padaya, marapi, karkar, frebi Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 29, 2009, 12:47 PM] gort, anca, yanta, gao, kanat, vsael, duwo, rendu, sekweta, midhae, djole, padaya, marapi, karkar, frebi Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

gort (www24)
anca (www53)
yanta (www67)
gao (www111)
kanat (www128)
vsael (www173)
duwo (www219)
rendu (www240)
sekweta (www258)
midhae (www278)
djole (www314)
padaya (www385)
marapi (www390)
karkar (www429)
frebi (www485)

An additional notice will be posted once all upgrades have been completed.

[Oct 29, 2009, 12:02 PM] flaid Downtime

flaid (www91) became unresponsive while in service and required a manual file system check upon reboot. Downtime was about 20 minutes.

[Oct 29, 2009, 10:27 AM] kodh Downtime

kodh (www90) encountered an error and was reset. Downtime was 10 minutes.

[Oct 29, 2009, 8:09 AM] borro Downtime

borro (www489) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 29, 2009, 5:20 AM] sirung, foma, ulawun, suteki, sariga, kohala Maintenance Completed

Tonight's upgrades have been completed. sirung, ulawun, suteki, and sariga now have 160GB drives, and foma now has a 250GB drive. Additionally, kohala was given a new 250GB primary drive. Downtime for each server was about 5 minutes.

[Oct 29, 2009, 2:42 AM] sirung, foma, ulawun, suteki, sariga, kohala Planned Maintenance

sirung (www409), foma (www176), ulawun (www432), suteki (www339), and sariga (www420) will be taken down shortly for drive upgrades. Additionally, kohala (www389) will be taken down to swap a failing drive. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Oct 28, 2009, 11:20 PM] woolong Maintenance Completed

woolong (www367) now has a new shadow drive. Complete downtime was 20 minutes.

[Oct 28, 2009, 10:42 PM] woolong Planned Maintenance

woolong (www367) will be taken down shortly to replace a failing shadow drive. An additional notice will be posted when maintenance is completed.

[Oct 28, 2009, 6:39 PM] dempo Downtime

dempo (www395) encountered an error and was reset. Downtime was less than 10 minutes.

[Oct 28, 2009, 6:11 PM] patru Downtime

patru (www232) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 28, 2009, 3:25 PM] akai Downtime

akai (www353) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Oct 28, 2009, 2:56 PM] omicron, harma, bellat, othala, delsi, auddo, dukoni, gyaku, sramet, azuma, gaua, sali, olonto, eotle, daijoubu Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 28, 2009, 2:55 PM] calma Maintenance Completed

The chassis swap on calma (www43) is now complete. The server is now Core 2 E4400 with 2GB of RAM. Downtime was about 25 minutes.

[Oct 28, 2009, 2:10 PM] calma Emergency Maintenance

calma (www43) will be going down shortly to perform an emergency chassis swap. Another notice will be posted once the maintenance is complete.

[Oct 28, 2009, 12:06 PM] omicron, harma, bellat, othala, delsi, auddo, dukoni, gyaku, sramet, azuma, gaua, sali, olonto, eotle, daijoubu Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

omicron (www9)
harma (www50)
bellat (www101)
othala (www150)
delsi (www206)
auddo (www253)
dukoni (www305)
gyaku (www351)
sramet (www399)
azuma (www414)
gaua (www442)
sali (www454)
olonto (www460)
eotle (www487)
daijoubu (www488)

An additional notice will be posted once all upgrades have been completed.

[Oct 28, 2009, 4:19 AM] kuolau, fimfi, nadakh, pi, woolong Maintenance Completed

Tonight's upgrades have been completed. kuolau (www386) is now a Core 2 E4600 with 2GB of RAM and a 250GB primary drive. fimfi (www223) is now a Pentium 4 2.80 GHz with 2GB of RAM. nadakh (www287) now has a 250GB primary drive, and pi (www10) and woolong (www367) now have 160GB primary drives. Downtime for each server was less than 10 minutes.

[Oct 28, 2009, 1:41 AM] kuolau, fimfi, nadakh, pi, woolong Planned Maintenance

kuolau (www386) will be taken down shortly for a chassis and primary drive upgrade. fimfi (www223) will be taken down for a chassis upgrade, and nadakh (www287), pi (www10), and woolong (www367) will be taken down for drive upgrades. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Oct 28, 2009, 12:20 AM] hauda Downtime

hauda (www234) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 27, 2009, 6:42 PM] gamma, glikk, berkano, dotya, aveu, erraj, xebte, nandirse, tousko, suteki, kagamil, sariga, aoba, borro, musume Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 27, 2009, 4:57 PM] zelaza Downtime

zelaza (www247) encountered an error while in service and required a manual file system check. Downtime was about 20 minutes.

[Oct 27, 2009, 3:34 PM] gamma, glikk, berkano, dotya, aveu, erraj, xebte, nandirse, tousko, suteki, kagamil, sariga, aoba, borro, musume Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

gamma (www2)
glikk (www119)
berkano (www147)
dotya (www170)
aveu (www192)
erraj (www213)
xebte (www230)
nandirse (www255)
tousko (www291)
suteki (www339)
kagamil (www370)
sariga (www420)
aoba (www443)
borro (www489)
musume (www490)

An additional notice will be posted once all upgrades have been completed.

[Oct 27, 2009, 2:04 PM] musume Downtime

musume (www490) became unresponsive while in service and required a reboot. Downtime was less than 5 minutes.

[Oct 27, 2009, 12:13 PM] glikk Downtime

glikk (www119) became unresponsive while in service, and required a reboot. Downtime was less than 5 minutes.

[Oct 27, 2009, 12:00 PM] nadakh Emergency Maintenance

nadakh (www287) encountered an error and required a chassis swap. The server is now a Core 2 6700 with 4G of RAM.

[Oct 27, 2009, 11:48 AM] kodh Downtime

kodh (www90) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Oct 27, 2009, 9:45 AM] Network Maintenance Completed

We have completed the maintenance on our direct circuit to our Las Vegas servers.

[Oct 27, 2009, 8:49 AM] Network Maintenance

At approximately 9:00 AM Eastern, we will be performing maintenance on the direct circuit to our Las Vegas servers. During this time, the ACC may be unavailable to accounts located in Las Vegas. We expect to complete this maintenance no later than 10:00 AM. We apologize for any inconvenience.

[Oct 26, 2009, 4:02 PM] ngatwo, mini, peswar, kindoi, chanas, migi, ushiro, yinaska, kuolau, sirung, ulawun, oppo, traad, jionor, yuki Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 26, 2009, 3:40 PM] zhun Downtime

The server zhun (www107) encountered an error while in service and was reset. Downtime was 10 minutes.

[Oct 26, 2009, 2:09 PM] nadakh Downtime

nadakh (www287) became unresponsive while in service and was reset. Downtime was about 15 minutes.

[Oct 26, 2009, 1:36 PM] nadakh Downtime

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

[Oct 26, 2009, 12:27 PM] ngatwo, mini, peswar, kindoi, chanas, migi, ushiro, yinaska, kuolau, sirung, ulawun, oppo, traad, jionor, yuki Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

ngatwo (www115)
mini (www126)
peswar (www233)
kindoi (www308)
chanas (www321)
migi (www327)
ushiro (www350)
yinaska (www363)
kuolau (www386)
sirung (www409)
ulawun (www432)
oppo (www455)
traad (www478)
jionor (www491)
yuki (www493)

An additional notice will be posted once all upgrades have been completed.

[Oct 26, 2009, 12:25 PM] ailm Downtime

ailm (www28) became unresponsive while in service and required a reset. Downtime was about 10 minutes.

[Oct 26, 2009, 11:55 AM] eotle Downtime

eotle (www487) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Oct 26, 2009, 11:42 AM] ailm Downtime

ailm (www28) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Oct 25, 2009, 8:21 AM] eotle Downtime

eotle (www487) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Oct 25, 2009, 2:48 AM] erraj Downtime

erraj (www213) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 25, 2009, 1:24 AM] erraj Downtime

erraj (www213) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 24, 2009, 10:28 PM] calma Downtime

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

[Oct 24, 2009, 12:50 PM] dotya Downtime

dotya (www170) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Oct 24, 2009, 11:59 AM] theta Downtime

theta (www4) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 15 minutes.

[Oct 24, 2009, 9:06 AM] erraj Downtime

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

[Oct 24, 2009, 1:32 AM] qaske Downtime

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

[Oct 24, 2009, 12:15 AM] yuki Downtime

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

[Oct 23, 2009, 11:43 PM] calma Downtime

calma (www43) encountered and error and required a reboot. Downtime was under 10 minutes.

[Oct 23, 2009, 10:18 PM] lliamna Maintenance Completed

lliamna (www358) now has a new shadow drive. Downtime was about 5 minutes.

[Oct 23, 2009, 8:33 PM] lliamna Planned Maintenance

lliamna (www358) will be taken down shortly after 10PM EDT to replace a failing shadow drive. An additional notice will be posted after the maintenance is complete.

[Oct 23, 2009, 11:33 AM] naih Downtime

naih (www214) became unresponsive while in service and required a reset. Downtime was less than 10 minutes.

[Oct 23, 2009, 11:00 AM] eltsi Downtime

eltsi (www459) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 23, 2009, 10:23 AM] zais Maintenance Completed

The filesystems check on zais (www89) has been completed. Downtime was about 30 minutes.

[Oct 23, 2009, 9:39 AM] zais Emergency Maintenance

zais (www89) will be taken down shortly to run a manual filesystem check.

[Oct 23, 2009, 5:55 AM] zais, kohala, haebrath, gikani, lliamna Maintenance Completed

Tonight's drive upgrades have been completed. zais, haebrath, and lliamna now have 250GB drives, and kohala and gikani now have 160GB drives. Downtime for each server was less than 5 minutes.

[Oct 23, 2009, 2:23 AM] zais, kohala, haebrath, gikani, lliamna Planned Maintenance

zais (www89), kohala (www389), haebrath (www156), gikani (www301), and lliamna (www301) will be taken down shortly for drive upgrades. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Oct 22, 2009, 4:11 PM] ilwe, zais, aster, paat, dhabat Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 22, 2009, 4:00 PM] suoh Downtime

suoh (www396) became unresponsive and was reset. Downtime was about 5 minutes.

[Oct 22, 2009, 2:18 PM] umbar Downtime

umbar (www46) encountered an error and was reset. Downtime was less than 5 minutes.

[Oct 22, 2009, 12:38 PM] ilwe, zais, aster, paat, dhabat Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

ilwe (www81)
zais (www89)
aster (www96)
paat (www100)
dhabat (www105)

An additional notice will be posted once all upgrades have been completed.

[Oct 22, 2009, 10:26 AM] pyyl Downtime

pyyl (www97) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 22, 2009, 10:11 AM] thuule Downtime

thuule (www49) encountered an error and required a chassis swap. The server is now a Pentium 4 3.0 GHz with 3.5GB of RAM.

[Oct 22, 2009, 4:19 AM] gnaaste Downtime

gnaaste (www79) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 22, 2009, 3:31 AM] ocha Maintenance Completed

ocha (www355) now has a new Shadowdrive. Downtime was about 5 minutes.

[Oct 21, 2009, 9:27 PM] tiwaz Downtime

tiwaz (www146) encountered an error and was reset. Downtime was about 15 minutes.

[Oct 21, 2009, 7:39 PM] ihani, mordo, otara, pasang, osadha, coll, tinco, vilya, gwind, midori Maintenance Completed

The FreeBSD 7.2 upgrades for ihani, mordo, otara, pasang, osadha, coll, tinco, vilya, gwind, and midori are complete.

[Oct 21, 2009, 7:07 PM] waianae Downtime

waianae (www388) encountered an error and was reset. Downtime was less than 10 minutes.

[Oct 21, 2009, 5:53 PM] vilya Downtime

vilya (www60) encountered additional difficulties during its upgrade to FreeBSD 7.2 and was down for approximately 30 minutes while the upgrade was completed. We apologize for this inconvenience.

[Oct 21, 2009, 3:28 PM] ihani, mordo, otara, pasang, osadha, coll, tinco, vilya, gwind, midori Planned Maintenance

The following servers will be taken down momentarily to perform
FreeBSD 7.2 Upgrades:

ihani (www499)
mordo (www498)
otara (www500)
pasang (www494)
osadha (www497)
coll (www22)
tinco (www41)
vilya (www60)
gwind (www74)
midori (www492)

An additional notice will be posted once all upgrades have been completed.

[Oct 21, 2009, 3:01 PM] FreeBSD 7.2 Kernel Update

The following servers will be rebooted momentarily to install an updated FreeBSD 7.2 kernel:

vedra (www466)
sobo (www476)
gozaimasu (www486)
cead (www496)
tinne (www21)
uann (www462)

Downtime should be less than 5 minutes.

[Oct 21, 2009, 6:03 AM] calma Downtime

calma (www43) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 21, 2009, 4:36 AM] niwun Downtime

niwun (www225) encountered an error and was reset. Downtime was less than 5 minutes.

[Oct 21, 2009, 12:09 AM] siyazi Downtime

siyazi (www251) encountered an error and was reset. Downtime was under 5 minutes.

[Oct 20, 2009, 10:25 PM] oppo Downtime

oppo (www455) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 20, 2009, 5:13 PM] yasur Downtime

yasur (www447) unresponsive while in service and was reset. Downtime was less than 10 minutes.

[Oct 20, 2009, 7:13 AM] siyazi Downtime

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

[Oct 20, 2009, 3:43 AM] ocha Maintenance Completed

ocha (www355) now has a 500GB drive. Downtime was less then 10 minutes.

[Oct 20, 2009, 2:44 AM] ocha Emergency Maintenance

ocha (www355) will be taken down shortly to swap out a failing drive. Downtime should be less than 10 minutes. An additional notice will be posted when the maintenance is complete.

[Oct 19, 2009, 6:05 PM] glavandi Downtime

glavandi (www269) encountered an error and was reset. Downtime was about 15 minutes.

[Oct 19, 2009, 3:17 PM] straif Downtime

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

[Oct 19, 2009, 2:37 PM] vedra, sobo, gozaimasu, cead, tinne Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 19, 2009, 1:59 PM] vedra, sobo, gozaimasu, cead, tinne Planned Maintenance

The following servers will be taken down momentarily to perform FreeBSD 7.2 Upgrades:

vedra (www466)
sobo (www476)
gozaimasu (www486)
cead (www496)
tinne (www21)

An additional notice will be posted once all upgrades have been completed.

[Oct 19, 2009, 1:46 PM] eahta Downtime

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

[Oct 19, 2009, 1:45 PM] dukoni Downtime

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

[Oct 19, 2009, 11:20 AM] beeoro Downtime

beeoro (www69) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 19, 2009, 8:37 AM] amse Downtime

amse (www210) experienced high load and was reset. Downtime was under 10 minutes.

[Oct 19, 2009, 4:23 AM] iota Downtime

iota (www5) encountered an error and was reset. Downtime was less than 5 minutes.

[Oct 18, 2009, 10:51 PM] kodh Downtime

kodh (www90) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 18, 2009, 9:50 PM] amse Downtime

amse (www210) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 18, 2009, 3:14 PM] glikk Downtime

glikk (www119) became unresponsive due to high load and was reset. Downtime was about 20 minutes.

[Oct 17, 2009, 10:52 AM] nish Downtime

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

[Oct 17, 2009, 9:14 AM] yekk Downtime

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

[Oct 17, 2009, 4:06 AM] ilwe Downtime

ilwe (www81) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 17, 2009, 2:29 AM] ur Downtime

ur (www30) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 16, 2009, 5:32 PM] sirung Downtime

sirung (www409) crashed and was rebooted. Downtime was under 5 minutes.

[Oct 16, 2009, 12:29 PM] immi Downtime

immi (www457) became unresponsive and was reset. Downtime was 10 minutes.

[Oct 15, 2009, 11:12 PM] saakal Downtime

saakal (www264) encountered an error and reset itself. Downtime was about 3 minutes.

[Oct 15, 2009, 7:21 PM] Database Server Reboots Complete

The shared database server reboots are complete. Downtime for each server was about 10 minutes or less.

[Oct 15, 2009, 5:54 PM] Database Server Reboots

Over the next hour we will be rebooting all shared database servers to install a new kernel. Downtime for each server should be under 10 minutes. An additional notice will be posted when the reboots are complete.

[Oct 15, 2009, 2:01 PM] emancholl Downtime

emancholl (www37) encountered an error and was reset. Downtime was less than 10 minutes.

[Oct 15, 2009, 12:58 PM] amse Downtime

amse (www210) became unresponsive due to high load and was reset. Downtime was less then 10 minutes.

[Oct 14, 2009, 2:45 PM] uann Maintenance Completed

Today's FreeBSD upgrades have now been completed.

[Oct 14, 2009, 1:54 PM] uann Planned Maintenance

The following servers will be taken down momentarily to perform FreeBSD 7.2 Upgrades: uann (www462) An additional notice will be posted once all upgrades have been completed.

[Oct 14, 2009, 12:13 PM] PHP 5.2.11 for QuickServe and pairVPS

All pairVPS servers and QuickServe dedicated servers will be upgraded to PHP 5.2.11 today. Please contact support@pair.com or qs@pair.com if you experience any problems or have any questions.

[Oct 14, 2009, 8:19 AM] dukoni Downtime

dukoni (www305) encountered an error and was reset. Downtime was under 5 minutes.

[Oct 13, 2009, 10:48 PM] karkar Downtime

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

[Oct 13, 2009, 8:50 PM] glikk, pyyl, fayev Maintenance Completed

Tonight's maintenance is complete. glikk is now a Core2 E6420 with 2GB of RAM. A new shadow drive has been installed in pyyl. fayev now has a 250GB drive. Downtime for each server was under 10 minutes.

[Oct 13, 2009, 7:23 PM] glikk, pyyl, fayev Emergency Maintenance

glikk (www119) will be taken down shortly to swap out a failing chassis. pyyl (www97) will be taken down to swap out a failing shadow drive. fayev (www365) will also be taken down for an emergency drive upgrade. Downtime for each server should be under 10 minutes. An additional notice will be posted when the maintenance is complete.

[Oct 13, 2009, 2:03 PM] reit Downtime

reit (www108) encountered an error and was reset. Downtime was less than 10 minutes.

[Oct 13, 2009, 1:38 PM] anga Downtime

anga (www47) became unresponsive and required a reset. Downtime was less than 10 minutes.

[Oct 13, 2009, 10:09 AM] diviy Downtime

diviy (www217) encountered an error and was reset. Downtime was around 5 minutes.

[Oct 13, 2009, 5:20 AM] petora Maintenance Completed

petora (www229) now has a new Shadowdrive. Downtime was about 5 minutes.

[Oct 13, 2009, 4:22 AM] petora Planned Maintenance

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

[Oct 13, 2009, 3:04 AM] glikk Downtime

glikk (www119) encountered an error while in service and was reset. Downtime was under 10 minutes.

[Oct 12, 2009, 8:03 PM] glikk Downtime

glikk (www119) crashed while in service and was reset. A manual file system check was needed to bring it back online. Downtime was under 15 minutes.

[Oct 12, 2009, 2:59 PM] waianae Downtime

waianae (www388) encountered and error and was reset. Downtime was less than 5 minutes.

[Oct 12, 2009, 9:48 AM] gaccin Downtime

gaccin (www315) encountered an error while in service and was reset. Downtime was under 10 minutes.

[Oct 12, 2009, 2:23 AM] dallol Downtime

dallol (www379) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 12, 2009, 1:02 AM] glikk Downtime

glikk (www119) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Oct 11, 2009, 4:08 PM] kanat Downtime

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

[Oct 11, 2009, 10:44 AM] rho Downtime

rho (www11) crashed due to high load and was reset. Downtime was about 5 minutes.

[Oct 11, 2009, 10:25 AM] orvni Downtime

orvni (www205) crashed due to high load and was reset. Downtime was about 5 minutes.

[Oct 11, 2009, 7:13 AM] glikk Downtime

glikk (www119) encountered an error and was rebooted. Downtime was less than 5 minutes.

[Oct 10, 2009, 9:52 AM] xoopi Downtime

xoopi (www266) encountered high load and was reset. Downtime was under 10 minutes.

[Oct 10, 2009, 1:09 AM] migi Downtime

migi (www327) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 9, 2009, 10:24 PM] ezera Downtime

ezera (www281) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 9, 2009, 4:10 PM] glikk Downtime

glikk (www119) crashed and was rebooted. Downtime was under 5 minutes.

[Oct 9, 2009, 12:20 PM] db48 Emergency Maintenance

db48.pair.com will be taken down briefly to replace a failing boot drive. The boot drive does not host customer data so no databases should be affected. Downtime should be less than 10 minutes. A follow-up notice will be posted when maintenance has been completed.

[Oct 9, 2009, 12:28 AM] wokkil Downtime

wokkil (www249) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Oct 8, 2009, 10:34 PM] sirung Downtime

sirung (www409) crashed and rebooted. Downtime was under 10 minutes.

[Oct 8, 2009, 10:27 PM] inyo Downtime

inyo (www453) crashed and was rebooted. Downtime was under 5 minutes.

[Oct 8, 2009, 8:31 PM] oaboa Downtime

oaboa (www502) encountered an error and was reset. Downtime was about 10 minutes. The server is being monitored closely.

[Oct 8, 2009, 6:05 PM] oaboa Downtime

oaboa (www502) encountered and error and was reset. We are now watching this server closely. Downtime was about 5 minutes.

[Oct 8, 2009, 4:52 PM] fiann Downtime

fiann (www188) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Oct 8, 2009, 4:21 PM] maym Downtime

maym (www202) crashed under high load and was reset. Downtime was about 5 minutes.

[Oct 8, 2009, 4:20 PM] oaboa Downtime

oaboa (www502) became unresponsive and was reset. Downtime was about 5 minutes.

[Oct 8, 2009, 5:13 AM] glikk Downtime

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

[Oct 8, 2009, 1:13 AM] inyo Downtime

inyo (www453) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 7, 2009, 7:54 PM] glikk Downtime

glikk (www119) encountered an error and was reset. Downtime was about 10 minutes.

[Oct 7, 2009, 7:28 PM] djole Downtime

djole (www314) encountered an error and was reset. Downtime was less than 10 minutes.

[Oct 7, 2009, 5:42 PM] emancholl Downtime

emancholl became unresponsive and was reset. Downtime was less than ten minutes.

[Oct 7, 2009, 12:32 PM] inyo Downtime

inyo (www453) crashed due to high load and was reset. Downtime was about 5 minutes.

[Oct 7, 2009, 11:39 AM] fiann Downtime

fiann (www188) crashed due to high load and was reset. Downtime was about 5 minutes.

[Oct 7, 2009, 9:46 AM] glikk Downtime

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

[Oct 7, 2009, 3:03 AM] rilwi Downtime

rilwi (www347) encountered and error and was reset. Downtime was under 5 minutes.

[Oct 6, 2009, 9:10 PM] tinco Downtime

tinco (www41) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 6, 2009, 4:27 PM] tyungwa Downtime

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

[Oct 6, 2009, 10:48 AM] gaccin Downtime

gaccin (www315) encountered an error and was reset. Downtime was under 10 minutes.

[Oct 6, 2009, 12:23 AM] fayev Downtime

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

[Oct 5, 2009, 4:15 PM] mu Downtime

The server mu (www7) crashed while in service and was reset. Downtime was less than 10 minutes.

[Oct 5, 2009, 3:31 PM] sasi Downtime

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

[Oct 5, 2009, 3:18 PM] ailm Downtime

The server ailm (www28) crashed while in service and was reset. Downtime was 5 minutes.

[Oct 5, 2009, 7:05 AM] or Downtime

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

[Oct 5, 2009, 3:22 AM] or Downtime

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

[Oct 5, 2009, 3:11 AM] gaccin Downtime

gaccin (www315) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 4, 2009, 11:53 PM] raung Downtime

raung (www405) encountered an error and was reset. Downtime was about 15 minutes.

[Oct 4, 2009, 2:30 PM] amse Downtime

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

[Oct 4, 2009, 6:01 AM] amse Downtime

amse (www210) encountered an error and was reset. Downtime was about 5 minutes.

[Oct 3, 2009, 11:06 PM] Network Problems Resolved

We have received word from our vendors that the problem with the Global Crossing network has been resolved. If any customer is having continued issues, please contact us. We apologize for any inconvenience caused by this issue.

[Oct 3, 2009, 5:34 PM] Network Problems

The problem reported earlier, which is affecting a small percentage of network traffic, has been traced to problems in the Global Crossing network. This issue has been escalated with our vendors, and we will stay in close contact with them until the problem is resolved.

[Oct 3, 2009, 4:50 PM] Network Problems

We've received multiple reports of customers having trouble reaching our network, with the problem originating in the XO Communications network. We are working with our vendors to isolate the problem -- affected customers are encouraged to contact their ISP as well to report the problem.

[Oct 3, 2009, 11:17 AM] sallane Downtime

sallane (www263) became unresponsive due to high traffic and was reset. A manual file system check was needed to bring online. Downtime was 20 minutes.

[Oct 3, 2009, 8:09 AM] sallane Downtime

sallane (www263) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Oct 3, 2009, 12:24 AM] Server Reboots

Tonight's server reboots have been completed.

[Oct 2, 2009, 6:34 PM] Server Reboots

Beginning at 6:40 PM Eastern, we will begin rebooting all shared account servers, QuickServes, and Virtual QuickServes to apply a security patch. This includes all FreeBSD 6.2 and 7.2 servers. Downtime for each server should be about 5 minutes. An additional notice will be posted when the reboots are complete.

[Oct 2, 2009, 5:22 PM] penkwe Downtime

penkwe (www220) crashed and was rebooted. Downtime was under 10 minutes.

[Oct 2, 2009, 1:23 PM] flure Downtime

flure (www75) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 2, 2009, 5:42 AM] ur Downtime

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

[Oct 2, 2009, 12:13 AM] mildh Downtime

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

[Oct 1, 2009, 10:24 PM] yekk Downtime

yekk (www124) crashed and was rebooted. Downtime was under 5 minutes.

[Oct 1, 2009, 4:51 PM] aedde Downtime

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

[Oct 1, 2009, 12:41 PM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Oct 1, 2009, 10:04 AM] xebte Downtime

xebte (www230) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Oct 1, 2009, 7:36 AM] dakara Downtime

dakara (www441) encountered high load and was reset. Downtime was less than 10 minutes.

[Oct 1, 2009, 3:19 AM] mildh Downtime

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

[Oct 1, 2009, 12:06 AM] dhabat Downtime

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

[Sep 30, 2009, 8:49 PM] cead Downtime

cead (www496) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 30, 2009, 8:48 PM] zhun Downtime

zhun (www107) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 30, 2009, 8:18 PM] dhabat Downtime

dhabat (www105) encountered an error and was reset. Downtime was approximately 5 minutes.

[Sep 30, 2009, 1:08 PM] itske Downtime

itske (www472) encountered an error and was reset. Upon reboot, it required a manual file system check. Downtime was 10 minutes.

[Sep 30, 2009, 11:29 AM] kesa Downtime

kesa (www479) crashed due to high load and was reset. Downtime was under 10 minutes.

[Sep 30, 2009, 11:08 AM] zirx Downtime

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

[Sep 30, 2009, 10:18 AM] dakara Downtime

dakara (www441) crashed due to high load and was reset. Downtime was about 5 minutes.

[Sep 30, 2009, 7:11 AM] omicron Downtime

omicron (www9) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 30, 2009, 6:10 AM] eite Downtime

eite (www38) encountered an error and was reset. Downtime was about five minutes.

[Sep 30, 2009, 2:30 AM] glikk Downtime

glikk (www19) encountered an error and reset. Downtime was about 5 minutes.

[Sep 30, 2009, 1:58 AM] cead Downtime

cead (www496) encountered an error and reset. Downtime was about 5 minutes.

[Sep 30, 2009, 12:29 AM] wokkil Downtime

wokkil (www249) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 29, 2009, 8:28 PM] kuolau Downtime

kuolau (www386) became unresponsive while in server and was reset. Downtime was less than 10 minutes.

[Sep 29, 2009, 7:04 PM] tinne Downtime

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

[Sep 29, 2009, 1:59 PM] karkar Downtime

karkar (www429) encountered an error and required a reset. Downtime was about 5 minutes.

[Sep 29, 2009, 12:54 PM] karkar Downtime

karkar (www429) crashed while in service and was reset. Upon reboot, it required a manual file system check. Downtime was 20 minutes.

[Sep 29, 2009, 10:04 AM] yinaska Downtime

yinaska (www363) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 29, 2009, 9:36 AM] maor Downtime

maor (www113) encountered an error while in service and required a chassis swap. The hardware specifications have remained the same. Downtime was 30 minutes.

[Sep 29, 2009, 8:05 AM] torbaane Downtime

torbaane (www262) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 28, 2009, 6:55 PM] bunepi Downtime

bunepi (www318) encountered an error and had to be rebooted. Downtime was about 15 minutes.

[Sep 28, 2009, 4:19 PM] dhabat Downtime

dhabat (www105) crashed while in service and was reset. Downtime was less than 10 minutes.

[Sep 28, 2009, 3:19 PM] wokkil Downtime

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

[Sep 28, 2009, 3:07 PM] Network Problems Resolved

We have received word from our vendors that the problem with the Global Crossing network has been resolved, and we are now able to reach Integra Telecom from our network. If any customer is having continued issues, please contact us. We apologize for any inconvenience caused by this issue.

[Sep 28, 2009, 2:26 PM] maym Downtime

maym (www202) became unresponsive while in service and required a manual file system check. Downtime was under 15 minutes.

[Sep 28, 2009, 1:51 PM] maym Downtime

maym (www202) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 28, 2009, 1:21 PM] Network Problems

We have received problem reports from several customers having trouble reaching our network from Integra Telecom, with the traffic blocked in the Global Crossing network. We are currently working with our vendors to identify and correct this problem. We will post additional notices as updates are received.

[Sep 28, 2009, 1:16 PM] gaccin Downtime

gaccin (www315) became unresponsive while in server and was reset. Downtime was less than 10 minutes.

[Sep 28, 2009, 11:05 AM] emra Downtime

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

[Sep 27, 2009, 7:23 PM] kappa Downtime

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

[Sep 27, 2009, 1:19 PM] neter Downtime

neter (www132) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Sep 27, 2009, 4:00 AM] fiann Downtime

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

[Sep 27, 2009, 12:10 AM] atsui Downtime

atsui (www480) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Sep 26, 2009, 11:13 AM] atsui Downtime

atsui (www480) became unresponsive while in service and was reset. Downtime was less then 5 minutes.

[Sep 26, 2009, 10:09 AM] ulawun Downtime

ulawun (www432) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 25, 2009, 3:02 PM] nuin Downtime

nuin (www18) encountered an error and reset. Downtime was under 5 minutes.

[Sep 25, 2009, 1:40 PM] abej Downtime

The server abej (www464) crashed due to an error and was rebooted. The total downtime was under 15 minutes.

[Sep 25, 2009, 1:40 PM] siyazi Downtime

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

[Sep 25, 2009, 1:35 PM] mirozo Downtime

The server mirozo crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Sep 25, 2009, 2:55 AM] eite Downtime

eite (www38) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 25, 2009, 12:17 AM] xebte Downtime

xebte (www230) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 24, 2009, 9:31 PM] auddo Downtime

auddo (www253) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 24, 2009, 4:41 PM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was less than 5 minutes.

[Sep 24, 2009, 4:30 PM] omega Downtime

omega (www16) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 24, 2009, 3:54 PM] patru Downtime

patru (www232) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 24, 2009, 3:48 PM] xebte Downtime

xebte (www230) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 24, 2009, 3:30 PM] bemnet Downtime

bemnet (www158) crashed due to high load and was reset. Downtime was about 10 minutes.

[Sep 24, 2009, 11:11 AM] ur Downtime

ur (www30) became unresponsive and was reset. Downtime was under 10 minutes.

[Sep 24, 2009, 4:29 AM] immi Downtime

immi (www457) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 24, 2009, 3:21 AM] aoujw Downtime

aoujw (www366) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 24, 2009, 12:11 AM] yuki Downtime

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

[Sep 23, 2009, 9:28 PM] waiowa Maintenance Completed

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

[Sep 23, 2009, 8:57 PM] waiowa Emergency Maintenance

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

[Sep 23, 2009, 8:53 PM] yitiya Downtime

yitiya (www252) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 23, 2009, 8:06 PM] udumti Emergency Maintenance

udumti (www312) suffered a hardware failure and was given an emergency chassis swap. The server is now a Core2 Duo 6400 @ 2.13GHz with 2GB RAM. Downtime was about 15 minutes.

[Sep 23, 2009, 7:27 PM] udumti Downtime

udumti (www312) encountered an error and was reset. Downtime was under 15 minutes.

[Sep 23, 2009, 4:46 PM] karkar Downtime

karkar (www429) became unresponsive and was reset. Downtime was under 15 minutes.

[Sep 23, 2009, 12:07 PM] omsano Downtime

omsano (www164) crashed while in service and was reset. Downtime was 5 minutes.

[Sep 23, 2009, 11:59 AM] petora Downtime

petora (www229) crashed due to high load and was reset. Downtime was under 10 minutes.

[Sep 22, 2009, 11:22 PM] ampa Downtime

ampa (www52) became unresponsive and was reset. Downtime was under 15 minutes.

[Sep 22, 2009, 7:55 PM] or Downtime

or (www34) became unresponsive and was reset. Downtime was under 10 minutes.

[Sep 22, 2009, 4:54 PM] fimfi Downtime

fimfi (www223) encountered an error and had to be reset. Downtime was less than 10 minutes.

[Sep 22, 2009, 3:54 PM] dallol Downtime

dallol (www379) crashed and required a manual file system check. Downtime was 15 minutes.

[Sep 22, 2009, 3:41 PM] silme Downtime

silme (www64) encountered an error and was reset. Downtime was under 15 minutes.

[Sep 22, 2009, 3:01 PM] nisyros Downtime

nisyros (www383) encountered an error and had to be reset. Downtime was less than 10 minutes.

[Sep 22, 2009, 1:05 PM] gaua Downtime

gaua (www442) became unresponsive and was reset. Downtime was under 10 minutes.

[Sep 22, 2009, 12:38 PM] zhun Downtime

zhun (www107) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 22, 2009, 12:25 PM] penkwe Downtime

penkwe (www220) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 11:51 AM] sothor Downtime

sothor (www182) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 11:14 AM] aedde Downtime

aedde (www84) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 22, 2009, 11:04 AM] ando Downtime

ando (www45) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 10:33 AM] fimfi Downtime

fimfi (www223) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 10:11 AM] sothor Downtime

sothor (www182) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 6:08 AM] amse Downtime

amse (www210) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 3:48 AM] zulle Downtime

zulle (www175) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Sep 22, 2009, 3:30 AM] ur Downtime

ur (www30) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 2:53 AM] fimfi Downtime

fimfi (www223) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 22, 2009, 12:21 AM] zirx Downtime

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

[Sep 21, 2009, 10:35 PM] auddo Downtime

auddo (www253) encountered an error and was reset. Downtime was about 15 minutes.

[Sep 21, 2009, 9:12 PM] Network Problems Resolved

Our Verizon circuit was down from approximately 1:00 PM Eastern until 5:20 PM, due to a fiber cut at a construction site. Traffic was routed over alternate providers during this outage, with no loss in service. The circuit has remained stable since returning to service.

[Sep 21, 2009, 3:48 PM] ingwaz Downtime

ingwaz (www49) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Sep 21, 2009, 3:47 PM] coll Downtime

coll (www22) became unresponsive while in service and required a manual file system check. Downtime was about 15 minutes.

[Sep 21, 2009, 3:45 PM] mirozo Downtime

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

[Sep 21, 2009, 1:47 AM] niwun Downtime

niwun (www225) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 20, 2009, 1:06 PM] manam Downtime

manam (www428) ran out of swap space and was reset. Downtime was less then 10 minutes.

[Sep 20, 2009, 10:42 AM] calma Downtime

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

[Sep 19, 2009, 11:06 AM] omega Downtime

omega (www16) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Sep 19, 2009, 10:49 AM] mirozo Downtime

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

[Sep 19, 2009, 5:24 AM] borro Downtime

borro (www489) became unresponsive and was reset. Downtime was less than ten minutes.

[Sep 19, 2009, 1:14 AM] flure Downtime

flure (www75) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Sep 18, 2009, 9:55 PM] aedde Downtime

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

[Sep 18, 2009, 6:10 PM] maor Downtime

maor (www113) crashed and was rebooted. Downtime was under 5 minutes. We are monitoring this server closely.

[Sep 18, 2009, 3:03 PM] maor Downtime

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

[Sep 18, 2009, 2:57 PM] neter Downtime

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

[Sep 18, 2009, 12:07 PM] dempo Downtime

dempo (www395) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 10 minutes.

[Sep 18, 2009, 9:22 AM] yotoy Downtime

yotoy (www461) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Sep 18, 2009, 8:44 AM] ruis Downtime

ruis (www27) encountered an error and was rebooted. Total downtime was approximately 5 minutes.

[Sep 18, 2009, 5:20 AM] tenshian Downtime

tenshian (www103) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Sep 18, 2009, 4:09 AM] salanja Emergency Maintenance

salanja (www302) has been given an emergency chassis swap. It is now a P4 3.0GHz with 3.5GB of RAM. Downtime was about 15 minutes.

[Sep 17, 2009, 10:34 PM] silme Maintenance Completed

The maintenance on uumor has been completed. While the server was down it was given a chassis swap. The server is now a Core2 E6420 with 2GB of RAM.

[Sep 17, 2009, 10:04 PM] silme Planned Maintenance

silme (www64) will be taken down shortly to swap a failing ShadowDrive. Another notice will be posted once the maintenance has been completed.

[Sep 17, 2009, 5:41 PM] arda Downtime

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

[Sep 17, 2009, 5:27 PM] senwi Emergency Maintenance

senwi (www325) has been given an emergency chassis swap. It is now a Core2 E6420 with 2GB of RAM. Downtime was about 15 minutes.

[Sep 17, 2009, 4:56 PM] senwi Downtime

senwi (www325) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 17, 2009, 12:54 PM] senwi Downtime

senwi (www325) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Sep 17, 2009, 9:34 AM] yitiya Downtime

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

[Sep 17, 2009, 5:58 AM] sowilu Downtime

sowilu (www145) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 16, 2009, 3:52 PM] dyyme Downtime

The server dyyme (www71) crashed while in service and became unresponsive. Downtime was about 10 minutes.

[Sep 16, 2009, 1:29 PM] okmok Downtime

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

[Sep 16, 2009, 12:41 PM] Server Reboots

Beginning at 1:00PM, we will begin rebooting all shared account servers, QuickServes, and Virtual QuickServes to apply a security patch. This includes all FreeBSD 6.2 and 7.2 servers. Downtime for each server should be about 5 minutes. An additional notice will be posted when the reboots are complete.

[Sep 16, 2009, 8:41 AM] glikk Downtime

glikk (www119) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 16, 2009, 6:28 AM] tenshian Downtime

tenshian (www103) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 16, 2009, 3:24 AM] hauda Downtime

hauda (www234) encountered an error and reset. Downtime was about 5 minutes.

[Sep 16, 2009, 2:05 AM] hauda Downtime

hauda (www234) encountered an error and reset. Downtime was about 5 minutes.

[Sep 15, 2009, 11:44 AM] tenshian Downtime

tenshian (www103) experienced high load and was reset. Downtime was approximately 20 minutes. We are monitoring this server closely.

[Sep 15, 2009, 10:42 AM] tenshian Downtime

tenshian (www103) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 15, 2009, 5:39 AM] delsi Downtime

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

[Sep 15, 2009, 12:07 AM] cead Downtime

cead (www496) encountered an error and reset. Downtime was about 5 minutes.

[Sep 14, 2009, 8:15 PM] tenshian Emergency Maintenance

tenshian (www103) has been given an emergency chassis swap. It is now a Core2 E6420 with 2GB of RAM. Downtime was about 15 minutes.

[Sep 14, 2009, 7:28 PM] tenshian Downtime

tenshian (www103) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Sep 14, 2009, 8:04 AM] karkar Downtime

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

[Sep 14, 2009, 4:59 AM] patru Downtime

patru (www232) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 14, 2009, 12:10 AM] cead Downtime

cead (www496) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 13, 2009, 7:19 PM] bganat Downtime

bganat (www481) reset itself and was online within a few minutes.

[Sep 13, 2009, 7:00 PM] raung Maintenance Completed

raung (www405) now has a new 200GB drive. Downtime was less than 10 minutes.

[Sep 13, 2009, 5:59 PM] raung Emergency Maintenance

raung (www405) will be taken down shortly to replace a failing drive. Downtime should be under 10 minutes. An additional notice will be posted when the maintenance is complete.

[Sep 13, 2009, 4:26 PM] nish Downtime

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

[Sep 13, 2009, 2:50 PM] raung Downtime

raung (www405) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 13, 2009, 1:57 PM] or Downtime

or (www34) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Sep 13, 2009, 3:22 AM] mordo Downtime

mordo (www498) encountered an error and was reset. Downtime was about 15 minutes.

[Sep 12, 2009, 10:47 PM] yuzz Downtime

yuzz (www117) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 12, 2009, 3:15 AM] cicka Downtime

cicka (www167) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 11, 2009, 6:45 PM] maym Downtime

maym (www202) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 11, 2009, 5:23 PM] vemeq Emergency Maintenance

Due to ongoing issues with vemeq, an emergency hardware upgrade was performed. The new server is now a Core2 Duo 6400 @ 2.13GHz and 2GB of RAM. The total downtime was under 20 minutes.

[Sep 11, 2009, 4:26 PM] vemeq Downtime

vemeq (www328) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 11, 2009, 3:20 PM] maor Downtime

maor (www113) became unresponsive while in service and was reset. Downtime was 10 minutes. We are monitoring this server closely.

[Sep 11, 2009, 1:56 PM] maor Downtime

maor (www113) encountered an error and was reset. A manual file system check was required to bring the server back online. Downtime was 20 minutes.

[Sep 11, 2009, 1:08 PM] ohayou Downtime

ohayou (www477) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Sep 11, 2009, 3:12 AM] karkar Downtime

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

[Sep 10, 2009, 11:01 PM] akket Downtime

akket (www211) crashed and was rebooted. Downtime was under 5 minutes.

[Sep 10, 2009, 10:37 PM] uumor Maintenance Completed

The maintenance on uumor has been completed. Downtime was under 5 minutes.

[Sep 10, 2009, 10:09 PM] beeoro Downtime

beeoro (www69) crashed and required a manual file system check. Downtime was under 20 minutes.

[Sep 10, 2009, 10:05 PM] uumor Planned Maintenance

Shortly, uumor (www159) will be taken down to replace a failing ShadowDrive. Another notice will be posted when the maintenance has been completed.

[Sep 10, 2009, 2:31 PM] aedde Downtime

aedde (www84) encountered an error and had to be reset. Downtime was less than 10 minutes.

[Sep 10, 2009, 7:42 AM] jera Downtime

jera (www142) crashed due to high load. Downtime was about 5 minutes.

[Sep 10, 2009, 5:25 AM] jera Downtime

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

[Sep 10, 2009, 12:16 AM] wokkil Downtime

wokkil (www249) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 9, 2009, 9:49 PM] xomi Maintenance Completed

The maintenance on xomi (www169) is complete. It now has a 160GB primary drive. Downtime was under 10 minutes.

[Sep 9, 2009, 9:35 PM] xomi Planned Maintenance

Shortly, xomi (www169) will be taken down for a drive swap. An additional notice will be posted once the maintenance is complete.

[Sep 9, 2009, 7:25 PM] calma Downtime

calma (www43) crashed and was rebooted. Downtime was under 15 minutes.

[Sep 9, 2009, 7:13 PM] abej Downtime

abej (www464) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 9, 2009, 2:11 PM] xebte Downtime

xebte (www230) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 9, 2009, 6:34 AM] hasaya Downtime

hasaya(www364) encountered an error and was reset. Downtime was approximatel 10 minutes.

[Sep 9, 2009, 6:11 AM] lambe Maintenance Completed

lambe (www63) now has a new Shadowdrive. Downtime was under 5 minutes.

[Sep 9, 2009, 2:11 AM] lambe Planned Maintenance

lambe (www63) will be taken down shortly to replace a failing Shadowdrive. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[Sep 9, 2009, 12:29 AM] zirx Downtime

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

[Sep 8, 2009, 10:42 PM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was under 15 minutes.

[Sep 8, 2009, 3:10 PM] azul Downtime

azul (www375) became unresponsive while in service and required a reset. Downtime was less than 10 minutes.

[Sep 8, 2009, 2:48 PM] oynos Downtime

oynos (www218) encountered an error and was reset. Downtime was less than 5 minutes.

[Sep 8, 2009, 10:39 AM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was under 10 minutes.

[Sep 8, 2009, 7:50 AM] zais Downtime

zais (www89) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 8, 2009, 2:50 AM] auddo Downtime

auddo (www253) encountered an error and was reset. Downtime was about 10 minutes.

[Sep 8, 2009, 12:34 AM] zirx Downtime

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

[Sep 7, 2009, 1:37 PM] alayta Downtime

alayta (www380) encountered an error and was reset. Downtime was less than 10 minutes.

[Sep 6, 2009, 4:49 PM] fiann Downtime

fiann (www188) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 6, 2009, 1:11 AM] inyo Downtime

inyo (www453) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Sep 5, 2009, 9:09 PM] Network Problems Resolved

At approximately 8:15PM Eastern, our circuit between Pittsburgh and Las Vegas was restored. The cause of the outage was a water main break in Kansas City. We apologize for any inconvenience this downtime may have caused.

[Sep 5, 2009, 5:38 PM] Network Problems

At approximately 4:25 PM Eastern, our circuit between Pittsburgh and Las Vegas went offline. Our vendor is working to find and correct the problem. Customers with servers in Las Vegas may be unable to access the Account Control Center during this outage.

[Sep 5, 2009, 4:51 PM] fiann Downtime

fiann (www188) crashed and required a manual file system check. Downtime was under 20 minutes.

[Sep 5, 2009, 12:22 PM] maborym Downtime

maborym (www204) became unresponsive while in service and needed to be rebooted. Total downtime was less than 10 minutes.

[Sep 5, 2009, 11:32 AM] aerre Downtime

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

[Sep 4, 2009, 6:51 PM] gwind Downtime

gwind (www74) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 4, 2009, 2:39 PM] orvni Emergency Maintenance

orvni (www205) experienced a sudden drive failure and has been swapped to the shadow drive. All data was current as of approximately 12:36PM Eastern. Downtime was about 15 minutes.

[Sep 4, 2009, 2:03 PM] somkix Emergency Maintenance

somkix (www319) suffered a hardware failure and was given an emergency chassis swap. The server is now a Core2 Duo 6400 @ 2.13GHz with 2GB RAM. Downtime was about 15 minutes.

[Sep 4, 2009, 12:58 PM] somkix Downtime

somkix (www319) became unresponsive while in service and was reset. Downtime was less then 5 minutes.

[Sep 4, 2009, 10:24 AM] parma Downtime

parma (www42) ran out of swap space and needed to be rebooted. Total downtime was less than 15 minutes.

[Sep 4, 2009, 8:00 AM] somkix Downtime

somkix (www319) crashed and was rebooted. Downtime was under 5 minutes.

[Sep 3, 2009, 9:52 PM] aster Maintenance Completed

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

[Sep 3, 2009, 9:19 PM] aster Planned Maintenance

aster (www96) 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.

[Sep 3, 2009, 7:58 PM] alayta Downtime

alayta (www380) became unresponsive while in service. Downtime was less than 10 minutes.

[Sep 3, 2009, 3:40 PM] ulwar Downtime

ulwar (www82) became unresponsive while in service and was reset. Downtime was less then 5 minutes. We will continue to monitor this server.

[Sep 3, 2009, 3:12 PM] ulwar Downtime

ulwar (www82) ran out of swap space and required a reboot. Downtime was 10 minutes.

[Sep 3, 2009, 2:00 PM] ulwar Downtime

ulwar (www82) ran out of swap space and required a reset. Downtime was 10 minutes.

[Sep 3, 2009, 12:11 PM] vroo Downtime

vroo (www125) became unresponsive while in service and required a reset. Downtime was less than 10 minutes.

[Sep 3, 2009, 10:06 AM] vroo Downtime

vroo (www125) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 10 minutes.

[Sep 3, 2009, 8:53 AM] vroo Downtime

vroo (www125) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Sep 3, 2009, 6:38 AM] aedde Downtime

aedde (www84) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Sep 3, 2009, 12:37 AM] ceirt Downtime

ceirt (www39) encountered an error and was reset. Downtime was under 10 minutes.

[Sep 2, 2009, 10:18 PM] maor Maintenance Completed

The chassis upgrade for maor is complete. It is now a Core2 E6400 with 2GB of RAM. Downtime was about 5 minutes.

[Sep 2, 2009, 10:00 PM] maor Planned Maintenance

maor (www113) will be taken shortly for a chassis upgrade. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[Sep 2, 2009, 9:36 PM] diviy Downtime

diviy (www217) encountered an error and was reset. Downtime was under 5 minutes.

[Sep 2, 2009, 6:10 PM] ulwar Downtime

ulwar (www82) crashed again and was rebooted. We are monitoring this server closely. Downtime was under 10 minutes.

[Sep 2, 2009, 5:28 PM] ulwar Downtime

ulwar (www82) crashed and was rebooted. Downtime was under 10 minutes.

[Sep 2, 2009, 2:38 PM] somkix Downtime

The server somkix (www319) crashed due to a high load and was rebooted. The total downtime was 5 minutes.

[Sep 2, 2009, 2:28 PM] idad Emergency Maintenance

Due to recent crashes, idad (www32) has been upgraded with better hardware. The server is now a Core2 Duo 6400 @ 2.13GHz with 2GB RAM. Downtime was about 20 minutes.

[Sep 2, 2009, 1:21 PM] pyyl Downtime

pyyl (www97) encountered an error and reset itself. Downtime was less than 5 minutes.

[Sep 2, 2009, 12:33 PM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 2, 2009, 11:58 AM] beeoro Downtime

beeoro (www69) crashed due to high load and was reset. Downtime was about 10 minutes.

[Sep 2, 2009, 10:53 AM] lolmoh Downtime

lolmoh (www348) crashed due to high load and was reset. Downtime was about 5 minutes.

[Sep 2, 2009, 10:18 AM] kodh Downtime

kodh (www90) encountered an error and reset itself. Downtime was less than 5 minutes.

[Sep 2, 2009, 7:58 AM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was about 5 minutes.

[Sep 2, 2009, 12:47 AM] misilay Downtime

misilay (www282) encountered an error and reset. Downtime was about 10 minutes.

[Sep 1, 2009, 10:47 PM] enda Downtime

enda (www80) reset itself and was online within a few minutes.

[Sep 1, 2009, 4:33 PM] idad Downtime

The server idad (www32) crashed due to a high load and was rebooted. The total downtime was 15 minutes.

[Sep 1, 2009, 3:30 PM] phpMyAdmin Upgrade

We will be upgrading the version of phpMyAdmin installed on our my-db.pair.com server from version 2 to version 3.2.1. Any customer using the service will need to log back in after the upgrade.

[Sep 1, 2009, 8:22 AM] amutka Downtime

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

[Sep 1, 2009, 5:34 AM] pi, somkix, masilma Maintenance Completed

pi (www10) now has a new Shadowdrive. somkix (www319) has a 200GB drive. masilma (www307) has a 250GB drive. Downtime was about 5 minutes each.

[Sep 1, 2009, 4:21 AM] pi, somkix, masilma Planned Maintenance

pi (www10), somkix (www319), and masilma (www307) will be taken down shortly to replace failing drives. Downtime should be under 10 minutes each. An additional notice will be posted when the maintenance is complete.

[Sep 1, 2009, 4:11 AM] fiann Downtime

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

[Sep 1, 2009, 2:03 AM] erraj Downtime

erraj (www213) encountered an error and was reset. Downtime was about 15 minutes.

[Sep 1, 2009, 12:16 AM] egon Downtime

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

[Aug 31, 2009, 10:00 PM] delsi Downtime

delsi (www206) encountered an error and was reset. Downtime was less than 10 minutes.

[Aug 31, 2009, 7:16 PM] taupo Downtime

taupo (www426) became unresponsive while in service and was reset. Downtime was about 20 minutes.

[Aug 31, 2009, 5:42 PM] socorro Downtime

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

[Aug 31, 2009, 1:56 PM] sali Downtime

sali (www454) ran out of swap space and required a reset. Downtime was under 10 minutes.

[Aug 31, 2009, 1:52 PM] yitiya Downtime

yitiya (www252) encountered an error and was reset. Downtime was less than 10 minutes.

[Aug 31, 2009, 1:48 PM] egon Downtime

egon (www410) encountered an error and was reset. Downtime was 10 minutes.

[Aug 31, 2009, 12:55 PM] sali Downtime

sali (www454) ran out of swap space and required a reset. Downtime was about 15 minutes.

[Aug 31, 2009, 12:53 PM] khurla Downtime

khurla (www112) became unresponsive while in service and was reset. Downtime was less than 15 minutes.

[Aug 31, 2009, 10:56 AM] PHP 5.2.10 (pairVPS)

pairVPS servers were accidentally omitted from our PHP upgrade last week. These servers will be receiving the PHP 5.2.10 upgrade today. Please contact support@pair.com with any questions.

[Aug 30, 2009, 7:29 PM] mildh Downtime

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

[Aug 30, 2009, 7:22 AM] lassen Emergency Maintenance

lassen (www440) suffered a hardware failure and was given an emergency chassis swap. The server is now a Core2 Duo E6420 with 2GB of RAM. Downtime was about 10 minutes.

[Aug 30, 2009, 12:29 AM] ulwar Downtime

ulwar (www82) became unresponsive and had to be rebooted. Additionally, a manual disk check had to be performed before it could be returned to service. Downtime was about 10 minutes.

[Aug 29, 2009, 8:49 PM] ceirt Downtime

ceirt (www39) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 29, 2009, 3:34 PM] xoopi Maintenance Completed

The chassis swap of xoopi (www266) has been completed. It is now a P4 3.80GHz CPU with 3GB of RAM. Total downtime was 25 minutes.

[Aug 29, 2009, 3:09 PM] xoopi Emergency Maintenance

xoopi (www266) will be taken down to perform an emergency chassis swap. Another notice will be posted as soon as the maintenance has been completed.

[Aug 29, 2009, 6:57 AM] ulwar Downtime

ulwar (www82) ran out of swap space and had to be rebooted. Downtime was about 5 minutes.

[Aug 29, 2009, 12:18 AM] yuki Downtime

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

[Aug 28, 2009, 10:02 AM] ur Downtime

ur (www30) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 28, 2009, 2:30 AM] aerre Downtime

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

[Aug 28, 2009, 12:20 AM] gamma Downtime

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

[Aug 27, 2009, 10:02 PM] somkix Maintenance Completed

The shadow drive swap for somkix (www319) is complete. Downtime was about 5 minutes. The server now has a 250GB shadow drive.

[Aug 27, 2009, 7:58 PM] somkix Planned Maintenance

somkix (www319) will be taken down shortly after 9PM to swap out a failing shadow drive. Downtime should not exceed 10 minutes. Ad additional notice will be posted once the maintenance is complete.

[Aug 27, 2009, 6:06 PM] xomi Downtime

xomi (www169) encountered an error and was reset. Downtime was under 5 minutes.

[Aug 27, 2009, 4:45 PM] fiann Downtime

fiann (www188) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 27, 2009, 8:41 AM] gamma Downtime

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

[Aug 27, 2009, 3:08 AM] kesa Maintenance Completed

kesa (www479) now has a new 250GB drive. Downtime was less than 10 minutes.

[Aug 27, 2009, 12:50 AM] kesa Emergency Maintenance

kesa (www479) will be taken down shortly to replace a failing drive. Downtime should be under 10 minutes. An additional notice will be posted when the maintenance is complete.

[Aug 27, 2009, 12:22 AM] wokkil Downtime

wokkil (www249) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 26, 2009, 10:49 AM] idad Downtime

idad (www32) crashed due to high load and was reset. Downtime was under 10 minutes.

[Aug 26, 2009, 10:22 AM] atsui Downtime

atsui (www480) crashed due to high load and was reset. Downtime was about 5 minutes.

[Aug 26, 2009, 8:54 AM] salak Downtime

salak (www397) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 26, 2009, 8:24 AM] auddo Downtime

auddo (www253) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 26, 2009, 3:38 AM] gebo Downtime

gebo (www139) encountered an error and was reset. Downtime was about 5 minutes

[Aug 25, 2009, 11:20 PM] mildh Downtime

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

[Aug 25, 2009, 1:31 PM] karkar Downtime

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

[Aug 25, 2009, 1:21 PM] sali Downtime

sali (www454) became unresponsive while in service and required a reset. Downtime was less than 20 minutes.

[Aug 25, 2009, 11:29 AM] glikk Downtime

glikk (www119) encountered high load and was reset. Downtime was under 15 minutes.

[Aug 25, 2009, 8:07 AM] yuzz Downtime

yuzz (www117) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 25, 2009, 7:10 AM] ulwar Downtime

ulwar (www82) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Aug 25, 2009, 12:14 AM] woolong Downtime

woolong (www367) encountered an error and reset. Downtime was about 10 minutes.

[Aug 24, 2009, 10:10 PM] gwind Downtime

gwind (www74) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 24, 2009, 8:06 PM] woolong Downtime

woolong (www367) became unresponsive while in service and was reset. Downtime was about 20 minutes.

[Aug 24, 2009, 4:08 PM] parma Downtime

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

[Aug 24, 2009, 3:06 PM] kwarcu Downtime

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

[Aug 24, 2009, 1:31 PM] musume Downtime

musume (www490) encountered an error and was reset. Downtime was less than 10 minutes.

[Aug 24, 2009, 9:49 AM] hidari Emergency Maintenance Completed

hidari (www346) became unresponsive again and was given an immediate chassis swap. The server is now a P4 3.4GHz with 2GB of RAM. Total downtime for the maintenance was 20 minutes.

[Aug 24, 2009, 8:41 AM] ijen Downtime

ijen (www404) encountered an error and was reset. Downtime was under 15 minutes.

[Aug 24, 2009, 8:12 AM] ijen Downtime

ijen (www404) encountered high load and was reset. Downtime was under 10 minutes.

[Aug 24, 2009, 7:51 AM] ansuz Downtime

ansuz (www137) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 24, 2009, 7:08 AM] hidari Downtime

hidari (www346) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 24, 2009, 4:15 AM] idad Downtime

idad (www32) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 24, 2009, 12:25 AM] yuki Downtime

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

[Aug 23, 2009, 8:22 PM] ulwar Downtime

ulwar (www82) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 23, 2009, 6:24 PM] hidari Downtime

hidari (www346) reset itself and was online within a few minutes.

[Aug 23, 2009, 5:59 PM] amutka Downtime

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

[Aug 23, 2009, 5:07 PM] hidari Downtime

hidari (www346) crashed and was rebooted. A manual file system check was required on the drive. Downtime was about 15 minutes.

[Aug 23, 2009, 3:20 PM] daas Downtime

daas (www376) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 23, 2009, 10:59 AM] xebte Downtime

xebte (www230) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 23, 2009, 8:41 AM] klesh Downtime

klesh (www200) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Aug 23, 2009, 8:40 AM] hidari Downtime

hidari (www346) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 23, 2009, 3:38 AM] straif Downtime

straif (www26) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 23, 2009, 3:02 AM] Network Problems Resolved

Our Verizon circuit was returned to service at approximately 2:35AM Eastern. All traffic was carried over our other network providers during this circuit outage.

[Aug 23, 2009, 12:36 AM] wokkil Downtime

wokkil (www249) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 22, 2009, 11:40 PM] vsael Log Issue

Due to an error, the web logs for vsael (www173) for August 22 were removed, and will not be available. We apologize for any inconvenience this may cause.

[Aug 22, 2009, 11:13 PM] Network Problems

At approximately 10:15 PM Eastern, our Verizon circuit went offline. Our vendor is working to find and correct the problem. All traffic is being carried over our other network providers with no loss of service due to this circuit outage.

[Aug 22, 2009, 4:49 PM] kayan Emergency Maintenance completed

kayan (www133) became unresponsive again and was given an immediate chassis swap. The server is now a Core2 E8200 with 4GB of RAM. Total downtime for the maintenance was 20 minutes.

[Aug 22, 2009, 3:46 PM] kayan Downtime

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

[Aug 22, 2009, 6:51 AM] yitiya Downtime

yitiya (www252) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 22, 2009, 5:30 AM] hidari Downtime

hidari (www346) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 22, 2009, 1:36 AM] aedde Downtime

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

[Aug 22, 2009, 12:34 AM] zirx Downtime

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

[Aug 21, 2009, 9:19 PM] nezumi Emergency Maintenance

nezumi (www337) received an emergency chassis swap. The server is now a Core2 Duo E6400 @ 2.13GHz with 2GB of RAM. Downtime was about 10 minutes.

[Aug 21, 2009, 5:59 PM] nezumi Downtime

nezumi (www337) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 21, 2009, 4:55 PM] murifwae Downtime

murifwae (www279) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 21, 2009, 4:30 PM] idad Downtime

idad (www32) was reset. Downtime was under 5 minutes.

[Aug 21, 2009, 12:50 PM] kuroi Downtime

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

[Aug 21, 2009, 11:16 AM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was 10 minutes.

[Aug 21, 2009, 10:45 AM] yotoy Downtime

yotoy (www461) encountered an error and needed to be rebooted. Total downtime was approximately 5 minutes.

[Aug 21, 2009, 9:54 AM] ulwar Downtime

ulwar (www82) ran out of swap space and was rebooted. Downtime was under 10 minutes.

[Aug 21, 2009, 9:48 AM] iota Maintenance Completed

The chassis swap of iota (www5) is complete. The server is now an Intel P4 3.80GHz CPU with 2GB of RAM. Total downtime for the maintenance was approximately 30 minutes.

[Aug 21, 2009, 9:05 AM] iota Emergency Maintenance

iota (www5) will be taken down for an emergency chassis swap, since it was found to have cooling problems due to a fan that had failed. Another notice will be posted as soon as the server is back online.

[Aug 21, 2009, 7:57 AM] ulwar Downtime

ulwar (www82) ran out of swap space and had to be rebooted. Downtime was about 5 minutes.

[Aug 21, 2009, 4:43 AM] idad Downtime

idad (www32) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Aug 20, 2009, 11:20 PM] socorro Downtime

socorro (www422) encountered an error and was reset. Downtime was less than 5 minutes.

[Aug 20, 2009, 10:55 PM] nezumi Downtime

nezumi (www337) encountered an error and was reset. Downtime was less than 5 minutes.

[Aug 20, 2009, 4:25 PM] delsi Downtime

delsi (www206) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 20, 2009, 10:10 AM] petora Downtime and RAM upgrade

petora (www229) became unresponsive under high load and was rebooted. While the server was down, it was given a RAM upgrade for a total of 2.5GB of RAM. Total downtime was approximately 20 minutes.

[Aug 20, 2009, 8:59 AM] ulwar Downtime

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

[Aug 20, 2009, 4:48 AM] nwalme Downtime

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

[Aug 20, 2009, 4:35 AM] arda Downtime

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

[Aug 20, 2009, 4:34 AM] karkar Downtime

karkar (www429) encountered an error and was reset. A manual file system check was required. Downtime was about 20 minutes.

[Aug 19, 2009, 11:36 PM] aoujw Downtime

aoujw (www366) encountered an error and was reset. Downtime was less than 10 minutes.

[Aug 19, 2009, 9:00 PM] kaarei, londaste Maintenance Completed

The drive swaps for kaarei and londaste are complete. kaarei now has a 160GB drive, and londaste has a 250GB drive. Downtime for each server was about 5 minutes.

[Aug 19, 2009, 8:17 PM] londaste Downtime

londaste (www177) will be taken down shortly for an emergency drive upgrade. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[Aug 19, 2009, 6:33 PM] kaarei Emergency Maintenance

kaarei (www300) will be taken down shortly for an emergency drive upgrade. Downtime should be under 10 minutes. An additional notice will be posted when the upgrade is complete.

[Aug 19, 2009, 4:34 PM] poict Downtime

poict (www195) encountered an error and was reset. A manual file system check was required on the drive. Downtime was about 20 minutes.

[Aug 19, 2009, 2:11 PM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was less than 10 minutes.

[Aug 19, 2009, 12:43 PM] glikk Downtime

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

[Aug 19, 2009, 11:36 AM] gamsi Downtime

gamsi (www289) crashed due to high load and was reset. Downtime was about 5 minutes.

[Aug 19, 2009, 8:26 AM] auddo Downtime

auddo (www253) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 19, 2009, 7:00 AM] gikani Maintenance Completed

gikani (www301) now has a 120 GB drive and a new Shadowdrive. Downtime was less than 10 minutes total.

[Aug 19, 2009, 3:51 AM] mirozo Downtime

mirozo (www257) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 19, 2009, 2:01 AM] gikani Planned Maintenance

gikani (www301) will be taken down shortly for scheduled maintenance. Downtime should be less than 15 minutes total. An additional notice will be posted when the maintenance is complete.

[Aug 18, 2009, 6:15 PM] kaarei Emergency Maintenance

The server kaarei (www300) required a chassis swap due to a motherboard failure. The server was down for approximately 20 minutes. The server is now a Core2 Duo E6400 @ 2.13GHz and 2GB of RAM. We apologize for the inconvenience.

[Aug 18, 2009, 6:15 PM] huath Downtime

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

[Aug 18, 2009, 5:20 PM] taupo Downtime

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

[Aug 18, 2009, 2:33 PM] aoba Downtime

aoba (www443) became unresponsive while in service and required a reset. Downtime was less than 10 minutes.

[Aug 18, 2009, 12:19 PM] lambe Downtime

lambe (www63) became unresponsive while in service and required a reset. Downtime was less than 10 minutes.

[Aug 18, 2009, 11:49 AM] borro Downtime

borro (www489) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 17, 2009, 9:56 PM] thesel Downtime

thesel (www99) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 17, 2009, 5:51 PM] ur Downtime

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

[Aug 17, 2009, 4:24 PM] erraj Downtime

erraj (www213) encountered an error while in service and was reset. Downtime was about 15 minutes.

[Aug 17, 2009, 1:59 PM] PHP 5.2.10

All shared servers have now been upgraded to PHP 5.2.10. QuickServe dedicated servers will be upgraded on Wednesday, August 19th. Please contact support@pair.com or qs@pair.com with any questions or concerns.

[Aug 17, 2009, 11:57 AM] midori Downtime

The server midori (www492) encountered an error while in service and was reset. Downtime was about 10 minutes.

[Aug 17, 2009, 9:25 AM] ilwe Downtime

ilwe (www81) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 16, 2009, 9:45 AM] dukoni Downtime

dukoni (www305) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Aug 16, 2009, 4:27 AM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 16, 2009, 3:36 AM] midori Downtime

midori (www492) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 16, 2009, 12:16 AM] zirx Downtime

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

[Aug 15, 2009, 10:27 PM] idad Downtime

idad (www32) became unresponsive while in service and needed reset. Downtime was about 10 minutes.

[Aug 15, 2009, 5:48 PM] ceirt Downtime

ceirt (www39) encountered an error and was reset. Downtime was around 5 minutes.

[Aug 15, 2009, 3:09 AM] uruz Downtime

uruz (www135) encountered an error and was reset. A manual file system check was required on the drive. Downtime was about 20 minutes.

[Aug 14, 2009, 9:17 AM] uruz Downtime

uruz (www135) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 14, 2009, 4:12 AM] dempo Downtime

dempo (www395) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 14, 2009, 4:04 AM] rotua Maintenance Completed

The drive swap for rotua (www424) is now complete. This server now has a 250GB drive. Downtime was about 10 minutes.

[Aug 14, 2009, 2:32 AM] gamma Downtime

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

[Aug 14, 2009, 1:39 AM] rotua Downtime

rotua (www424) will be taken down shortly to swap out a failing drive. Downtime should be less than 15 minutes. An additional notice will be posted when the drive swap is complete.

[Aug 14, 2009, 1:13 AM] migi Downtime

migi (www327) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 14, 2009, 1:07 AM] yuzz Downtime

yuzz (www117) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 13, 2009, 11:01 PM] daijoubu Maintenance Completed

The maintenance on daijoubu (www488) has been completed. Downtime was under 10 minutes.

[Aug 13, 2009, 10:39 PM] daijoubu Planned Maintenance

Shortly, we will be taking down daijoubu (www488) to swap out a failing shadow drive. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is completed.

[Aug 13, 2009, 10:37 PM] lambe Maintenance Completed

The chassis upgrade for lambe is complete. It is now a P4 3.8 with 2.5GB of RAM. Downtime was under 10 minutes.

[Aug 13, 2009, 10:17 PM] oomur Downtime

oomur (www209) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 13, 2009, 10:10 PM] lambe Planned Maintenance

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

[Aug 13, 2009, 10:06 PM] ambym Downtime

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

[Aug 13, 2009, 4:24 PM] ilwe Downtime

ilwe (www81) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 13, 2009, 4:06 PM] yitiya Downtime

yitiya (www252) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 13, 2009, 8:50 AM] imtis Downtime

imtis (www208) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Aug 13, 2009, 8:17 AM] ansuz Downtime

ansuz (www137) encountered an error and reset. Downtime was less than 5 minutes.

[Aug 13, 2009, 8:16 AM] taupo Downtime

taupo (www426) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 13, 2009, 7:55 AM] zhun Downtime

zhun (www107) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 12, 2009, 10:05 PM] lissa Downtime

lissa (www72) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 12, 2009, 6:09 PM] saghotta Downtime

saghotta (www259) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 12, 2009, 2:51 PM] pi Downtime

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

[Aug 12, 2009, 9:47 AM] sothor Downtime

sothor (www182) became unresponsive while in service, and required a reset. Downtime was under 10 minutes.

[Aug 11, 2009, 9:17 PM] vert Downtime

vert (www102) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 11, 2009, 7:31 PM] eltsi Downtime

eltsi (www459) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Aug 11, 2009, 7:17 PM] auddo Downtime

auddo (www253) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 11, 2009, 3:57 PM] akai Downtime

The server akai (www353) crashed due to a high load. The total downtime was under 10 minutes.

[Aug 11, 2009, 2:05 PM] Account Control Center Maintenance

At approximately 2:15 PM Eastern, the ACC servers will receive a software update as part of weekly maintenance. This update will require all customers using the ACC to log in again afterward. Logged-in customers will receive a session error the first time they access the ACC after the update. We apologize for any inconvenience.

[Aug 11, 2009, 1:37 PM] zhun Downtime

The server zhun (www107) encountered an error and had to be restarted. Downtime was about 10 minutes.

[Aug 11, 2009, 12:29 PM] abej Downtime

abej (www464) encountered and error and was reset. Downtime was under 10 minutes.

[Aug 11, 2009, 4:38 AM] lambe Maintenance Completed

lambe (www63) now has a new Shadowdrive. Downtime was about 5 minutes.

[Aug 11, 2009, 4:00 AM] lambe Emergency Maintenance

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

[Aug 11, 2009, 12:50 AM] yuki Downtime

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

[Aug 10, 2009, 10:18 PM] siyazi Downtime

siyazi (www251) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 10, 2009, 1:59 PM] kesa Downtime

kesa (www479) was taken down briefly for a manual file systems check and repair. Downtime was approximately 10 minutes.

[Aug 10, 2009, 12:16 PM] kesa Downtime

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

[Aug 10, 2009, 11:38 AM] lambe Downtime

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

[Aug 10, 2009, 10:10 AM] paell Downtime

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

[Aug 10, 2009, 3:47 AM] kxoese Downtime

kxoese (www320) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 9, 2009, 4:33 PM] unque Downtime

unque (www54) became unresponsive while in service, and required a reset. Downtime was under 10 minutes.

[Aug 9, 2009, 8:30 AM] aedde Downtime

aedde (www84) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 9, 2009, 8:29 AM] or Downtime

or (www34) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Aug 9, 2009, 7:06 AM] tehun Downtime

tehun (www226) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 8, 2009, 4:45 PM] eeoth Maintenance Completed

The chassis swap of eeoth (www85) has been completed. The server is now a P4 3.40GHz with 2GB of RAM. Total downtime for the maintenance was less than 20 minutes.

[Aug 8, 2009, 4:44 PM] falku Downtime

falku (www98) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 8, 2009, 3:58 PM] eeoth Emergency Maintenance

eeoth (www85) will be taken down shortly for a chassis swap, as we have determined that the server is suffering from cooling issues. Another notice will be posted as soon as the server is back online.

[Aug 8, 2009, 12:07 PM] mu Downtime

mu (www7) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 8, 2009, 5:07 AM] eeoth Downtime

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

[Aug 8, 2009, 4:29 AM] eeoth Downtime

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

[Aug 8, 2009, 2:48 AM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 7, 2009, 9:46 PM] tuzuba Downtime

tuzuba (www256) crashed and was rebooted. Downtime was under 10 minutes.

[Aug 7, 2009, 4:21 PM] aedde Downtime

aedde (www84) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 7, 2009, 2:04 PM] kesa Downtime

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

[Aug 7, 2009, 1:55 PM] qaske Downtime

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

[Aug 7, 2009, 9:00 AM] glikk Downtime

glikk (www119) became unresponsive under high load and needed to be rebooted. Total downtime was about 10 minutes.

[Aug 7, 2009, 8:34 AM] unque Downtime

unque (www54) encountered an error and needed to be rebooted. Total downtime was approximately 5 minutes.

[Aug 7, 2009, 12:47 AM] calma Downtime

calma (www4) encountered an error and reset. Downtime was about 10 minutes.

[Aug 7, 2009, 12:21 AM] zirx Downtime

zirx (www106) encountered an error and had to be rebooted. Downtime was about 10 minutes.

[Aug 6, 2009, 7:18 PM] kaazh Downtime

kaazh (www212) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 6, 2009, 5:26 PM] lufem Downtime

lufem (www297) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 6, 2009, 5:03 AM] waiowa Maintenance Completed

waiowa (www430) now has a new Shadowdrive. Downtime was about 5 minutes.

[Aug 6, 2009, 4:28 AM] waiowa Planned Maintenance

waiowa (www430) will be taken down shortly for scheduled maintenance. Downtime should be less than 10 minutes. An additional notice will be posted when the maintenance is complete.

[Aug 5, 2009, 11:58 AM] okkod Downtime

okkod (www235) crashed due to high load and was reset. Downtime was under 10 minutes.

[Aug 5, 2009, 9:00 AM] delsi Downtime

delsi (www206) encountered an error and was reset. Downtime was under 10 minutes.

[Aug 4, 2009, 11:54 PM] flure Downtime

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

[Aug 4, 2009, 10:54 PM] ijen Maintenance Completed

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

[Aug 4, 2009, 9:45 PM] db107 Maintenance Complete

At this time, InnoDB tables on db107a have been returned to "read/write" status, and all databases with InnoDB tables have been restored.

[Aug 4, 2009, 9:35 PM] ijen Emergency Maintenance

ijen (www404) 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 4, 2009, 5:51 PM] db107 Emergency Maintenance

db107 has suffered a complete drive failure. We are currently working to restore the server. At this time, InnoDB tables on db107a are in "read only" mode. db107b is fully operational at this time. Backups for db107a were restored to current as of about 7:25PM yesterday. Another notice will be posted when InnoDB tables on db107a are restored to read/write status.

[Aug 4, 2009, 12:25 PM] rilwi Downtime

rilwi (www347) encountered and error and was reset. Downtime was less than 10 minutes.

[Aug 4, 2009, 6:05 AM] wunjo Downtime

wunjo (www140) encountered an error and reset. Downtime was less than 10 minutes.

[Aug 4, 2009, 1:10 AM] eotle Downtime

eotle (www487) encountered an error and was reset. Downtime was about 10 minutes.

[Aug 4, 2009, 12:04 AM] eotle Downtime

eotle (www487) became unresponsive while in service and required a restart. Downtime was less than 10 minutes. This server is being monitored closely.

[Aug 3, 2009, 11:05 PM] eotle Downtime

eotle (www487) became unresponsive while in service and required a restart. Downtime was less than 10 minutes.

[Aug 3, 2009, 8:14 PM] roku Downtime

roku (www343) became unresponsive while in service and required a restart. Downtime was less than 10 minutes.

[Aug 3, 2009, 6:43 PM] fiann Downtime

fiann (www188) crashed and was reset. Downtime was less then 15 minutes.

[Aug 3, 2009, 3:58 PM] taupo Downtime

taupo (www426) crashed after running out of swap space. Downtime was about 10 minutes.

[Aug 3, 2009, 11:07 AM] eotle Downtime

eotle (www487) became unresponsive while in service and required a restart. Downtime was less than 10 minutes.

[Aug 3, 2009, 8:14 AM] kanat Downtime

kanat (www128) encountered an error while in service and was reset. Downtime was under 5 minutes.

[Aug 3, 2009, 2:16 AM] eotle Downtime

eotle (www487) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 3, 2009, 1:50 AM] eotle Downtime

eotle (www487) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 2, 2009, 7:07 PM] morx Downtime

morx (www198) crashed and was reset. Downtime was about 10 minutes.

[Aug 2, 2009, 3:20 PM] mirozo Downtime

mirozo (www257) became unresponsive while in service and was reset. Downtime was less then 15 minutes.

[Aug 2, 2009, 3:17 AM] aoujw Downtime

aoujw (www366) encountered an error and was reset. Downtime was about 5 minutes.

[Aug 1, 2009, 9:37 PM] berkano Downtime

berkano (www147) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Aug 1, 2009, 3:02 PM] ceirt Downtime

ceirt (www39) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 20 minutes.

[Aug 1, 2009, 2:41 PM] cenena Downtime

cenena (www469) encountered an error an needed to be rebooted. Total downtime was less than 15 minutes.

[Aug 1, 2009, 10:35 AM] peulik Downtime

peulik (www360) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Aug 1, 2009, 2:04 AM] marapi Downtime

marapi (www390) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Aug 1, 2009, 12:25 AM] flaid Downtime

flaid (www91) became unresponsive and had to be rebooted. A manual disk check was also required during the reboot. The total downtime was about 15

[Jul 31, 2009, 8:35 PM] flaid Downtime

flaid (www91) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 31, 2009, 12:26 PM] foma Downtime

foma (www176) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 31, 2009, 10:26 AM] uruz Emergency Maintenance completed

uruz (www135) became unresponsive while in service and would not power back on. uruz was given an immediate chassis swap, and it is now an Intel Core2 E7200 with 2GB of RAM. Total downtime was approximately 25 minutes.

[Jul 31, 2009, 6:58 AM] ailm Downtime

ailm (www28) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Jul 31, 2009, 6:37 AM] alayta Downtime

alayta (www380) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 31, 2009, 1:55 AM] gessire Downtime

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

[Jul 30, 2009, 11:04 PM] otara Maintenance Completed

The maintenance for otara is complete. Downtime was less than 5 minutes.

[Jul 30, 2009, 9:01 PM] otara Planned Maintenance

otara (www500) will be taken down shortly for scheduled maintenance. Downtime should be less than 10 minutes. An additional notice will be posted when the maintenance is complete.

[Jul 30, 2009, 11:51 AM] ittsui Downtime

ittsui (www323) became unresponsive while in service and was reset. Additionally, a manual file system check was required. Downtime was approximately 40 minutes.

[Jul 30, 2009, 11:43 AM] zhun Downtime

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

[Jul 30, 2009, 2:13 AM] thesel Downtime

thesel (www99) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 29, 2009, 11:58 PM] marapi Downtime

marapi (www390) became unresponsive while in service. Downtime was less than 10 minutes.

[Jul 29, 2009, 11:56 PM] irazu Downtime

irazu (www377) encountered an error and was reset. Downtime was less than 10 minutes.

[Jul 29, 2009, 7:49 PM] egmont Downtime

egmont (www449) reset itself and was online within a few minutes.

[Jul 29, 2009, 3:19 PM] alayta Downtime

The server alayta (www380) encountered an error and had to be reset. Downtime was less than 10 minutes.

[Jul 29, 2009, 9:38 AM] enore Downtime

enore (www468) encountered high load and was reset. Downtime was under 10 minutes.

[Jul 29, 2009, 3:57 AM] vilya, itske Maintenance Completed

Maintenance is complete. vilya (www60) now has a 200 GB drive. itske (www472) has a 250 GB drive and a new Shadowdrive. Downtime was about 5 minutes each.

[Jul 29, 2009, 1:32 AM] vilya, itske Planned Maintenance

vilya (www60) and itske (www472) 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, 2009, 12:30 AM] yuki Downtime

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

[Jul 28, 2009, 4:30 PM] cereme Downtime

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

[Jul 28, 2009, 1:59 PM] roku Downtime

roku (www343) encountered an error while in service and was reset. Downtime was about 10 minutes.

[Jul 28, 2009, 11:31 AM] iski Downtime

The server iski (www242) encountered an error while in service and was reset. Downtime was about 10 minutes.

[Jul 28, 2009, 11:11 AM] ghiq Downtime

ghiq (www324) encountered a hardware error requiring a swap to a new chassis. The server is now running a Pentium 4 3.0Ghz processor with 2G of RAM. Downtime was approximately 20 minutes.

[Jul 28, 2009, 8:48 AM] suteki Downtime

suteki (www339) encountered an error and was reset. Downtime was under 5 minutes.

[Jul 28, 2009, 5:25 AM] bemnet, dieci, vilya Maintenance Completed

bemnet (www158), dieci (www231) both have 160 GB drives. The upgrade for vilya (www60) will be completed during the next maintenance window. Downtime for each server was under 10 minutes.

[Jul 28, 2009, 1:32 AM] bemnet, dieci, vilya Planned Maintenance

bemnet (www158), dieci (www231), and vilya (www60) 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 27, 2009, 9:27 PM] itske Maintenance Completed

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

[Jul 27, 2009, 8:50 PM] itske Emergency Maintenance

itske (www472) 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 maintenance is complete.

[Jul 27, 2009, 4:19 PM] ambym Downtime

The server ambym (www444) ran out of swap space and was rebooted. Additionally, a manual file system check was needed to complete the rebooting process. The total downtime for this was approximately 20 minutes.

[Jul 27, 2009, 8:39 AM] fiann Downtime

fiann (www188) encountered an error and was reset. Downtime was under 10 minutes.

[Jul 27, 2009, 5:46 AM] immi Downtime

immi (www457) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 27, 2009, 3:48 AM] rotua Downtime

rotua (www424) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 27, 2009, 1:58 AM] alayta Downtime

alayta (www380) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 26, 2009, 11:31 AM] kodh Downtime

kodh (www90) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 26, 2009, 6:53 AM] psi Downtime

psi (www15) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 26, 2009, 4:10 AM] neko Downtime

neko (www356) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 26, 2009, 4:10 AM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was about 15 minutes.

[Jul 25, 2009, 6:25 PM] gamma Downtime

gamma (www2) became unresponsive and had to be rebooted. reset. A manual file system check was required during the reboot. Downtime was about 15 minutes.

[Jul 25, 2009, 4:58 AM] qaske Downtime

qaske (www250) became unresponsive and had to be rebooted. Downtime was less than 10 minutes.

[Jul 25, 2009, 4:37 AM] nezumi Downtime

nezumi (www337) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 25, 2009, 2:44 AM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 25, 2009, 12:52 AM] wawrra Downtime

wawrra (www109) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 25, 2009, 12:18 AM] zirx Downtime

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

[Jul 24, 2009, 7:28 PM] yitiya Downtime

yitiya (www252) crashed and was reset. Downtime was under 10 minutes.

[Jul 24, 2009, 1:07 PM] khin Downtime

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

[Jul 24, 2009, 12:16 PM] anca Downtime

anca (www53) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 24, 2009, 12:19 AM] kesa Downtime

kesa (www479) encountered an error and reset. A manual file system check was required during the reboot. Downtime was about 15 minutes.

[Jul 23, 2009, 4:45 PM] atsui Downtime

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

[Jul 23, 2009, 12:16 PM] reit Downtime

reit (www108) became unresponsive while in service and required a reset. Total downtime was less than 10 minutes.

[Jul 23, 2009, 10:27 AM] soputan Downtime

soputan (www408) became unresponsive while in service and needed to be rebooted. Total downtime was 15 minutes.

[Jul 23, 2009, 9:35 AM] gamma Downtime

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

[Jul 23, 2009, 4:55 AM] izalc, vedra, paell Maintenance Completed

Upgrades are complete. vedra (www466) now has a 200 GB drive. izalc (www378) and paell (www153) both have 250 GB drives. Downtime for each server was about 5 minutes.

[Jul 23, 2009, 4:32 AM] aedde Downtime

aedde (www84) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Jul 23, 2009, 1:20 AM] izalc, vedra, paell Planned Maintenance

izalc (www378), vedra (www466), paell (www153) 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 23, 2009, 12:53 AM] wredhor Downtime

wredhor (www76) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 23, 2009, 12:26 AM] yuki Downtime

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

[Jul 22, 2009, 10:18 PM] fehu Downtime

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

[Jul 22, 2009, 3:37 PM] kesa Downtime

kesa (www479) became unresponsive and required a reset. The total downtime was about 10 minutes.

[Jul 22, 2009, 3:34 PM] ingwaz Downtime

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

[Jul 22, 2009, 10:53 AM] aoujw Downtime

aoujw (www366) crashed due to high load and was reset. Downtime was under 10 minutes.

[Jul 22, 2009, 6:21 AM] virre Downtime

virre (www193) encountered an error and was reset. Downtime was about 10 minutes

[Jul 22, 2009, 4:59 AM] kodh Downtime

kodh (www90) encountered an error and was reset. Downtime was under 5 minutes.

[Jul 22, 2009, 4:29 AM] yanta, hakone, shen Maintenance Completed

Upgrades are complete. yanta and shen have 160 GB hard drives. hakone has a 250 GB hard drive. Downtime for each server was about 5 minutes.

[Jul 22, 2009, 2:18 AM] kesa Maintenance Completed

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

[Jul 22, 2009, 1:58 AM] yanta, hakone, shen Planned Maintenance

yanta (www67), hakone (www415), and shen (www88) 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, 2009, 1:24 AM] calma Downtime

calma (www43) encountered an error and reset. Downtime was about 10 minutes.

[Jul 22, 2009, 1:22 AM] kesa Emergency Maintenance

kesa (www479) 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 22, 2009, 12:45 AM] aerre Downtime

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

[Jul 21, 2009, 8:11 PM] irazu Downtime

irazu (www377) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 21, 2009, 5:10 PM] maym Downtime

The server maym (www202) crashed due to an error and was rebooted. The total downtime was under 10 minutes.

[Jul 21, 2009, 12:59 PM] Network Maintenance

We will be taking down our Level(3) circuit briefly for maintenance. While the circuit is down, our other providers will handle all traffic.

[Jul 21, 2009, 11:07 AM] nezumi Downtime

nezumi (www337) encountered an error and was reset. Downtime was under 10 minutes.

[Jul 21, 2009, 10:18 AM] ohayou Downtime

ohayou (www477) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 21, 2009, 9:28 AM] falku Downtime

falku (www98) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 21, 2009, 9:11 AM] chi Downtime

chi (www14) encountered an error and was reset. Downtime was under 10 minutes. This server is being monitored closely.

[Jul 21, 2009, 8:38 AM] chi Downtime

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

[Jul 20, 2009, 2:42 PM] bganat Downtime

bganat (www481) encountered an error and was reset. Downtime was less than 10 minutes.

[Jul 20, 2009, 1:38 PM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was less than 10 minutes.

[Jul 19, 2009, 9:36 PM] yitiya Downtime

yitiya (www252) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 19, 2009, 11:57 AM] kunatri Downtime

kunatri (www316) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 19, 2009, 6:44 AM] kodh Downtime

kodh (www90) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 19, 2009, 4:04 AM] daas Downtime

daas (www376) became unresponsive and had to be rebooted. Total downtime was about 10 minutes.

[Jul 19, 2009, 12:20 AM] zirx Downtime

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

[Jul 18, 2009, 9:16 PM] mae Downtime

mae (www349) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 18, 2009, 5:09 AM] nezumi Downtime

nezumi (www337) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jul 18, 2009, 2:07 AM] shema Emergency Maintenance

The restoration of shema (www203) from backups is now complete. Once again, we apologize for any inconvenience caused by this outage.

[Jul 17, 2009, 11:10 PM] shema Emergency Maintenance

All mail, home, SSL, and public FTP directories have been restored on shema (www203). Most web directories have been restored -- the final nine are uncompressing from backups at this time. We apologize for the inconvenience caused by this outage.

[Jul 17, 2009, 9:41 PM] aedde Downtime

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

[Jul 17, 2009, 8:25 PM] shema Emergency Maintenance

We have determined that shema (www203) will need to be restored from backups. The backups are now being moved over to the machine and will be put in place over the next few hours. Customer data will become available across that time. Incoming mail will be held until everything is back in place.

[Jul 17, 2009, 8:16 PM] shema Emergency Maintenance

shema (www203) has suffered a primary hard drive failure, and is showing errors on its secondary drive as well. We are currently evaluating the situation and will return it to service as soon as possible. If the secondary drive is not viable, we'll be restoring from off-server backups that are current as of approximately 5 AM Eastern today.

[Jul 17, 2009, 7:24 PM] enore Downtime

enore (www468) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 17, 2009, 5:00 PM] shema Downtime

shema (www203) was reset to clear an error condition. Downtime was about 5 minutes.

[Jul 17, 2009, 10:40 AM] otok Downtime

otok (www131) ran out of swap space and needed to be rebooted. Total downtime was approximately 10 minutes.

[Jul 17, 2009, 2:00 AM] dempo Downtime

dempo (www395) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Jul 16, 2009, 6:48 PM] aqquz Downtime

aqquz (www248) encountered an error and was reset. Downtime was less than 5 minutes.

[Jul 16, 2009, 5:30 AM] karkar Downtime

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

[Jul 16, 2009, 12:22 AM] zirx Downtime

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

[Jul 15, 2009, 2:59 PM] rexai Downtime

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

[Jul 15, 2009, 2:58 PM] ilwe Downtime

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

[Jul 15, 2009, 9:27 AM] nezumi Downtime

nezumi (www337) became unresponsive while in service and required a reset. Downtime was about 10 minutes.

[Jul 15, 2009, 8:43 AM] ghiq Downtime

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

[Jul 15, 2009, 5:13 AM] izalc, vedra, inyo, vash Maintenance Completed

Today's upgrades are complete. izalc, vedra, and vash now have 160GB drives. inyo now has a 200GB drive. Downtime for each server was about 5 minutes.

[Jul 15, 2009, 2:24 AM] jera Downtime

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

[Jul 15, 2009, 12:31 AM] izalc, vedra, inyo, vash Planned Maintenance

izalc (www378), vedra (www466), inyo (www453), and vash (www368) 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 15, 2009, 12:27 AM] zirx Downtime

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

[Jul 14, 2009, 10:35 PM] karkar Downtime

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

[Jul 14, 2009, 9:19 PM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 14, 2009, 7:52 PM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 14, 2009, 6:45 PM] eite Downtime

eite (www38) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 14, 2009, 12:36 PM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was less than 10 minutes.

[Jul 14, 2009, 7:57 AM] ijen Downtime

ijen (www404) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 14, 2009, 7:15 AM] gamma Downtime

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

[Jul 14, 2009, 2:43 AM] dukoni, upsilon, shema Maintenance Completed

The drive swaps for dukoni and upsilon are now complete. Each server now has a 160GB drive. The shadow drive swap for shema is also complete. Downtime for each server was about 5 minutes.

[Jul 14, 2009, 12:15 AM] dukoni, upsilon, shema Emergency Maintenance

dukoni (www305) and upsilon (www13) will be taken down shortly to swap out failing drives. shema (www203) will be taken down to swap out a failed shadow drive. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Jul 13, 2009, 7:44 PM] agrihan Downtime

agrihan (www418) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 13, 2009, 4:14 PM] dieci Downtime

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

[Jul 13, 2009, 4:13 PM] gamma Downtime

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

[Jul 13, 2009, 5:50 AM] yiwen Downtime

yiwen (www246) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Jul 13, 2009, 4:13 AM] ijen Downtime

ijen (www404) crashed due to a high load and was rebooted. The total downtime was under 10 minutes.

[Jul 13, 2009, 1:44 AM] ijen Downtime

ijen (www404) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 12, 2009, 9:42 PM] otok Downtime

otok (www131) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 12, 2009, 9:42 PM] neled Downtime

neled (www127) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 12, 2009, 8:00 PM] agrihan Maintenance Completed

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

[Jul 12, 2009, 6:02 PM] agrihan Emergency Maintenance

agrihan (www418) 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 12, 2009, 5:10 PM] vedra Downtime

vedra (www466) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 12, 2009, 4:10 PM] omicron Maintenance Completed

The chassis swap on omicron (www9) has been completed. The server is now a Pentium 4 3.00GHz with 3.5GB of RAM. The shadow drive was also swapped to a SATA drive during this down time. Total downtime for the maintenance was about 15 minutes.

[Jul 12, 2009, 3:34 PM] omicron Emergency Maintenance

omicron (www9) will be taken down shortly for a chassis swap. An additional notice will be posted when completed.

[Jul 12, 2009, 9:53 AM] omicron Downtime

omicron (www9) encountered an error and was reset. Downtime was under 10 minutes. This server is being monitored closely.

[Jul 12, 2009, 9:22 AM] omicron Downtime

omicron (www9) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jul 11, 2009, 8:43 PM] dempo Downtime

dempo (www395) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jul 10, 2009, 4:42 PM] gamma Downtime

gamma (www2) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 9, 2009, 8:35 PM] kaazh Downtime

kaazh (www212) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 9, 2009, 4:12 AM] kindoi, kwarcu, ainaz Maintenance Completed

Today's upgrades are complete. kindoi and kwarcu now have 250GB drives. ainaz now has a 160GB drive. Downtime for each server was about 5 minutes.

[Jul 9, 2009, 2:59 AM] glavandi Downtime

glavandi (www269) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jul 9, 2009, 1:54 AM] kindoi, kwarcu, ainaz Planned Maintenance

kindoi (www308), kwarcu (www293), and ainaz (www221) 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, 2009, 1:38 AM] aedde Maintenance Completed

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

[Jul 9, 2009, 12:28 AM] aedde Emergency Maintenance

aedde (www84) 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 8, 2009, 2:45 PM] abej Downtime

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

[Jul 8, 2009, 12:20 AM] falku Downtime

falku (www98) encountered an error and was reset. Downtime was about 10 minutes.

[Jul 7, 2009, 11:44 AM] diviy Downtime

diviy (www217) encountered an error and was reset. Downtime was under 10 minutes.

[Jul 7, 2009, 10:44 AM] falku Downtime

falku (www98) encountered an error and was reset. Downtime was under 10 minutes.

[Jul 7, 2009, 4:47 AM] udumti, kohala, naudhiz, eahta Maintenance Completed

Today's maintenance is complete. A new shadow drive has been installed in kohala. udumti now has a 120GB drive. naudhiz and eahta now have 160GB drives. Downtime for each server was under 10 minutes.

[Jul 7, 2009, 2:41 AM] udumti, kohala, naudhiz, eahta Planned Maintenance

udumti (www312), naudhiz (www141), and eahta (www227) will be taken down shortly for drive upgrades. kohala (www389) will also 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 7, 2009, 1:50 AM] wredhor, kikai Maintenance Completed

The drive swaps for wredhor and kikai are complete. A new shadow drive has been installed in kikai. wredhor now has a 200GB drive. Downtime for each server was under 10 minutes.

[Jul 7, 2009, 12:29 AM] wredhor, kikai Emergency Maintenance

wredhor (www76) will be taken down shortly to replace a failing drive. kikai (www417) will be taken down to replace a failing shadow drive. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Jul 6, 2009, 10:17 PM] abej Downtime

abej (www464) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 6, 2009, 6:25 PM] gaccin Downtime

gaccin (www315) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jul 6, 2009, 4:26 PM] parma Downtime

parma (www42) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 6, 2009, 12:20 AM] morx Downtime

morx (www198) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 5, 2009, 10:18 PM] cenena Downtime

cenena (www469) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 5, 2009, 8:56 PM] idad Downtime

idad (www32) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 5, 2009, 5:52 PM] soputan Downtime

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

[Jul 5, 2009, 5:37 PM] dotya Downtime

dotya (www170) became unresponsive while in service and was reset. Downtime was about 10 minutes

[Jul 5, 2009, 2:48 PM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was less than 5 minutes.

[Jul 5, 2009, 1:40 PM] wredhor Maintenance Completed

The drive swap on wredhor (www76) has been completed. It now has a 160GB primary drive. During the drive swap some difficulties were encountered and a chassis swap was performed that caused unexpected downtime. The server is now a Pentium 4 3.00GHz with 4GB of RAM. Total downtime was 50 minutes.

[Jul 5, 2009, 1:39 PM] bhoth Downtime

bhoth (www163) encountered an error and was reset. Downtime was less then 10 minutes.

[Jul 5, 2009, 10:58 AM] alayta Downtime

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

[Jul 5, 2009, 10:36 AM] wredhor Emergency Maintenance

wredhor (www76) 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 5, 2009, 8:43 AM] manam Downtime

manam (www428) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 5, 2009, 8:00 AM] wredhor Downtime

wredhor (www76) encountered an error and was reset. Downtime was about 5 minutes.

[Jul 5, 2009, 12:28 AM] flure Downtime

flure (www75) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jul 4, 2009, 11:47 PM] tama Downtime

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

[Jul 4, 2009, 10:23 PM] dieci Downtime

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

[Jul 4, 2009, 8:17 PM] flure Downtime

flure (www75) crashed and was rebooted. Downtime was under 10 minutes.

[Jul 4, 2009, 10:18 AM] huath Downtime

huath (www19) encountered an error and had to be rebooted. Downtime was about 10 minutes.

[Jul 4, 2009, 9:29 AM] aedde Downtime

The server aedde (www84) crashed due to a high load and was rebooted. The total downtime was approximately 10 minutes.

[Jul 4, 2009, 6:24 AM] ulwar Downtime

ulwar (www82) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Jul 3, 2009, 7:43 PM] mae, qatlh Maintenance Completed

This maintenance has been completed. mae (www349) now has a 160GB primary drive. Downtime for each server was under 10 minutes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Jun 19, 2009, 3:41 PM] parma Downtime

parma (www42) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 19, 2009, 2:16 PM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 19, 2009, 12:31 AM] muin Downtime

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

[Jun 18, 2009, 3:56 AM] gaua Maintenance Completed

gaua (www442) now has a 200GB drive. Downtime was less than 5 minutes.

[Jun 18, 2009, 3:02 AM] gaua Planned Maintenance

gaua (www442) will be taken down shortly to swap out a failing drive. An additional notice will be posted when the swap is complete.

[Jun 18, 2009, 12:19 AM] yuki Downtime

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

[Jun 17, 2009, 7:21 PM] gaua Downtime

gaua (www442) crashed and was rebooted. Downtime was about 15 minutes.

[Jun 17, 2009, 5:03 PM] gwind Downtime

gwind (www74) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 17, 2009, 4:43 PM] salak Downtime

salak (www397) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 17, 2009, 4:34 PM] migi Downtime

migi (www327) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 17, 2009, 3:59 AM] talang Maintenance Completed

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

[Jun 17, 2009, 3:46 AM] karkar Downtime

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

[Jun 17, 2009, 3:27 AM] talang Planned Maintenance

talang (www391) will be taken down shortly to swap out a failing shadow drive. An additional notice will be posted when the swap is complete.

[Jun 17, 2009, 12:16 AM] ohayou Downtime

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

[Jun 16, 2009, 6:24 PM] whury Downtime

whury (www179) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jun 16, 2009, 5:45 AM] sali, talang Maintenance Completed

The maintenance has been completed for sali (www454). The maintenance for talang (www391) will be completed during the next maintenance window.

[Jun 16, 2009, 4:34 AM] sali, talang Planned Maintenance

sali (www454), talang (www391) will be taken down to replace failing drives. An additional notice will be posted when the maintenance is complete.

[Jun 15, 2009, 11:02 PM] talang Maintenance Completed

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

[Jun 15, 2009, 10:35 PM] talang Emergency Maintenance

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

[Jun 15, 2009, 10:14 PM] DB Server Maintenance Completed

The drive swap for db125 is complete. Downtime was under 10 minutes.

[Jun 15, 2009, 8:46 PM] DB Server Maintenance

We will be taking db125.pair.com down shortly to replace a failing drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Jun 15, 2009, 7:50 PM] tama Downtime

tama (www70) crashed and was rebooted. Downtime was about 10 minutes.

[Jun 15, 2009, 9:52 AM] ezera Downtime

ezera (www281) encountered high load and was reset. Downtime was under 15 minutes.

[Jun 15, 2009, 12:18 AM] zirx Downtime

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

[Jun 14, 2009, 10:59 PM] vert Downtime

vert (www102) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jun 14, 2009, 10:39 PM] eltsi Downtime

eltsi (www459) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 14, 2009, 5:33 PM] dieci Downtime

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

[Jun 13, 2009, 4:04 PM] whury Downtime

whury (www179) encountered an error and rebooted. Total downtime was approximately 5 minutes.

[Jun 13, 2009, 11:50 AM] patru Downtime

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

[Jun 13, 2009, 10:31 AM] saghotta Downtime

saghotta (www259) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Jun 13, 2009, 12:15 AM] muin Downtime

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

[Jun 12, 2009, 3:42 PM] kesa Downtime

kesa (www479) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 12, 2009, 10:56 AM] flure Downtime

flure (www75) encountered an error while in service and needed to be rebooted. Total downtime was less than 15 minutes.

[Jun 11, 2009, 4:48 PM] nuumen Downtime

nuumen (www55) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 11, 2009, 2:25 AM] wawrra Maintenance Completed

The drive swap for wawrra (www109) has been completed. Downtime was under 10 minutes.

[Jun 11, 2009, 2:05 AM] wawrra Planned Maintenance

wawrra (www109) will be taken down to replace failing ShadowDrive. An additional notice will be posted when the maintenance is complete.

[Jun 11, 2009, 12:35 AM] aedde Downtime

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

[Jun 10, 2009, 7:23 PM] aedde Downtime

aedde (www84) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 10, 2009, 3:52 PM] neter Downtime

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

[Jun 10, 2009, 3:13 PM] taupo Downtime

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

[Jun 10, 2009, 12:21 AM] yuki Downtime

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

[Jun 9, 2009, 7:35 PM] ailm Downtime

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

[Jun 9, 2009, 4:42 PM] fearn Downtime

The server fearn (www40) crashed while in service and was reset. Upon booting it required a file system check. Downtime was less than 15 minutes.

[Jun 9, 2009, 12:58 PM] diviy Downtime

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

[Jun 9, 2009, 11:56 AM] dieci Downtime

dieci (www231) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 9, 2009, 11:38 AM] immi Downtime

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

[Jun 9, 2009, 9:12 AM] wokkil Downtime

wokkil (www249) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 9, 2009, 5:15 AM] vepar Downtime

vepar (www201) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jun 9, 2009, 2:24 AM] onn, yuki Maintenance Completed

The drive swap for onn (www29) and yuki (www493) has been completed. Downtime was under 5 minutes each.

[Jun 9, 2009, 1:40 AM] onn, yuki Planned Maintenance

onn, (www29), and yuki (www493) will be taken down to replace failing ShadowDrives. An additional notice will be posted when the maintenance is complete.

[Jun 8, 2009, 11:47 PM] kirei Downtime

kirei (www336) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jun 8, 2009, 6:34 PM] karkar Downtime

karkar (www429) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 8, 2009, 5:09 PM] ailm Downtime

The server ailm (www28) encountered an error while in service and was reset. Downtime was less than 10 minutes.

[Jun 8, 2009, 4:26 AM] poict Downtime

poict (www195) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 8, 2009, 12:12 AM] muin Downtime

muin (www23) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 7, 2009, 2:05 PM] Network Problems Resolved

The faulty distribution switch has been replaced, and connectivity for the affected servers has returned to normal. Total duration of the problem was approximately 30 minutes. We apologize for the inconvenience.

[Jun 7, 2009, 1:41 PM] Network Problems

One of our internal distribution switches is showing signs of failure, including heavy packet loss for servers connected to it. We will be replacing it shortly on an emergency basis. Affected shared user servers are:

upsilon (www13)
chi (www14)
psi (www15)
coll (www22)
nuumen (www55)
scire (www78)
ulwar (www82)
aedde (www84)
sether (www95)
falku (www98)
paat (www100)
wawrra (www109)
xrra (www116)
yuzz (www117)
elhaz (www144)
mhoh (www191)
xebte (www230)
patru (www232)
peswar (www233)
hauda (www234)

[Jun 6, 2009, 10:28 AM] harma Downtime

harma (www50) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 6, 2009, 9:47 AM] tinco Downtime

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

[Jun 6, 2009, 4:19 AM] yitiya Downtime

yitiya (www252) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Jun 5, 2009, 9:39 PM] kishou Downtime

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

[Jun 5, 2009, 2:25 PM] zais Downtime

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

[Jun 5, 2009, 12:24 AM] yuki Downtime

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

[Jun 4, 2009, 3:38 PM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 4, 2009, 2:50 PM] penkwe Downtime

penkwe (www220) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jun 4, 2009, 1:15 PM] sothor Downtime

sothor (www182) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Jun 4, 2009, 10:38 AM] zais Downtime

zais (www89) became unresponsive and needed to be rebooted. Total downtime was about 5 minutes.

[Jun 4, 2009, 5:34 AM] atsui Downtime

atsui (www480) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Jun 4, 2009, 12:43 AM] gao Downtime

gao (www111) encountered an error and was reset. Downtime was about 10 minutes.

[Jun 3, 2009, 6:19 PM] Phone System Outage

Our phone systems suffered an outage at approximately 6:10 PM Eastern which lasted approximately 15 minutes. We have identified the faulty piece of equipment and it will be replaced as part of normal maintenance. No more downtime is expected. We apologize for any inconvenience.

[Jun 3, 2009, 2:53 PM] morx Downtime

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

[Jun 2, 2009, 9:37 PM] irazu Downtime

irazu (www377) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 2, 2009, 7:32 PM] taupo Downtime

taupo (www426) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Jun 2, 2009, 11:27 AM] mirozo Downtime

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

[Jun 2, 2009, 8:47 AM] orxul Maintenance Completed

orxul (www471) now has a 250GB drive. Downtime was under 10 minutes.

[Jun 2, 2009, 5:41 AM] zirx Downtime

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

[Jun 2, 2009, 4:42 AM] orxul Planned Maintenance

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

[Jun 2, 2009, 3:41 AM] ilwe Downtime

ilwe (www81) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 1, 2009, 9:40 PM] gessire Downtime

gessire (www273) crashed and was rebooted. Downtime was under 10 minutes.

[Jun 1, 2009, 9:20 PM] qiorre Downtime

qiorre (www482) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jun 1, 2009, 8:21 PM] usagi Downtime

usagi (www331) encountered an error and was reset. It also required a manual file system check. Downtime was approximately 15 minutes.

[Jun 1, 2009, 3:26 PM] tenshian Downtime

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

[Jun 1, 2009, 1:53 PM] nyartu Downtime

nyartu (www254) encountered an error and was reset. Downtime was about 5 minutes.

[Jun 1, 2009, 1:20 PM] xoopi Downtime

xoopi (www266) crashed under heavy load and had to be restarted. Downtime was about 10 minutes.

[Jun 1, 2009, 12:46 PM] erraj Downtime

erraj (www213) encountered an error and was reset. Downtime was approximately 10 minutes.

[Jun 1, 2009, 12:18 AM] xebte Downtime

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

[May 31, 2009, 2:44 PM] namt Downtime

namt (www196) encountered an error and was reset. Downtime was under 10 minutes.

[May 31, 2009, 11:20 AM] xebte Downtime

xebte (www230) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 30, 2009, 9:33 PM] maborym Downtime

maborym (www204) crashed and was rebooted. Downtime was under 10 minutes.

[May 30, 2009, 12:49 PM] cuzea Maintenance Completed

The chassis swap on cuzea (www94) has been completed. The server is now an Intel Core 2 6420 with 4GB of RAM. Total downtime for the maintenance was about 10 minutes.

[May 30, 2009, 12:20 PM] cuzea Emergency Maintenance

cuzea (www94) will be taken down shortly to replace a failing chassis. Another notice will be posted once the maintenance has been completed.

[May 30, 2009, 8:27 AM] tinne Downtime

tinne (www21) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 30, 2009, 5:00 AM] ulwar Downtime

ulwar (www82) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[May 29, 2009, 5:40 PM] ninin Downtime

ninin (www322) crashed and was rebooted. Downtime was under 5 minutes.

[May 29, 2009, 4:56 PM] hidari Downtime

hidari (www346) crashed and was rebooted. Downtime was under 20 minutes.

[May 29, 2009, 3:28 PM] cuzea Maintenance Completed

The drive swap on cuzea (www94) has been completed. Downtime was less than 5 minutes.

[May 29, 2009, 3:06 PM] cuzea Emergency Maintenance

cuzea (www94) will be taken down shortly to replace a failing ShadowDrive. A second notice will be posted once the maintenance is complete.

[May 29, 2009, 12:39 PM] ajilan Downtime

ajilan (www384) became unresponsive due to high load and was reset. Downtime was 15 minutes.

[May 29, 2009, 11:17 AM] naam Downtime

naam (www114) became unresponsive while in service and was reset. Downtime was approximately 10 minutes.

[May 29, 2009, 6:29 AM] cuzea Maintenance Completed

The drive swap on cuzea (www94) has been completed. Downtime was less than 5 minutes.

[May 29, 2009, 6:27 AM] tama Downtime

tama (www70) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[May 29, 2009, 1:30 AM] cuzea Planned Maintenance

cuzea (www94) will be taken down later to swap out a failing drive. Downtime should be about 5 minutes or less. An additional notice will be posted when this has been completed.

[May 28, 2009, 10:43 PM] hidari Downtime

hidari (www346) crashed and was rebooted. Downtime was under 10 minutes.

[May 28, 2009, 4:33 PM] wedhans Downtime

wedhans (www483) was reset to clear an error condition. Downtime was less than 5 minutes.

[May 28, 2009, 12:14 PM] upsilon Downtime

upsilon (www13) became unresponsive while in service and was reset. Downtime was approximately 10 minutes.

[May 28, 2009, 12:11 PM] azul Downtime

azul (www375) became unresponsive under high load, and needed to be rebooted. Total downtime was approximately 15 minutes.

[May 28, 2009, 1:40 AM] wredhor Maintenance Completed

The cable swap on wredhor (www76) had been completed. Downtime was less than 5 minutes.

[May 28, 2009, 1:07 AM] wredhor Planned Maintenance

wredhor (www76) will be taken down to replace a failing drive cable. Downtime is expected to be less than 10 minutes.

[May 28, 2009, 12:57 AM] oynos Maintenance Completed

The drive upgrade on oynos (www218) is complete. The primary drive is now a 250GB SATA drive.

[May 27, 2009, 11:07 PM] tyllur Maintenance Completed

The drive swap on tyllur (www285) has been completed. It now has a 160GB primary drive. Downtime was under 10 minutes.

[May 27, 2009, 9:13 PM] oynos Planned Maintenance

Later tonight, oynos (www218) will be taken down for a drive upgrade. There will be two brief periods of downtime. An additional notice will be posted once the maintenance is complete.

[May 27, 2009, 9:03 PM] tyllur Planned Maintenance

Later tonight, tyllur (www285) will be taken down to swap out a failing drive. An additional notice will be posted once this maintenance is completed.

[May 27, 2009, 8:16 PM] biont Downtime

biont (www174) crashed and was rebooted. Downtime was under 10 minutes.

[May 27, 2009, 6:35 PM] batur Downtime

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

[May 27, 2009, 9:26 AM] mirozo Downtime

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

[May 27, 2009, 12:22 AM] zirx Downtime

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

[May 26, 2009, 8:52 PM] bganat Downtime

bganat (www481) encountered an error and was reset. Downtime was about 5 minutes.

[May 26, 2009, 2:24 PM] izalc Downtime

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

[May 26, 2009, 2:07 PM] karkar Downtime

karkar (www429) encountered an error and was reset. It also required a manual file system check. Downtime was approximately 15 minutes.

[May 26, 2009, 1:21 PM] hidari Downtime

hidari (www346) crashed under heavy load and had to be rebooted. Downtime was under 5 minutes.

[May 26, 2009, 9:38 AM] sumbing Maintenance Completed

sumbing (www393) now has a new ShadowDrive. Downtime was under 10 minutes.

[May 26, 2009, 9:26 AM] sumbing Emergency Maintenance

sumbing (www393) will be taken down shortly to swap out a failing shadow drive. A second notice will be posted once the maintenance is complete.

[May 26, 2009, 6:32 AM] isris, sumbing Maintenance Completed

isris (www149) and sumbing (www393) both have new ShadowDrives. Downtime was under 10 minutes each.

[May 26, 2009, 5:49 AM] isris, sumbing Planned Maintenance

isris (www149) and sumbing (www393) will be taken down shortly to replace a failing drive. Downtime should be under 10 minutes. An additional notice will be posted when the maintenance is complete.

[May 26, 2009, 1:29 AM] aerre Downtime

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

[May 26, 2009, 12:33 AM] omega Downtime

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

[May 26, 2009, 12:31 AM] yuki Downtime

yuki (www493) encountered an error and was reset. It also required a manual file system check. Downtime was approximately 10 minutes.

[May 26, 2009, 12:30 AM] zirx Downtime

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

[May 25, 2009, 11:42 PM] chi Downtime

chi (www14) crashed under heavy load and had to be rebooted. Downtime was under 10 minutes.

[May 25, 2009, 4:40 PM] gnaaste Downtime

gnaaste (www79) crashed under heavy load and had to be rebooted. Downtime was under 10 minutes.

[May 25, 2009, 3:21 PM] bganat Downtime

bganat (www481) encountered an error and was reset. It also required a manual disk check and repair. Downtime was approximately 10 minutes.

[May 25, 2009, 4:27 AM] dair Downtime

dair (www20) Encountered an error and was reset. Downtime was about 5 minutes.

[May 23, 2009, 11:23 PM] enore Downtime

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

[May 23, 2009, 10:16 PM] biont Downtime

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

[May 23, 2009, 10:09 PM] bagana Downtime

bagana (www431) encountered an error and was reset. Downtime was less than 5 minutes.

[May 23, 2009, 4:53 PM] penkwe Downtime

penkwe (www220) encountered an error and was reset. Downtime was less than 5 minutes.

[May 22, 2009, 9:47 PM] poict Downtime

poict (www195) was reset to clear an error condition. Downtime was about 5 minutes.

[May 22, 2009, 5:58 PM] akai Downtime

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

[May 22, 2009, 4:18 PM] jaane Downtime

The server jaane (www261) crashed due to a high load and was rebooted. The total downtime was approximately 10 minutes.

[May 22, 2009, 10:59 AM] ifin Downtime

ifin (www36) encountered an error while in service and needed to be rebooted. Total downtime was approximately 15 minutes.

[May 22, 2009, 12:24 AM] zirx Downtime

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

[May 21, 2009, 5:28 PM] uruz Downtime

uruz (www135) encountered an error and was reset. While the server was down and additional 1GB of RAM was added to the server for a total of 3GB or RAM.

[May 21, 2009, 4:35 PM] uruz Downtime

uruz (www135) encountered an error and was reset. Downtime was about 5 minutes.

[May 21, 2009, 2:17 PM] zirx Downtime

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

[May 21, 2009, 2:03 PM] cenena Downtime

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

[May 21, 2009, 8:52 AM] roku Downtime

roku (www343) became unresponsive under high load and needed to be rebooted. Total downtime was under 20 minutes.

[May 21, 2009, 3:59 AM] ilceille Downtime

ilceille (www189) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[May 20, 2009, 5:22 PM] scire Downtime

scire (www78) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[May 20, 2009, 4:07 PM] hwesta Downtime

hwesta (www51) encountered high load and was reset. Downtime was about 10 minutes.

[May 20, 2009, 4:05 PM] fearn Downtime

fearn (www40) encountered high load and crashed while in service. Downtime was about 10 minutes.

[May 20, 2009, 5:37 AM] dyyme Downtime

dyyme (www71) encountered an error and was reset. Downtime was about 5 minutes.

[May 20, 2009, 2:35 AM] thuule Downtime

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

[May 20, 2009, 12:18 AM] aedde Downtime

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

[May 19, 2009, 10:35 PM] morx Downtime

morx (www198) crashed and was reset. Downtime was about 10 minutes.

[May 19, 2009, 8:52 PM] diviy Downtime

diviy (www217) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 19, 2009, 4:39 PM] aedde Downtime

The server aedde (www84) encountered an error and was rebooted. The total downtime was under 10 minutes.

[May 19, 2009, 12:28 PM] midori Downtime

midori (www492) encountered an error and reset. Downtime was about 5 minutes.

[May 19, 2009, 9:54 AM] erraj Downtime

erraj (www213) encountered an error and was reset. Downtime was under 10 minutes.

[May 19, 2009, 8:11 AM] lopevi Downtime

lopevi (www445) encountered an error and was reset. Downtime was under 10 minutes.

[May 19, 2009, 7:56 AM] sasi Downtime

sasi (www207) encountered an error and reset. Downtime was about 5 minutes.

[May 19, 2009, 7:29 AM] zirx Downtime

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

[May 19, 2009, 6:50 AM] otok Downtime

otok (www131) encountered an error and reset. Downtime was about 5 minutes.

[May 19, 2009, 5:19 AM] cuzea Maintenance Completed

cuzea (www94) the drive cable swap is complete. Downtime was less than 5 minutes.

[May 19, 2009, 4:57 AM] cuzea Planned Maintenance

cuzea (www94) will be taken down shortly to replace a failing drive cable. Downtime is expected to be less than 10 minutes.

[May 19, 2009, 2:38 AM] mirozo Downtime

mirozo (www257) encountered an error and reset. Downtime was about 5 minutes.

[May 19, 2009, 1:40 AM] sali Downtime

sali (www454) encountered an error and was reset. Downtime was about 10 minutes.

[May 18, 2009, 10:35 PM] karkar Downtime

karkar (www429) crashed and was reset. Downtime was about 5 minutes.

[May 18, 2009, 10:10 PM] delsi Maintenance Completed

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

[May 18, 2009, 9:11 PM] delsi Planned Maintenance

delsi (www206) 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 18, 2009, 5:19 PM] karkar Downtime

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

[May 18, 2009, 4:45 PM] delsi Downtime

The server delsi (www206) crashed and required an extensive file system check. Downtime was about 20 minutes.

[May 18, 2009, 4:01 PM] xoopi Downtime

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

[May 18, 2009, 5:00 AM] tinco Downtime

tinco (www41) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 18, 2009, 12:16 AM] yuki Downtime

yuki (www493) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 17, 2009, 6:30 PM] uruz Downtime

uruz (www135) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[May 17, 2009, 3:53 PM] elhaz Downtime

elhaz (www144) crashed due to high load and was reset. Downtime was about 5 minutes.

[May 17, 2009, 10:46 AM] ainaz Downtime

ainaz (www221) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 17, 2009, 4:42 AM] poict Downtime

poict (www195) encountered an error and was reset. Downtime was about 5 minutes.

[May 17, 2009, 12:28 AM] muin Downtime

muin (www23) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[May 16, 2009, 10:26 AM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 16, 2009, 10:24 AM] borro Downtime

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

[May 16, 2009, 5:16 AM] isris Maintenance Completed

isris (www194) the drive cable swap is complete. Downtime was less than 5 minutes.

[May 16, 2009, 4:34 AM] isris Planned Maintenance

isris (www194) will be taken down shortly to replace a failing drive cable. Downtime is expected to be less than 10 minutes.

[May 16, 2009, 12:20 AM] fayev Downtime

fayev (www365) encountered an error and was reset. Downtime was about 10 minutes.

[May 15, 2009, 9:07 PM] delsi Downtime

delsi (www206) was reset to clear an error condition. A manual file system check was performed before bringing the server online. Downtime was about 20 minutes.

[May 15, 2009, 7:48 PM] Network Problems

Between approximately 7:10 PM and 7:20 PM Eastern, we experienced an outage of an internal network router, causing problems reaching a subset of our network. The problem has been isolated and is being monitored -- we have additional equipment online and ready to take over should it become necessary. We apologize for the inconvenience.

[May 15, 2009, 6:59 AM] bganat Downtime

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

[May 15, 2009, 6:52 AM] ailm Downtime

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

[May 15, 2009, 12:23 AM] muin Downtime

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

[May 14, 2009, 4:31 PM] wunjo Downtime

wunjo (www140) became unresponsive and was reset. Downtime was about 5 minutes.

[May 14, 2009, 3:29 PM] delsi Downtime

delsi (www206) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 14, 2009, 8:01 AM] chi Downtime

chi (www14) encountered an error and was reset. Downtime was about 10 minutes.

[May 14, 2009, 12:07 AM] salak Downtime

salak (www397) encountered an error and was reset. Downtime was less than 5 minutes.

[May 13, 2009, 12:54 PM] tama Downtime

tama (www70) crashed and was reset. Downtime was under 10 minutes.

[May 12, 2009, 8:13 PM] yanta Downtime

yanta (www67) became unresponsive and had to be rebooted. Downtime as about 15 minutes.

[May 12, 2009, 2:41 AM] omicron Downtime

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

[May 12, 2009, 12:27 AM] muin Downtime

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

[May 11, 2009, 11:01 PM] kesa Downtime

kesa (www479) crashed and was rebooted. Downtime was 10 minutes.

[May 11, 2009, 10:01 PM] gebo Downtime

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

[May 11, 2009, 7:51 PM] Server Reboots Completed

Tonight's maintenance is now complete.

[May 11, 2009, 5:29 PM] Server Reboots

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

[May 11, 2009, 9:39 AM] naam Downtime

naam (www114) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[May 11, 2009, 3:26 AM] itske Downtime

itske (www472) became unresponsive while in service and was reset. Total downtime was under 20 minutes.

[May 11, 2009, 1:53 AM] aoujw Downtime

aoujw (www366) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 10, 2009, 12:38 PM] tama Downtime

tama (www70) encountered an error and was reset. Downtime was under 15 minutes.

[May 10, 2009, 12:30 PM] kayan Downtime

kayan (www133) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[May 9, 2009, 12:00 PM] uruz Downtime

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

[May 9, 2009, 11:06 AM] theta Downtime

theta (www4) became unresponsive due to high load and was reset. A manual file system check was preformed before bringing back online, downtime was 20 minutes.

[May 9, 2009, 4:33 AM] eite Downtime

eite (www38) became unresponsive and had to be rebooted. Downtime as about 5 minutes.

[May 9, 2009, 2:26 AM] omega Downtime

omega (www16) encountered an error and was reset. Downtime was about 10 minutes.

[May 8, 2009, 7:56 PM] delsi Downtime

delsi (www206) crashed and was rebooted, and required a manual file system check. Downtime was under 20 minutes.

[May 8, 2009, 3:23 PM] amutka Downtime

amutka (www369) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 8, 2009, 11:10 AM] ynilo Downtime

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

[May 8, 2009, 10:04 AM] gyaku Emergency Maintenance

gyaku (www351) became unresponsive while in service, and was given an immediate chassis swap. The server is now a Pentium 4 3.8GHz with 2GB of RAM. Total downtime for the maintenance was less than 30 minutes.

[May 8, 2009, 12:15 AM] flure Downtime

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

[May 7, 2009, 10:10 PM] kaarei Maintenance Completed

The chassis swap on kaarei (www300) has been completed. The server is now a Pentium 4 3.8GHz with 3GB of RAM. Total downtime was about 5 minutes.

[May 7, 2009, 9:36 PM] kaarei Planned Maintenance

kaarei (www300) will be taken down shortly for a chassis swap. Downtime should be 15 minutes or less, and an additional notice will be posted once this has been completed.

[May 7, 2009, 6:49 PM] galeras Downtime

galeras (www451) was reset to clear an error condition. Downtime was less than 5 minutes.

[May 7, 2009, 3:56 PM] kuwae Downtime

kuwae (www446) became unresponsive due to high load and was reset. Downtime was 25 minutes.

[May 7, 2009, 3:09 PM] kuwae Downtime

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

[May 7, 2009, 2:22 PM] gyaku Downtime

gyaku (www351) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 7, 2009, 1:58 PM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 7, 2009, 8:19 AM] eeoth Downtime

eeoth (www85) encountered an error while in service and reset. Total downtime was about 5 minutes.

[May 7, 2009, 1:20 AM] flure Downtime

flure (www75) encountered an error and was reset. Downtime was under 10 minutes.

[May 6, 2009, 10:38 PM] neled Downtime

neled (www127) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[May 6, 2009, 9:03 PM] gyaku Downtime

gyaku (www351) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[May 6, 2009, 6:08 PM] uinus Downtime

uinus (www228) crashed and was rebooted. Downtime was under 10 minutes.

[May 6, 2009, 5:07 PM] flure Downtime

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

[May 6, 2009, 4:28 PM] xoopi Downtime

xoopi (www266) encountered an error and was reset. Downtime was under 10 minutes.

[May 6, 2009, 11:27 AM] musume Downtime

musume (www490) crashed and was reset. Downtime was about 5 minutes.

[May 6, 2009, 6:57 AM] immi Downtime

immi (www457) crashed and required a manual file system check. Downtime was about 20 minutes.

[May 6, 2009, 12:20 AM] delsi Downtime

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

[May 5, 2009, 11:06 PM] dieci Downtime

dieci (www231) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[May 5, 2009, 11:17 AM] salak Downtime

salak (www397) crashed and was reset. Downtime was under 10 minutes.

[May 5, 2009, 4:34 AM] yali, uusu, immi, orxul, bganat, kelut Maintenance Completed

Tonight's upgrades have been completed. yali (www382) now has a 250GB drive, uusu (www412) now has a 200GB drive, and immi (www457), orxul (www471), and bganat (www481) now have 160GB drives.

During the maintenance, kelut (www400) began showing errors on its Shadow Drive, so it was swapped as well. Downtime for each server was 5 minutes or less.

[May 5, 2009, 2:14 AM] aoujw Downtime

aoujw (www366) encountered an error and was reset. Downtime was about 10 minutes.

[May 5, 2009, 1:27 AM] yali, uusu, immi, orxul, bganat Planned Maintenance

yali (www382), uusu (www412), immi (www457), orxul (www471), and bganat (www481) will be taken down shortly for drive upgrades. Downtime for each server should be 5 minutes or less. An additional notice will be posted when this has been completed.

[May 4, 2009, 8:01 PM] gao Downtime

gao (www111) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[May 4, 2009, 2:50 PM] cuzea Downtime

cuzea (www94) crashed and required a manual file system check. Downtime was about 20 minutes.

[May 4, 2009, 2:40 PM] gao Downtime

gao (www111) encountered an error and was reset. Downtime was under 10 minutes.

[May 4, 2009, 1:27 PM] allatu Downtime

allatu (www197) became unresponsive while in service and was reset. Downtime was 10 minutes.

[May 4, 2009, 1:06 PM] neter Downtime

neter (www132) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[May 4, 2009, 9:36 AM] zais Downtime

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

[May 3, 2009, 7:28 AM] ngatwo Downtime

ngatwo (www115) encountered an error and was reset. Downtime was about 5 minutes.

[May 2, 2009, 10:07 PM] yume Emergency Maintenance

yume (www334) experienced a hardware failure and received a chassis swap. The server is now a Pentium 4 3.4GHz with 3GB of RAM. Total downtime was about 5 minutes.

[May 2, 2009, 10:05 PM] kavachi Downtime

kavachi (www437) encountered an error and was reset. Downtime was under 5 minutes.

[May 2, 2009, 3:29 PM] akket Downtime

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

[May 2, 2009, 4:42 AM] upsilon Downtime

upsilon (www13) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[May 1, 2009, 6:24 PM] yume Downtime

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

[May 1, 2009, 5:09 PM] bganat Downtime

bganat (www481) crashed and was rebooted. Downtime was under 10 minutes.

[May 1, 2009, 2:56 PM] onn Downtime

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

[May 1, 2009, 11:44 AM] zirx Downtime

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

[Apr 30, 2009, 8:45 PM] orvni Downtime

orvni (www205) was reset to clear an error condition. Downtime was less than 5 minutes.

[Apr 30, 2009, 1:59 PM] kindoi Downtime

kindoi (www308) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Apr 30, 2009, 1:06 PM] bganat Downtime

bganat (www481) reset itself and was online within a few minutes.

[Apr 30, 2009, 1:00 PM] soputan Downtime

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

[Apr 30, 2009, 1:24 AM] traad Downtime

traad (www478) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 30, 2009, 12:16 AM] muin Downtime

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

[Apr 29, 2009, 1:24 PM] derba Downtime

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

[Apr 29, 2009, 12:26 PM] aedde Downtime

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

[Apr 29, 2009, 9:45 AM] kesa Downtime

kesa (www479) encountered an error and needed to be reset. Downtime was less than 5 minutes.

[Apr 29, 2009, 7:28 AM] tinco Maintenance Completed

The maintenance on tinco (www41) has been completed. It now has a new 200GB drive. Downtime was about 5 minutes.

[Apr 29, 2009, 6:56 AM] tinco Planned Maintenance

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

[Apr 29, 2009, 5:10 AM] bellat, tousko, cereme, ninin, nwalme Maintenance Completed

Tonight's maintenance has been completed. tousko (www291), cereme (www398), ninin (www322), and nwalme (www57) now have 160GB drives, and bellat (www101) now has a new 250GB drive. Downtime for each server was 5 minutes or less.

[Apr 29, 2009, 3:30 AM] falku Downtime

falku (www98) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 29, 2009, 3:16 AM] ur Downtime

ur (www30) encountered an error and reset. Downtime was about 10 minutes.

[Apr 29, 2009, 2:07 AM] bellat, tousko, cereme, ninin, nwalme Planned Maintenance

bellat (www101) will be taken down shortly to swap out a failing drive. tousko (www291), cereme (www398), ninin (www322), and nwalme (www57) will be taken down for drive upgrades. Total downtime should be less than 5 minutes per server. An additional notice will be posted when this has been completed.

[Apr 28, 2009, 6:10 PM] nyartu Downtime

The server nyartu (www254) crashed due to an error. New RAM was swapped into the server as the error likely came from a failing RAM module. The server now has 4GB DDR2-5300 RAM. The total downtime was under 10 minutes.

[Apr 28, 2009, 4:49 PM] neko Emergency Maintenance

Emergency maintenance was performed on neko (www356) due to a failing network card. The server is now a Pentium 4 3.8GHz with 4GB DDR2 RAM. The total downtime for this maintenance was under 20 minutes.

[Apr 28, 2009, 2:40 PM] kappa Downtime

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

[Apr 28, 2009, 2:31 PM] izalc Downtime

izalc (www378) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Apr 28, 2009, 2:05 PM] tyllur Downtime

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

[Apr 28, 2009, 12:51 PM] kfin Downtime

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

[Apr 28, 2009, 10:02 AM] bganat Downtime

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

[Apr 28, 2009, 6:48 AM] tinco Downtime

tinco (www41) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 28, 2009, 12:33 AM] muin Downtime

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

[Apr 27, 2009, 4:17 PM] neko Downtime

The server neko(www356) crashed due to an error and was rebooted. The total downtime was under 10 minutes.

[Apr 27, 2009, 1:45 PM] vilya Downtime

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

[Apr 27, 2009, 1:03 PM] douzo Downtime

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

[Apr 27, 2009, 12:14 PM] ruis Downtime

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

[Apr 27, 2009, 11:19 AM] aedde Downtime

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

[Apr 26, 2009, 9:37 PM] tama Downtime

tama (www70) crashed and was rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was about 20 minutes.

[Apr 26, 2009, 7:59 AM] kaarei Downtime

kaarei (www300) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Apr 25, 2009, 2:38 PM] thuule Downtime

thuule (www49) encountered an error while in service, and needed to be reset. Total downtime was less than 10 minutes.

[Apr 25, 2009, 2:33 PM] zhun Downtime

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

[Apr 25, 2009, 8:36 AM] aqquz Downtime

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

[Apr 24, 2009, 11:06 PM] kappa Downtime

kappa (www6) was reset to clear an error condition. Downtime was less than 5 minutes.

[Apr 24, 2009, 1:41 PM] oku Downtime

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

[Apr 23, 2009, 11:02 PM] paell Downtime

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

[Apr 23, 2009, 10:16 PM] sali Downtime

sali (www454) was rebooted to clear an error condition, and required a manual file system check. Downtime was under 25 minutes.

[Apr 23, 2009, 8:40 PM] fithwor Downtime

fithwor (www222) became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 23, 2009, 8:25 PM] midhae Maintenance Completed

The maintenance on midhae (www278) has been completed. Downtime was under 10 minutes.

[Apr 23, 2009, 7:02 PM] midhae Planned Maintenance

Tonight after 8PM Eastern, we will be taking midhae (www278) down to swap out a failing Shadow Drive. Downtime should not exceed 10 minutes.

[Apr 23, 2009, 5:24 PM] eldfell Downtime

eldfell (www450) became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 23, 2009, 12:05 PM] aerre Downtime

aerre (www185) became unresponsive while in service and needed to be rebooted. Total downtime was about 10 minutes.

[Apr 23, 2009, 11:55 AM] ajilan Downtime

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

[Apr 23, 2009, 7:22 AM] kwarcu Downtime

kwarcu (www293) became unresponsive and had to be rebooted. Downtime was less than 10 minutes.

[Apr 22, 2009, 7:31 PM] shen Downtime

shen (www88) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 21, 2009, 6:17 PM] tama Downtime

tama (www70) crashed due to a faulty RAM module. The RAM was replaced. This server still has 2GB of RAM. Downtime was about 15 minutes.

[Apr 21, 2009, 1:09 PM] saghotta Downtime

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

[Apr 21, 2009, 8:00 AM] ungwe Downtime

ungwe (www48) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 21, 2009, 5:42 AM] tama Downtime

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

[Apr 21, 2009, 4:40 AM] beith Maintenance Completed

The chassis upgrade on beith (www17) has been completed. It is now a Core 2 E6420 with 2GB of RAM. Total downtime was less than 10 minutes.

[Apr 21, 2009, 3:55 AM] beith Planned Maintenance

beith (www17) will be taken down shortly for a chassis upgrade. Downtime should be 15 minutes or less, and an additional notice will be posted when this has been completed.

[Apr 21, 2009, 12:22 AM] muin Downtime

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

[Apr 20, 2009, 2:52 PM] kesa Downtime

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

[Apr 20, 2009, 1:10 PM] sether Downtime

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

[Apr 20, 2009, 10:52 AM] jaane Downtime

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

[Apr 19, 2009, 10:24 PM] aedde Downtime

aedde (www84) crashed due to a faulty RAM module. The RAM was replaced. This server still has 2GB of RAM. Downtime was about 15 minutes.

[Apr 19, 2009, 9:25 PM] yume Downtime

yume (www334) reset itself and was online within a few minutes.

[Apr 19, 2009, 4:53 PM] shen Downtime

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

[Apr 19, 2009, 6:13 AM] aerre Downtime

aerre (www185) Encountered an error during operation and was reset. Downtime was about 5 minutes.

[Apr 19, 2009, 3:09 AM] glikk Downtime

glikk (www119) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 18, 2009, 1:24 AM] saakal Downtime

saakal (www264) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Apr 17, 2009, 11:45 AM] cuzea Downtime

cuzea (www94) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 15 minutes.

[Apr 17, 2009, 12:40 AM] muin Downtime

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

[Apr 16, 2009, 5:58 PM] gief Downtime

gief (www178) encountered an error and was reset. Downtime was about 5 minutes.

[Apr 16, 2009, 1:53 PM] quesse Downtime

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

[Apr 16, 2009, 11:44 AM] tinne Downtime

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

[Apr 16, 2009, 3:40 AM] tehun Downtime

tehun (www226) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 16, 2009, 1:03 AM] aerre Downtime

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

[Apr 15, 2009, 3:50 PM] rilwi Downtime

The server rilwi (www347) crashed while in service and was reset. The total downtime was about 10 minutes.

[Apr 15, 2009, 2:59 PM] bganat Downtime

The server bganat (www481) crashed due to a faulty RAM module. The RAM was replaced. This server now has 4GB of DDR2 memory.

[Apr 15, 2009, 1:46 PM] bganat Downtime

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

[Apr 15, 2009, 10:10 AM] saghotta Downtime

saghotta (www259) became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 15, 2009, 9:58 AM] fayev Downtime

fayev (www365) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Apr 15, 2009, 4:55 AM] ajilan, aster, amutka Maintenance Completed

Tonight's upgrades have been completed. ajilan (www384), aster (www96), and amutka (www369) have each been upgraded to a Core 2 E6420 with 2GB of RAM. Downtime for each server was less than 10 minutes.

[Apr 15, 2009, 2:47 AM] ajilan, aster, amutka Planned Maintenance

ajilan (www384), aster (www96), and amutka (www369) will be taken down shortly for chassis upgrades. Downtime for each server should be 15 minutes or less. An additional notice will be posted when this has been completed.

[Apr 15, 2009, 12:29 AM] muin Downtime

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

[Apr 14, 2009, 10:07 PM] ittsui Downtime

ittsui (www323) reset itself and was online within a few minutes.

[Apr 14, 2009, 2:38 PM] onn Downtime

onn (www29) crashed and was rebooted. Downtime was less than 5 minutes.

[Apr 14, 2009, 2:11 PM] oomur Downtime

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

[Apr 14, 2009, 11:33 AM] emlis Downtime

emlis (www216) Became unresponsive during operation and was reset. Downtime was about 10 minutes.

[Apr 14, 2009, 8:47 AM] seyyav Downtime

seyyav (www238) Became unresponsive during operation and was reset. Downtime was about 5 minutes.

[Apr 14, 2009, 3:58 AM] seyyav Maintenance Completed

The chassis upgrade on seyyav (www238) has been completed. It is now a Core2 E6420 with 2GB of RAM. Total downtime was about 15 minutes.

[Apr 14, 2009, 3:26 AM] seyyav Planned Maintenance

seyyav (www238) will be taken down shortly for a chassis upgrade. Total downtime should be 10 minutes or less. An additional notice will be posted when this has been completed.

[Apr 13, 2009, 10:54 PM] seyyav Downtime

seyyav (www238) Became unresponsive during service and was reset. Downtime was about 5 minutes.

[Apr 13, 2009, 3:37 PM] delsi Downtime

The server delsi (www206) crashed due to a hardware error. A suspected bad 2GB DDR2 RAM module was replaced with another new 2GB DD2 module. The total downtime was under 15 minutes.

[Apr 13, 2009, 11:25 AM] ydhu Downtime

ydhu (www83) encountered an error and rebooted itself. Downtime was less than 5 minutes.

[Apr 13, 2009, 11:22 AM] soputan Downtime

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

[Apr 13, 2009, 10:19 AM] soputan Downtime

soputan (www408) Became unresponsive during service and was reset. Downtime was about 15 minutes.

[Apr 13, 2009, 8:43 AM] ilwe Downtime

ilwe (www81) Became unresponsive during operation and was reset. Downtime was about 5 minutes.

[Apr 13, 2009, 6:49 AM] zirx Downtime

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

[Apr 13, 2009, 4:14 AM] seyyav Downtime

seyyav (www238) Became unresponsive during service and was reset. Downtime was about 5 minutes.

[Apr 13, 2009, 2:19 AM] seyyav Downtime

seyyav (www238) Became unresponsive during service and was reset. Downtime was about 5 minutes.

[Apr 13, 2009, 1:08 AM] seyyav Downtime

seyyav (www238) Became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 12, 2009, 9:31 PM] diviy Downtime

diviy (www217) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 12, 2009, 10:08 AM] fiann Downtime

fiann (www188) became unresponsive while in service and needed to be rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was about 20 minutes.

[Apr 12, 2009, 9:17 AM] omega Downtime

omega (www16) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Apr 12, 2009, 7:14 AM] seyyav Downtime

seyyav (www238) became unresponsive due to high load and was reset. Downtime was less than 10 minutes.

[Apr 12, 2009, 12:57 AM] dukoni Downtime

dukoni (www305) Encountered an error and was reset. Downtime was about 5 minutes.

[Apr 11, 2009, 5:07 PM] akutan Maintenance Completed

The drive swap on akutan (www361) has been completed. It now has a 160GB primary drive.

[Apr 11, 2009, 4:23 PM] akutan Planned Maintenance

This afternoon, akutan (www361) will be taken down briefly for a drive swap. Downtime should not exceed 10 minutes. An additional notice will be posted once the maintenance is complete.

[Apr 11, 2009, 11:28 AM] seyyav Downtime

seyyav (www238) became unresponsive due to high load and was reset. Downtime was less then 10 minutes.

[Apr 10, 2009, 11:56 PM] ohayou Downtime

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

[Apr 10, 2009, 7:38 PM] sitkin Downtime

sitkin (www373) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 10, 2009, 6:02 PM] bunepi Downtime

bunepi (www318) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Apr 10, 2009, 11:57 AM] seyyav Downtime

seyyav (www238) encountered an error and was reset. Downtime was less than 10 minutes.

[Apr 10, 2009, 9:26 AM] ur Downtime

ur (www30) encountered an error and reset. Downtime was less than 5 minutes.

[Apr 10, 2009, 6:17 AM] eiga Maintenance Completed

The shadow drive swap for eiga (www326) is complete. Downtime was less then 10 minutes.

[Apr 10, 2009, 5:51 AM] Emergency Maintenance

eiga (www326) will be taken down shortly to replace a failing shadow drive. An additional notice will be posted when the swap is complete.

[Apr 10, 2009, 3:12 AM] flure Downtime

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

[Apr 10, 2009, 12:08 AM] zirx Downtime

zirx (www106) crashed and was rebooted. Downtime was under 5 minutes.

[Apr 9, 2009, 9:39 PM] flure Downtime

flure (www75) crashed and was rebooted. Downtime was about 10 minutes.

[Apr 9, 2009, 11:57 AM] beeoro Downtime

beeoro (www69) became unresponsive while in service and needed to be rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was about 25 minutes.

[Apr 9, 2009, 4:47 AM] sowilu, zais, masilma Maintenance Completed

Tonight's upgrades have been completed. sowilu (www145) now has a 200GB drive, zais (www89) now has a 250GB drive, and masilma (www307) is now a Core 2 E6420 with 2GB of RAM. Downtime for each server was less than 10 minutes.

[Apr 9, 2009, 2:14 AM] sowilu, zais, masilma Planned Maintenance

sowilu (www145) and zais (www89) will be taken down shortly to swap out failing drives. Additionally, masilma (www307) will be taken down for a chassis upgrade. Downtime for each server should be 10 minutes or less. An additional notice will be posted when this has been completed.

[Apr 8, 2009, 9:34 PM] yume Downtime

yume (www334) encountered an error and was reset. Downtime was less than 5 minutes.

[Apr 8, 2009, 8:37 PM] uinus Downtime

uinus (www228) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 8, 2009, 7:27 PM] kaba Downtime

kaba (www394) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 8, 2009, 6:02 PM] marapi Downtime

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

[Apr 8, 2009, 3:58 PM] dieci Downtime

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

[Apr 8, 2009, 2:06 PM] wunjo Downtime

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

[Apr 8, 2009, 1:52 PM] quan Downtime

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

[Apr 8, 2009, 1:22 PM] Server Downtimes

Earlier today, an upgrade to ImageMagick was made across all shared user servers. Although the new version had been in testing for some time, including a successful test of 50 shared servers yesterday, an interaction between the new version and at least one other package caused multiple servers to run out of swap space and require rebooting. Affected servers were:

gamma (www2)
ailm (www28)
ando (www45)
wawrra (www109)
ngatwo (www115)
uumor (www159)
akket (www211)
mirozo (www257)
sekweta (www258)
thenge (www270)
kohala (www389)
sirung (www409)
taupo (www426)
aoba (www443)
abej (www464)

The upgrade has been reverted on all servers. We apologize for any inconvenience.

[Apr 8, 2009, 9:56 AM] xoopi Downtime

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

[Apr 8, 2009, 4:11 AM] aedde, ainaz, derba Maintenance Completed

The chassis upgrades on aedde (www84), ainaz (www221), and derba (www104) have been completed. Each server is now a Core 2 E6420 with 2GB of RAM. Downtime for each server was less than 10 minutes.

[Apr 8, 2009, 2:41 AM] aedde, ainaz, derba Planned Maintenance

aedde (www84), ainaz (www221), and derba (www104) will be taken down shortly for chassis upgrades. Downtime for each server should be 15 minutes or less. An additional notice will be posted when this has been completed.

[Apr 8, 2009, 12:22 AM] yuki Downtime

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

[Apr 7, 2009, 10:36 PM] hachi Downtime and RAM Upgrade

hachi (www344) became unresponsive while in service and required a reboot. While the server was down, 1 GB of RAM was added for a total of 2GB. Total downtime was under 10 minutes.

[Apr 7, 2009, 10:10 PM] hachi Downtime

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

[Apr 7, 2009, 7:39 PM] kesa Downtime

kesa (www479) crashed and was rebooted. Downtime was under 10 minutes.

[Apr 7, 2009, 4:04 PM] gaccin Downtime

gaccin (www315) became unresponsive while in service and required a manual file-system checking before being brought back online. Downtime was 30 minutes.

[Apr 7, 2009, 12:11 PM] zirx Downtime

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

[Apr 7, 2009, 11:26 AM] seyyav Downtime

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

[Apr 7, 2009, 11:06 AM] seyyav Downtime

seyyav (www238) became unresponsive while in service and needed to be rebooted. Total downtime was less than 10 minutes.

[Apr 7, 2009, 7:45 AM] ceirt Downtime

ceirt (www39) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 7, 2009, 5:29 AM] thenge Downtime

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

[Apr 7, 2009, 1:53 AM] gaua Downtime

gaua (www442) encountered an error and reset. Downtime was less than 10 minutes.

[Apr 6, 2009, 11:47 PM] kodh Downtime

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

[Apr 6, 2009, 7:33 PM] canlaon Downtime

canlaon (www434) encountered an error and reset. Downtime was about 15 minutes.

[Apr 6, 2009, 11:56 AM] kodh Downtime

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

[Apr 5, 2009, 10:33 AM] patru Downtime

patru (www232) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Apr 5, 2009, 9:36 AM] egon Downtime

egon (www410) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Apr 5, 2009, 3:46 AM] abej Downtime

abej (www464) encountered an error and was reset. Downtime was about 10 minutes.

[Apr 4, 2009, 12:47 PM] omega Downtime

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

[Apr 3, 2009, 6:13 PM] E-Mail Filtering Upgrade

Beginning Monday, and extending throughout the week, we will be deploying e-mail and virus filtering technology for all e-mail forwarded through our e-mail system as well as for all e-mail sent to an @pair.com e-mail address.

We are taking these steps to reduce the amount of junk e-mail that passes through our e-mail servers. When forwarded e-mail is left unfiltered, the receiving e-mail server can decide to block our e-mail server, assuming it to be the sender of the e-mail, even though that is not the case.

While there is a low likelihood that these technologies will falsely reject a legitimate e-mail, it may happen from time to time. Contact us if you experience any issues forwarding or receiving e-mail.

The technologies being deployed are:

  • Greylisting (greylisting.org)
  • Clam Anti-virus (clamav.net)
  • Spamhaus and Invaluement DNSBL (spamhaus.org and dnsbl.invaluement.com)

The Invaluement DNSBL lists will additionally be used alongside Spamhaus for any customer who has enabled DNSBL Rejection in the Advanced Junk E-Mail Filtering section of the ACC.

[Apr 3, 2009, 6:03 PM] nezumi Downtime

nezumi (www337) crashed and was rebooted. Downtime was under 5 minutes.

[Apr 3, 2009, 1:39 PM] iota Downtime

The server iota (www5) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Apr 3, 2009, 10:25 AM] seyyav Downtime

seyyav (www238) encountered an error and reset. Total downtime was approximately 5 minutes.

[Apr 3, 2009, 12:23 AM] muin Downtime

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

[Apr 2, 2009, 3:01 PM] noldo Downtime

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

[Apr 2, 2009, 6:40 AM] kayan Downtime

kayan (www133) had to be rebooted due to high load. Before the server could be brought back up, a manual disk check also had to be performed. Total downtime was about 15 minutes.

[Apr 2, 2009, 12:22 AM] karkar Downtime

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

[Apr 1, 2009, 11:46 PM] auddo, masilma Maintenance Completed

The chassis upgrade on auddo (www253) has been completed. It is now an Intel Core 2 6420 with 2GB of RAM. Downtime was less than 10 minutes. The chassis upgrade for masilma (www307) had to be postponed, and will be completed later this week.

[Apr 1, 2009, 11:07 PM] auddo, masilma Planned Maintenance

auddo (www253) and masilma (www307) will be taken down shortly for chassis upgrades. Downtime for each server should be 10 minutes or less. An additional notice will be posted when this has been completed.

[Apr 1, 2009, 8:42 PM] eite Downtime

eite (www38) became unresponsive and was reset. Downtime was about 5 minutes.

[Apr 1, 2009, 6:18 PM] raitax Downtime

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

[Apr 1, 2009, 5:45 PM] sothor Downtime

sothor (www182) reset itself and was online within a few minutes.

[Apr 1, 2009, 5:05 PM] delsi Downtime

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

[Apr 1, 2009, 4:48 PM] karkar Downtime

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

[Apr 1, 2009, 4:05 PM] kaarei Downtime

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

[Apr 1, 2009, 10:49 AM] fithwor Downtime

fithwor (www222) crashed due to high load and was reset. Downtime was under 10 minutes.

[Apr 1, 2009, 10:16 AM] flaid Downtime

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

[Apr 1, 2009, 1:46 AM] ingwaz Downtime

ingwaz (www149) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 31, 2009, 1:58 PM] biont Downtime

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

[Mar 31, 2009, 8:18 AM] onn Downtime

onn (www29) encountered an error and was reset. Downtime was under 10 minutes.

[Mar 31, 2009, 6:16 AM] ynilo Downtime

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

[Mar 31, 2009, 12:27 AM] ceirt Downtime

ceirt (www39) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 30, 2009, 11:01 PM] anca, foma, aerre Maintenance Completed

Tonight's maintenance is complete. anca, foma, and aerre are each now a Core2 E6420 with 2GB of RAM. Downtime for each server was 10 minutes or less.

[Mar 30, 2009, 8:49 PM] anca, aerre, foma Emergency Maintenance

anca (www53), aerre (www185), and foma (www176) will be taken down shortly for chassis upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Mar 30, 2009, 8:19 PM] orvni Maintenance Completed

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

[Mar 30, 2009, 7:50 PM] orvni Emergency Maintenance

orvni (www205) 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.

[Mar 30, 2009, 6:31 PM] meru Downtime

meru (www438) encountered an error and was reset. Downtime was about 5 minutes.

[Mar 30, 2009, 3:58 PM] bganat Downtime

The server bganat (www481) ran out of swap space and required a reboot. The total downtime was under 10 minutes.

[Mar 30, 2009, 3:13 PM] bganat Downtime

bganat (www481) crashed and was rebooted. Downtime was about 15 minutes.

[Mar 30, 2009, 2:38 PM] zortzi Downtime

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

[Mar 30, 2009, 8:09 AM] enore Downtime

enore (www468) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Mar 29, 2009, 2:38 PM] suteki Downtime

suteki (www339) crashed due to high load and was reset. Downtime was about 5 minutes.

[Mar 29, 2009, 10:19 AM] sali Downtime

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

[Mar 29, 2009, 8:15 AM] gort Downtime

gort (www24) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 29, 2009, 6:53 AM] roku Downtime

roku (www343) this server's secondary hard drive failed and was replaced. Downtime was about 10 minutes.

[Mar 29, 2009, 12:12 AM] ceirt, yuki Downtime

ceirt (www39) and yuki (www493) both crashed and were rebooted. Downtime for each server was under 10 minutes.

[Mar 28, 2009, 8:32 PM] ingwaz Downtime

ingwaz (www149) crashed and was rebooted. Downtime was under 5 minutes.

[Mar 28, 2009, 12:27 AM] muin Downtime

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

[Mar 27, 2009, 2:06 PM] khin Downtime

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

[Mar 26, 2009, 11:17 PM] tama Downtime

tama (www70) crashed while in service and was rebooted. Downtime was under 10 minutes.

[Mar 26, 2009, 11:21 AM] amse Downtime and RAM Upgrade

amse (www210) ran out of swap space and was rebooted. While the server was down, 1 GB of RAM was added for a total of 2GB. Total downtime was under 20 minutes.

[Mar 26, 2009, 9:06 AM] enek Downtime

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

[Mar 26, 2009, 2:13 AM] saghotta Downtime

saghotta (www259) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 26, 2009, 1:17 AM] athani Downtime

athani (www157) encountered an error and reset. A file system check was required. Downtime was about 15 minutes.

[Mar 25, 2009, 8:47 PM] wedhans Downtime

wedhans (www483) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 25, 2009, 2:24 PM] sali Downtime

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

[Mar 25, 2009, 11:42 AM] erraj Downtime

erraj (www213) crashed due to high load and was reset. Downtime was about 10 minutes.

[Mar 25, 2009, 11:07 AM] glikk Downtime

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

[Mar 25, 2009, 10:58 AM] ngatwo Downtime

ngatwo (www115) encountered an error and reset. Downtime was about 5 minutes.

[Mar 25, 2009, 10:43 AM] otok Downtime

otok (www131) crashed due to high load and was reset. Downtime was about 10 minutes.

[Mar 25, 2009, 3:40 AM] auddo, delsi Maintenance Completed

The chassis upgrades for auddo and delsi are complete. auddo is now a Core2 E6400 with 2GB of RAM. delsi is a Core2 E8200 with 2GB of RAM. Downtime for each server was under 10 minutes.

[Mar 25, 2009, 1:37 AM] vinke Downtime

vinke (www470) encountered an error and reset. Downtime was about 10 minutes.

[Mar 25, 2009, 1:33 AM] auddo, delsi Planned Maintenance

auddo (www253) and delsi (www206) will be taken down shortly for chassis upgrades. Downtime for each server should be under 10 minutes. An additional notice will be posted when the upgrades are complete.

[Mar 24, 2009, 2:51 PM] tinco Downtime

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

[Mar 24, 2009, 1:13 PM] yitiya Downtime

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

[Mar 24, 2009, 12:45 PM] noldo Downtime

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

[Mar 24, 2009, 4:59 AM] murifwae, sitkin Maintenance Completed

The drive upgrades for murifwae and sitkin are complete. Each server now has a 160GB drive. Downtime was under 5 minutes.

[Mar 24, 2009, 3:24 AM] murifwae, sitkin Planned Maintenance

murifwae (www279) and sitkin (www373) 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 24, 2009, 2:20 AM] vondu Maintenance Completed

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

[Mar 24, 2009, 1:44 AM] vondu Emergency Maintenance

vondu (www241) 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.

[Mar 24, 2009, 1:04 AM] patru Downtime

patru (www232) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 23, 2009, 11:29 PM] otara Maintenance Completed

The shadow drive swap for otara is complete. Downtime was less than 5 minutes.

[Mar 23, 2009, 10:53 PM] otara Emergency Maintenance

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

[Mar 23, 2009, 9:07 PM] abotye Downtime

abotye (www298) reset itself and was online within a few minutes.

[Mar 23, 2009, 2:44 PM] patru Downtime

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

[Mar 23, 2009, 5:14 AM] gamma Downtime

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

[Mar 23, 2009, 12:51 AM] Network Maintenance Completed

Our router maintenance is now complete, and our Sprint circuit has been returned to service as of 12:35 AM Eastern time.

[Mar 23, 2009, 12:08 AM] muin Downtime

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

[Mar 22, 2009, 2:40 PM] Network Problems Resolved

We have isolated two unrelated network faults and are working to correct them. An inbound network attack was suppressed, and one of our Juniper edge routers has had a hardware failure, taking our Sprint circuit offline.

We will be rerouting the Sprint circuit this evening. Customer traffic should no longer be affected, now that the problems have been identified.

[Mar 22, 2009, 2:34 PM] Network Problems

We are currently experiencing intermittent network connectivity problems to some of our customers. Our network engineers are currently working on the issue. Another notice will be posted as soon as the issue has been resolved.

[Mar 22, 2009, 3:33 AM] irazu Downtime

irazu (www377) encountered an error and was reset. Downtime was about 5 minutes.

[Mar 22, 2009, 12:14 AM] muin Downtime

muin (www23) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Mar 21, 2009, 12:05 AM] omega Downtime

omega (www16) encountered an error and reset. Downtime was about 5 minutes.

[Mar 20, 2009, 9:06 AM] vinke Downtime

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

[Mar 20, 2009, 7:48 AM] delsi Downtime

delsi (www206) encountered an error and had to be rebooted. Downtime was less than 10 minutes.

[Mar 20, 2009, 4:21 AM] omega Downtime

omega (www16) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Mar 20, 2009, 4:14 AM] nezumi Downtime

nezumi (www337) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 20, 2009, 12:50 AM] karkar Downtime

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

[Mar 19, 2009, 8:51 PM] bganat Downtime

bganat (www481) became unresponsive and was reset. Downtime was about 5 minutes.

[Mar 19, 2009, 1:49 PM] karkar Downtime

karkar (www429) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Mar 19, 2009, 1:25 PM] desu Downtime

The server desu (www474) encountered an error while in service and was reset. Downtime was 10 minutes.

[Mar 19, 2009, 11:15 AM] derba Downtime and RAM Upgrade

derba (www104) ran out of swap space and was rebooted. While the server was down, 1 GB of RAM was added for a total of 2GB. Total downtime was about 20 minutes.

[Mar 19, 2009, 3:57 AM] siyazi Downtime

siyazi (www251) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 19, 2009, 2:43 AM] waitak, maym Maintenance Completed

The shadow drive swaps for waitak and maym are complete. Downtime for each server was under 5 minutes.

[Mar 19, 2009, 1:39 AM] waitak, maym Emergency Maintenance

waitak (www283) and maym (www202) will be taken down shortly to replace failing shadow drives. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Mar 18, 2009, 9:38 PM] Database Server Maintenance Completed

The upgrades for db40.pair.com through db47.pair.com are complete. db40, db41, db42, and db43 are now on a Core2 E6600 with 4GB of RAM and 228GB disk. db44, db45, db46, and db47 are now on a Core2 E8200 with 4GB of RAM and 228GB disk. Downtime for each server was 5 minutes or less.

[Mar 18, 2009, 8:14 PM] DB Server Maintenance

The following servers will each be offline for up to 15 minutes over the next 2 hours, as each is migrated to newer hardware:

db40.pair.com
db41.pair.com
db42.pair.com
db43.pair.com
db44.pair.com
db45.pair.com
db46.pair.com
db47.pair.com

An additional notice will be posted when this maintenance is complete.

[Mar 18, 2009, 3:15 PM] izalc Downtime

The server izalc (www378) crashed due to high load and was rebooted. The total downtime was under 10 minutes.

[Mar 18, 2009, 1:59 PM] sali Downtime

sali (www454) became unresponsive while in service and required a manual filesystem check before being brought back online. Downtime was 20 minutes.

[Mar 18, 2009, 5:35 AM] zatz Downtime

zatz (www122) encountered an error during operation and was reset. Downtime was about 10 minutes.

[Mar 18, 2009, 3:16 AM] ghiq Downtime

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

[Mar 18, 2009, 1:22 AM] maym Maintenance Completed

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

[Mar 18, 2009, 12:20 AM] maym Emergency Maintenance

maym (www202) 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.

[Mar 18, 2009, 12:05 AM] sothor Downtime

sothor (www182) encountered an error and reset. Downtime was less than 5 minutes.

[Mar 17, 2009, 9:26 PM] usagi Emergency Maintenance

usagi (www331) experienced a hardware failure and received a chassis swap. The server is now a Pentium 4 3.4GHz with 2GB of RAM. Total downtime was about 15 minutes.

[Mar 17, 2009, 5:56 PM] xoopi Downtime

The server xoopi (www266) crashed due to a high load and required a manual file system check before rebooting. The total downtime was under 15 minutes.

[Mar 17, 2009, 12:22 PM] kavachi Downtime

kavachi (www437) encountered an error while in service and was reset. Downtime was under 10 minutes.

[Mar 17, 2009, 11:41 AM] mahawu Downtime

mahawu (www407) became unresponsive while in service and was reset. Downtime was under 20 minutes.

[Mar 17, 2009, 11:36 AM] thenge Downtime

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

[Mar 17, 2009, 11:35 AM] marapi Downtime

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

[Mar 17, 2009, 11:35 AM] aster Downtime

aster (www96) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Mar 17, 2009, 11:33 AM] wunjo Downtime

wunjo (www140) became unresponsive while in service and was reset. Downtime was under 20 minutes.

[Mar 17, 2009, 11:33 AM] marapi Downtime

[Mar 17, 2009, 11:33 AM] sothor Downtime

sothor (www182) became unresponsive while in service and was reset. Downtime was under 20 minutes.

[Mar 17, 2009, 11:31 AM] gamma Downtime

gamma (www2) became unresponsive while in service and was reset. Downtime was under 20 minutes.

[Mar 17, 2009, 11:30 AM] paell Downtime

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

[Mar 17, 2009, 10:27 AM] ando Downtime

ando (www45) encountered an error while in service and was reset. Downtime was under 10 minutes.

[Mar 17, 2009, 9:51 AM] flaid Downtime

flaid (www91) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Mar 17, 2009, 9:50 AM] akket Downtime

akket (www211) encountered an error and was reset. Downtime was under 20 minutes.

[Mar 17, 2009, 8:52 AM] PHP 5.2.9

All shared servers and QuickServe dedicated servers have now been upgraded to PHP 5.2.9. Please contact support@pair.com with any questions or problems.

[Mar 17, 2009, 8:47 AM] maym Downtime

maym (www202) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Mar 16, 2009, 10:03 PM] sowilu Downtime

sowilu (www145) encountered and error and had to be rebooted. Downtime was about 15 minutes.

[Mar 16, 2009, 8:40 PM] flaid Downtime

flaid (www91) became unresponsive and was reset. Downtime was about 10 minutes.

[Mar 16, 2009, 7:08 PM] hyaku Downtime

hyaku (www345) reset itself and was online within a few minutes.

[Mar 16, 2009, 6:01 PM] kunatri Downtime

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

[Mar 16, 2009, 3:17 PM] ungkohe Downtime

The server ungkohe (www306) crashed due to a high load and was rebooted. Downtime was less than 10 minutes.

[Mar 16, 2009, 5:28 AM] misilay Downtime

misilay (www282) became unresponsive and was reset. Downtime was about 5 minutes.

[Mar 16, 2009, 12:49 AM] ilwe Downtime

ilwe (www81) became unresponsive and was reset. Downtime was about 5 minutes.

[Mar 16, 2009, 12:42 AM] muin Downtime

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

[Mar 15, 2009, 6:57 PM] lehhdi Downtime

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

[Mar 15, 2009, 6:16 PM] ingwaz Downtime

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

[Mar 15, 2009, 4:40 PM] peswar Downtime

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

[Mar 15, 2009, 3:43 PM] nuumen Downtime

nuumen (www55) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Mar 15, 2009, 9:56 AM] ur Downtime

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

[Mar 15, 2009, 2:55 AM] yitiya Downtime

yitiya (www252) encountered an error and was reset. Downtime was about 5 minutes.

[Mar 15, 2009, 12:19 AM] muin Downtime

muin (www23) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Mar 14, 2009, 3:46 AM] yume Downtime

yume (www334) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 13, 2009, 8:32 PM] bganat Downtime

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

[Mar 13, 2009, 7:59 PM] umbar Downtime

umbar (www46) crashed while in service was was rebooted. Downtime was under 10 minutes.

[Mar 13, 2009, 7:12 PM] delsi Downtime

delsi (www206) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 13, 2009, 4:02 PM] misilay Downtime

misilay (www282) became unresponsive due to high load and was reset. Downtime was about 20 minutes.

[Mar 13, 2009, 3:15 PM] hauda Downtime

hauda (www234) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Mar 13, 2009, 1:44 PM] izalc Downtime

izalc (www378) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 13, 2009, 2:50 AM] anca Maintenance Completed

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

[Mar 13, 2009, 2:12 AM] anca Emergency Maintenance

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

[Mar 13, 2009, 12:18 AM] iruvul Downtime

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

[Mar 12, 2009, 9:33 PM] hyarmen Downtime

hyarmen (www66) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 12, 2009, 5:14 PM] diviy Downtime

diviy (www217) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Mar 12, 2009, 5:10 PM] kelut Downtime

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

[Mar 12, 2009, 12:42 PM] iruvul Downtime

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

[Mar 12, 2009, 10:22 AM] flure Downtime

flure (www75) encountered an error and needed to be reset. Total downtime was approximately 20 minutes.

[Mar 12, 2009, 10:08 AM] karkar Downtime

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

[Mar 12, 2009, 3:03 AM] oshima Downtime

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

[Mar 12, 2009, 2:08 AM] orroka Maintenance Completed

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

[Mar 12, 2009, 1:11 AM] orroka Emergency Maintenance

orroka (www276) 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.

[Mar 11, 2009, 4:21 PM] wredhor Downtime

wredhor (www76) rebooted itself. Downtime was under 5 minutes.

[Mar 11, 2009, 2:20 PM] or Downtime

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

[Mar 11, 2009, 12:41 PM] or Downtime

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

[Mar 11, 2009, 12:00 PM] ohayou Downtime

ohayou (www477) crashed due to an error and was reset. Downtime was about 5 minutes.

[Mar 11, 2009, 10:29 AM] lehhdi Downtime

lehhdi (www267) crashed due to high load and was reset. Downtime was about 5 minutes.

[Mar 11, 2009, 6:19 AM] ynilo Downtime

A chassis swap was performed on ynilo (www166) due to a fan failure. The server is now a Pentium 4 3.4GHz with 2GB of RAM. Total downtime was about 15 minutes.

[Mar 10, 2009, 11:01 PM] enore Downtime

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

[Mar 10, 2009, 6:51 PM] sether Downtime

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

[Mar 10, 2009, 3:48 PM] dotya Downtime

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

[Mar 10, 2009, 12:19 PM] muyal Downtime

muyal (www236) became unresponsive while in service. Downtime was under 10 minutes.

[Mar 10, 2009, 12:16 PM] muyal Downtime

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

[Mar 10, 2009, 11:13 AM] falku Downtime

falku (www98) encountered an error and was reset. Downtime was under 15 minutes.

[Mar 10, 2009, 10:03 AM] taal Downtime

taal (www433) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Mar 10, 2009, 1:06 AM] suoh Downtime

suoh (www396) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 9, 2009, 3:21 PM] thenge Downtime

The server thenge (www270) crashed due to a high load and was rebooted. The total downtime was less than 10 minutes.

[Mar 9, 2009, 8:40 AM] thenge Downtime

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

[Mar 8, 2009, 9:52 PM] oynos Downtime

oynos (www218) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 8, 2009, 6:35 PM] tinne Downtime

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

[Mar 8, 2009, 12:15 AM] muin Downtime

muin (www23) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Mar 7, 2009, 4:51 AM] klesh Emergency Maintenance

klesh (www200) experienced a sudden drive failure and has been swapped to the shadow drive. All data was current as of approximately 3:30AM Eastern. Downtime was about 15 minutes, and the server now has a 160GB drive.

[Mar 7, 2009, 2:42 AM] ijen Downtime

ijen (www404) encountered an error and was reset. Downtime was less than 10 minutes.

[Mar 7, 2009, 12:07 AM] sallane Downtime

sallane (www263) encountered and error and had to be rebooted. Downtime was about 5 minutes.

[Mar 6, 2009, 1:04 PM] gyaku Downtime

gyaku (www351) encountered an error and was reset. An additional 1GB of RAM was added to the server during its downtime. Downtime was about 10 minutes.

[Mar 6, 2009, 11:58 AM] sibum Downtime

sibum (www224) became unresponsive due to high load and was rebooted. Downtime was less than 5 minutes.

[Mar 6, 2009, 6:00 AM] quan Maintenance Completed

The emergency drive swap for quan is complete. It now has a 250GB drive. Downtime was about 15 minutes.

[Mar 6, 2009, 5:30 AM] quan Emergency Maintenance

quan (www120) 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.

[Mar 6, 2009, 4:15 AM] calma Emergency Maintenance

calma (www43) experienced a sudden drive failure and has been swapped to the shadow drive. All data was current as of about 10PM last evening. Mailbox data should be current as of about 2:45AM this morning. Downtime was about 15 minutes. The server now has a 160GB drive.

[Mar 6, 2009, 12:25 AM] ajilan Downtime

ajilan (www384) encountered an error and reset. Downtime was about 10 minutes.

[Mar 6, 2009, 12:12 AM] yuki Downtime

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

[Mar 5, 2009, 3:00 PM] traad Downtime

traad (www478) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 5, 2009, 12:16 PM] waitak Downtime

waitak (www283) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Mar 5, 2009, 8:58 AM] ailm Downtime

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

[Mar 5, 2009, 6:10 AM] thenge Downtime

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

[Mar 4, 2009, 11:19 PM] amse Downtime

amse (www210) became unresponsive and was reset. Downtime was about 10 minutes.

[Mar 4, 2009, 9:16 PM] DB Maintenance Completed

The maintenance on db32, db33, db34, db35, db36, db37, db38 and db39 is now complete. These MySQL servers are now on a Core 2 E8200 with 4GB of RAM. Downtime for each server was less than 10 minutes.

[Mar 4, 2009, 7:43 PM] DB Server Maintenance

The following servers will each be offline for up to 15 minutes over the next 2 hours, as each is migrated to newer hardware:

db32.pair.com
db33.pair.com
db34.pair.com
db35.pair.com
db36.pair.com
db37.pair.com
db38.pair.com
db39.pair.com

An additional notice will be posted when this maintenance is complete.

[Mar 4, 2009, 2:02 PM] soputan Downtime

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

[Mar 4, 2009, 1:45 AM] alayta Downtime

alayta (www380) encountered an error and was reset. Downtime was about 10 minutes.

[Mar 3, 2009, 6:51 PM] sether Downtime

sether (www95) crashed and was rebooted. Downtime was under 10 minutes.

[Mar 3, 2009, 6:03 PM] mordo Downtime

mordo (www498) reset itself and was online within a few minutes.

[Mar 3, 2009, 11:05 AM] atsui Downtime

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

[Mar 3, 2009, 10:27 AM] sali Downtime

sali (www454) encountered an error and was reset. Downtime was under 5 minutes.

[Mar 2, 2009, 8:59 PM] DB Maintenance Completed

The maintenance on db28, db29, db30, and db31 is now complete. These MySQL servers are now on a Core 2 E8200 with 4GB of RAM. Downtime for each server was less than 10 minutes.

[Mar 2, 2009, 8:28 PM] DB Server Maintenance

db28.pair.com, db29.pair.com, db30.pair.com, and db31.pair.com will each be offline for up to 15 minutes over the next 2 hours, as each is migrated to newer hardware. Another notice will be posted when this maintenance is complete.

[Mar 2, 2009, 8:29 AM] dieci Downtime

dieci (www231) encountered an error and was reset. Downtime was under 10 minutes.

[Feb 28, 2009, 3:46 PM] maym Downtime

maym (www202) is currently experiencing network connectivity problems due to an incoming network attack. We are working diligently on the issue and will post a notice once the issue has been resolved.

[Feb 28, 2009, 12:45 PM] mae Downtime and RAM Upgrade

mae (www349) ran out of swap space and was rebooted. While the server was down, 1 GB of RAM was added for a total of 2GB. Total downtime was under 20 minutes.

[Feb 28, 2009, 6:04 AM] klesh Maintenance Completed

klesh (www200) the drive cable swap is complete. Downtime was less than 5 minutes.

[Feb 28, 2009, 5:27 AM] klesh Planned Maintenance

klesh (www200) will be taken down shortly to replace a failing drive cable. Downtime is expected to be less than 10 minutes.

[Feb 27, 2009, 10:48 PM] mu Downtime

mu (www7) became unresponsive and was reset. Downtime was about 5 minutes.

[Feb 27, 2009, 4:49 PM] migi Emergency Maintenance

A chassis swap was performed on migi(www327) due to ongoing crashes. The new server is a Pentium 4 3.4GHz and 4GB of RAM. The total downtime for this operation was approximately 15 minutes.

[Feb 27, 2009, 3:10 PM] wredhor Downtime

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

[Feb 27, 2009, 1:58 PM] migi Downtime

migi (www327) reset itself and was online within a few minutes.

[Feb 27, 2009, 12:18 PM] yuzz Downtime

yuzz (www117) became unresponsive and was rebooted. Downtime was less than 5 minutes.

[Feb 27, 2009, 5:02 AM] yitiya, kelut Maintenance Completed

The shadow drive swaps for yitiya and kelut are complete. Downtime for each server was about 5 minutes.

[Feb 27, 2009, 4:26 AM] kelut Emergency Maintenance

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

[Feb 27, 2009, 3:32 AM] yitiya Emergency Maintenance

yitiya (www252) 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 maintenance is complete.

[Feb 26, 2009, 6:39 PM] falku Downtime

falku (www98) was reset to clear an error condition. Downtime was about 5 minutes.

[Feb 26, 2009, 1:34 PM] muin Downtime

muin (www23) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 26, 2009, 10:09 AM] bhoth Downtime

bhoth (www163) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 15 minutes.

[Feb 26, 2009, 7:05 AM] yitiya Downtime

yitiya (www252) became unresponsive and had to be rebooted. Downtime was about 10 minutes.

[Feb 26, 2009, 6:29 AM] kesa Downtime

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

[Feb 26, 2009, 5:34 AM] ajilan Downtime

ajilan (www384) crashed and had to be rebooted. Downtime was about 15 minutes.

[Feb 26, 2009, 2:57 AM] migi Downtime

migi (www327) encountered an error and was reset. During the reset a manual disk check was required. Downtime was about 15 minutes.

[Feb 26, 2009, 2:14 AM] bganat Downtime

bganat (www481) was rebooted to clear up an error condition. Downtime was under 5 minutes.

[Feb 25, 2009, 5:12 PM] jarre Downtime

jarre (www172) became unresponsive and was reset. Downtime was about 5 minutes.

[Feb 25, 2009, 4:11 PM] migi Downtime

The server migi(www327) crashed due to a high load and required a manual file system check. The total downtime was approximately 10 minutes.

[Feb 25, 2009, 7:29 AM] fithwor Downtime

fithwor (www222) Encountered an error during operation and was reset. Downtime was about 5 minutes.

[Feb 25, 2009, 6:36 AM] ceirt Downtime

ceirt (www39) Encountered an error and was reset. Downtime was about 5 minutes.

[Feb 25, 2009, 12:08 AM] yume Downtime

yume (www334) encountered an error and reset. Downtime was less than 10 minutes.

[Feb 24, 2009, 6:54 PM] omega Emergency Maintenance

omega (www16) crashed while in service. During this downtime, we performed a chassis swap. complete. It is now a Core2 E6600 with 2GB of RAM. Downtime was about 20 minutes.

[Feb 24, 2009, 6:43 PM] fiann Downtime

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

[Feb 24, 2009, 5:17 PM] rilwi Downtime

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

[Feb 24, 2009, 8:07 AM] ajilan Downtime

ajilan (www384) crashed due to high load and was rebooted. The total downtime for the server was under 10 minutes.

[Feb 24, 2009, 6:08 AM] ajilan Downtime

ajilan (www384) Encountered an error and was reset. Downtime was about 10 minutes.

[Feb 24, 2009, 5:17 AM] musume Maintenance Completed

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

[Feb 24, 2009, 4:59 AM] musume Emergency Maintenance

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

[Feb 24, 2009, 4:54 AM] alayta Maintenance Completed

The chassis swap for alayta is complete. It is now a Core2 E6600 with 2GB of RAM. Downtime was about 10 minutes.

[Feb 24, 2009, 3:54 AM] alayta Emergency Maintenance

Due to recent instability, alayta (www380) will be taken down for a chassis swap. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Feb 24, 2009, 3:36 AM] migi Downtime

migi (www327) encountered an error and reset. Downtime was less than 10 minutes.

[Feb 23, 2009, 11:10 PM] wokkil Downtime

wokkil (www249) crashed while in service. During this downtime, we performed an emergency RAM swap. Downtime was about 15 minutes.

[Feb 23, 2009, 9:31 PM] ceirt, psi Maintenance Completed

The drive maintenance has been completed. ceirt (www39) now has a new 250GB primary drive, and psi (www15) was given a new shadow drive. Downtime for each server was 10 minutes or less.

[Feb 23, 2009, 9:10 PM] saghotta Downtime

saghotta (www259) crashed while in service. During this downtime, we performed an emergency RAM swap. Downtime was about 10 minutes.

[Feb 23, 2009, 8:40 PM] ceirt, psi Planned Maintenance

ceirt (www39) will be taken down shortly to swap a failing drive. psi (www15) will be taken down to swap a failing Shadow Drive. Downtime for each server should be less than 10 minutes. An additional notice will be posted when this has been completed.

[Feb 23, 2009, 4:07 PM] bganat Downtime

The server bganat(www481) crashed due to high load and was rebooted. The total downtime for the server was under 10 minutes.

[Feb 22, 2009, 12:48 AM] anga Downtime

anga (www47) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Feb 22, 2009, 12:03 AM] alayta Downtime

alayta (www380) rebooted itself. Downtime was under 5 minutes.

[Feb 21, 2009, 4:47 PM] naam Emergency Maintenance

naam (www114) crashed while in service and was given a chassis swap. Downtime was less than 15 minutes. It is now a Pentium 4 3GHz with 1GB of RAM.

[Feb 21, 2009, 11:41 AM] alayta Downtime

alayta (www380) rebooted itself again. During this downtime, we performed an emergency RAM swap. Downtime was about 10 minutes.

[Feb 21, 2009, 9:38 AM] alayta Downtime

alayta (www380) reset itself and was online within a few minutes.

[Feb 21, 2009, 12:09 AM] alayta Downtime

alayta (www380) encountered an error and reset. Downtime was about 10 minutes.

[Feb 20, 2009, 6:48 PM] traad Downtime

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

[Feb 20, 2009, 6:22 PM] tinne Downtime

tinne (www21) crashed and was rebooted. We are monitoring this server closely. Downtime was under 10 minutes.

[Feb 20, 2009, 3:45 PM] tinne Downtime

tinne (www21) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Feb 20, 2009, 12:36 PM] lehhdi Downtime

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

[Feb 20, 2009, 9:18 AM] alayta Downtime

alayta (www380) became unresponsive while in service and needed to be reset. Total downtime was approximately 5 minutes.

[Feb 19, 2009, 9:39 PM] kirlian Downtime

kirlian (www110) crashed under high load and was rebooted. Downtime was under 10 minutes.

[Feb 19, 2009, 9:25 PM] Webmail maintenance completed

The maintenance on the Webmail system has been completed. Total downtime was less than 10 minutes.

[Feb 19, 2009, 8:42 PM] Webmail planned maintenance

Shortly after 9:00 PM, our webmail system will be taken down briefly while hardware maintenance is performed. Downtime should be less than 10 minutes, and an additional notice will be posted when this has been completed.

[Feb 19, 2009, 6:14 PM] thenge Downtime

thenge (www270) became unresponsive and was reset. Downtime was less than 5 minutes.

[Feb 19, 2009, 2:16 PM] djole Downtime

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

[Feb 18, 2009, 9:43 PM] abej Downtime

abej (www464) became unresponsive and was reset. Downtime was less than 10 minutes.

[Feb 18, 2009, 8:55 PM] Webmail maintenance completed

The maintenance on the Webmail system has been completed. Total downtime was about 2 minutes.

[Feb 18, 2009, 8:43 PM] Webmail planned maintenance

The webmail system will be unavailable for a few minutes while some brief maintenance is performed. Total downtime should be 5 minutes or less. An additional notice will be posted when this has been completed.

[Feb 18, 2009, 4:56 PM] naam Downtime

naam (www114) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Feb 18, 2009, 4:44 PM] abej Downtime

abej (www464) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 15 minutes.

[Feb 18, 2009, 2:27 PM] webmail downtime

The pair Networks webmail.pair.com system experienced a database problem. This was fixed with a downtime of about 30 minutes.

[Feb 18, 2009, 12:32 AM] ingwaz Downtime

ingwaz (www149) crashed and required an emergency RAM swap and filesystem check. Downtime was about 15 minutes.

[Feb 17, 2009, 11:54 PM] midori Downtime

midori (www492) encountered an error shortly after it came back up and required another filesystem check. Downtime was about 15 minutes. POP and IMAP mail service was unavailable for about 55 minutes after the server returned to service, while a configuration problem was repaired.

[Feb 17, 2009, 10:14 PM] midori Downtime

midori (www492) crashed and required a manual disk check. Downtime was approximately 20 minutes.

[Feb 17, 2009, 2:05 PM] midori Downtime

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

[Feb 17, 2009, 11:42 AM] ingwaz Downtime

ingwaz (www149) encountered an error and was reset. Downtime was under 10 minutes.

[Feb 17, 2009, 6:53 AM] mini Downtime

mini (www126) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 16, 2009, 9:14 PM] tinco Downtime

tinco (www41) Experienced an error and was reset. Downtime was about 5 minutes.

[Feb 16, 2009, 7:28 PM] lehhdi Downtime

lehhdi (www267) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Feb 16, 2009, 1:27 AM] bhoth Downtime

bhoth (www163) Experienced an error and was reset. Downtime was about 5 minutes.

[Feb 15, 2009, 11:27 AM] flaid Downtime

flaid (www91) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Feb 15, 2009, 12:26 AM] fayev Emergency Maintenance

fayev (www365) crashed and required an emergency chassis swap, as well as a manual disk check. Downtime was approximately 30 minutes. The server is now a Core2 Duo E6600 with 4GB of RAM. We apologize for the inconvenience.

[Feb 14, 2009, 11:45 PM] hasaya Emergency Maintenance

hasaya (www364) suffered a catastrophic chassis failure that required an emergency chassis swap. It is now Core2 Duo E6420 with 2GB of RAM. Downtime was about 30 minutes.

[Feb 14, 2009, 8:02 PM] amse Downtime

amse (www210) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Feb 14, 2009, 3:29 PM] hasaya Downtime

hasaya (www364) became unresponsive due to high load and was reset. Downtime was 10 minutes.

[Feb 14, 2009, 3:28 PM] naam Downtime

naam (www114) became unresponsive while in service and was reset. Downtime was 5 minutes.

[Feb 14, 2009, 12:53 PM] dieci Downtime

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

[Feb 14, 2009, 12:37 PM] bhoth Downtime

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

[Feb 14, 2009, 12:20 AM] emra Downtime

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

[Feb 13, 2009, 3:04 PM] karkar Downtime

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

[Feb 13, 2009, 10:57 AM] alayta Downtime

alayta (www380) became unresponsive while in service and needed to be rebooted. Total downtime was approximately 5 minutes.

[Feb 13, 2009, 8:07 AM] wedhans Downtime

wedhans (www483) crashed due to high load and was reset. Downtime was under 10 minutes.

[Feb 13, 2009, 7:58 AM] ulwar Downtime

ulwar (www82) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Feb 13, 2009, 7:35 AM] alayta Downtime

alayta (www380) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Feb 13, 2009, 3:51 AM] emra Downtime

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

[Feb 12, 2009, 8:26 AM] muin Downtime

muin (www23) encountered an error while in service and needed to be reset. Total downtime was about 10 minutes.

[Feb 12, 2009, 5:59 AM] Utility Power Outage

Utility power to our datacenter was lost at approximately 5:25 AM Eastern. Our UPS and generator systems seamlessly took over our power needs, and kept us running until the restoration of utility power approximately 15 minutes later.

[Feb 12, 2009, 2:29 AM] migi Downtime

migi (www327) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 11, 2009, 10:23 AM] lehhdi Downtime

lehhdi (www267) crashed due to high load and was reset. Downtime was under 10 minutes.

[Feb 11, 2009, 6:25 AM] omsano Downtime

omsano (www164) reset itself and was online within a few minutes.

[Feb 11, 2009, 1:52 AM] gessire Downtime

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

[Feb 10, 2009, 4:09 PM] Network Problems Resolved

While updating router configurations related to a new cross-country link, we inadvertently creating a routing loop that primarily affected customers of Time Warner Telecom. The problem was resolved after approximately 30 minutes. If you are still having any trouble reaching our network, please contact us. We apologize for this error; the changes should only have enhanced connectivity, not disrupted it.

[Feb 10, 2009, 3:33 PM] gessire Downtime

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

[Feb 10, 2009, 1:00 PM] midori Downtime

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

[Feb 9, 2009, 7:31 PM] alayta Downtime

alayta (www380) reset itself and was online within a few minutes.

[Feb 9, 2009, 3:19 PM] sali Downtime

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

[Feb 9, 2009, 1:16 PM] sali Downtime

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

[Feb 8, 2009, 12:35 PM] merau Downtime

merau (www245) encountered an error and was reset. Downtime was under 5 minutes.

[Feb 7, 2009, 5:51 AM] lehhdi Downtime

lehhdi (www267) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Feb 7, 2009, 3:47 AM] akket Downtime

akket (www211) encountered an error and reset. Downtime was about 10 minutes.

[Feb 7, 2009, 1:27 AM] siyazi Downtime

siyazi (www251) encountered an error and was reset. Downtime was about 10 minutes.

[Feb 7, 2009, 12:19 AM] yuki Downtime

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

[Feb 6, 2009, 10:40 PM] psi Downtime

psi (www15) encountered an error and was reset. Downtime was under 15 minutes.

[Feb 6, 2009, 9:27 AM] tuzuba Downtime

tuzuba (www256) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Feb 6, 2009, 9:21 AM] merau Maintenance Completed

The shadow drive swap for merau (www245) is complete. Downtime was about 5 minutes.

[Feb 6, 2009, 9:03 AM] merau Emergency Maintenance

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

[Feb 6, 2009, 8:37 AM] merau Downtime

merau (www245) became unresponsive while in service and needed to be rebooted. A manual filesystem check was required in order to bring the server back online. Total downtime was 20 minutes.

[Feb 5, 2009, 9:52 PM] akai Maintenance Completed

The maintenance on akai (www353) has been completed. It is now a Pentium 4 3.80GHz with 3GB of RAM. Total downtime was about 20 minutes.

[Feb 5, 2009, 9:19 PM] abej Downtime

abej (www464) crashed and was rebooted. Downtime was under 5 minutes.

[Feb 5, 2009, 8:57 PM] akai Planned Maintenance

akai (www353) will be taken down shortly for a chassis upgrade. Downtime should be less than 20 minutes, and an additional notice will be posted when this has been completed.

[Feb 5, 2009, 8:40 PM] eite Downtime

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

[Feb 5, 2009, 4:45 PM] eite Downtime

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

[Feb 5, 2009, 11:11 AM] uttu Downtime

uttu (www456) encountered an error while in service and needed to be reset. Total downtime was 10 minutes.

[Feb 5, 2009, 9:19 AM] iota Downtime

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

[Feb 5, 2009, 6:59 AM] lopevi Downtime

lopevi (www445) encountered an error and had to be rebooted. Downtime was about 5 minutes.

[Feb 5, 2009, 4:50 AM] quesse Maintenance Completed

The shadow drive swap for quesse (www44) is complete. Downtime was about 10 minutes.

[Feb 5, 2009, 3:55 AM] quesse Emergency Maintenance

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

[Feb 5, 2009, 1:09 AM] tenshian Downtime

tenshian (www103) encountered an error and reset. Downtime was less than 10 minutes.

[Feb 4, 2009, 11:16 PM] dukoni, falku Maintenance Completed

The maintenance on dukoni (www305) and falku (www98) has been completed. They each now have 160GB primary drives. Downtime for each server was under 10 minutes.

[Feb 4, 2009, 9:33 PM] sramet Maintenance Completed

The drive swap on sramet (www399) has been completed. It now has a new 250GB drive. Downtime was less than 5 minutes.

[Feb 4, 2009, 9:12 PM] sramet Emergency Maintenance

sramet (www399) 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.

[Feb 4, 2009, 6:49 PM] dukoni, falku Planned Maintenance

Tonight after 9PM EST dukoni (www305) and falku (www98) will be taken down for drive upgrades. Downtime for each server should not exceed 10 minutes. An additional notice will be posted once the maintenance is complete.

[Feb 4, 2009, 9:52 AM] sogbe Downtime

sogbe (www274) encountered an error and was reset. Downtime was approximately 5 minutes.

[Feb 4, 2009, 9:39 AM] bganat Downtime

bganat (www481) experienced high load and was reset. Downtime was under 15 minutes.

[Feb 4, 2009, 8:44 AM] ailm Downtime

ailm (www28) encountered an error and was reset. Downtime was under 15 minutes.

[Feb 4, 2009, 5:04 AM] marapi Downtime

marapi (www390) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 3, 2009, 12:29 PM] PHP 5.2.8 for QuickServe

All QuickServe dedicated servers will be updated to PHP 5.2.8 today. This version has been running on our shared hosting servers for a few weeks. This is a minor upgrade so no problems are expected. This upgrade will only be applied to servers running FreeBSD 6.2. Any custom PHP installations will be retained. If you have any questions or experience any problems, please contact qs@pair.com

[Feb 3, 2009, 10:25 AM] wedhans Downtime

wedhans (www483) encountered high load and was reset. Downtime was under 10 minutes.

[Feb 3, 2009, 8:21 AM] alayta Downtime

alayta (www380) encountered an error while in service and was reset. Downtime was approximately 5 minutes.

[Feb 2, 2009, 6:20 PM] ungwe Downtime

ungwe (www48) reset itself and was online within a few minutes.

[Feb 2, 2009, 3:28 PM] eite Downtime

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

[Feb 2, 2009, 1:28 PM] kanat Downtime

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

[Feb 2, 2009, 5:10 AM] mu Downtime

mu (www7) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 2, 2009, 2:57 AM] mu Downtime

mu (www7) became unresponsive and had to be rebooted. Downtime was about 5 minutes.

[Feb 1, 2009, 8:40 PM] biont Downtime

biont (www174) encountered an error and was reset. Downtime was about 5 minutes.

[Feb 1, 2009, 7:18 PM] ansuz Downtime

ansuz (www137) reset itself and was online within a few minutes.

[Feb 1, 2009, 3:31 AM] nyartu Downtime

nyartu (www254) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 31, 2009, 6:37 PM] alayta Downtime

alayta (www380) crashed again. During this downtime, we performed an emergency RAM swap, which should help to stabilize the server. Downtime was about 10 minutes.

[Jan 31, 2009, 4:37 PM] alayta Downtime

alayta (www380) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 31, 2009, 1:03 PM] nandirse Downtime

nandirse (www255) encountered an error and needed to be reset. Total downtime was less than 10 minutes.

[Jan 30, 2009, 6:07 PM] omega Downtime

omega (www16) crashed and required a manual file system check. Downtime was about 15 minutes.

[Jan 30, 2009, 2:48 PM] vroo Downtime

vroo (www125) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jan 30, 2009, 1:12 PM] migi Downtime

migi (www327) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Jan 30, 2009, 4:09 AM] ur Downtime

ur (www30) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 30, 2009, 2:01 AM] eotle Downtime

At approximately 1:35AM, eotle (www487) encountered an error and reset. Downtime was less than 10 minutes.

[Jan 29, 2009, 1:32 PM] padaya Downtime

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

[Jan 29, 2009, 5:45 AM] tuzuba, thnad, ur, xi Maintenance Completed

Today's maintenance is complete. tuzuba is now a Core2 E6420 with 2GB of RAM. thnad now has a 120GB drive. ur and xi now have 160GB drives. Downtime for each server was about 5 minutes.

[Jan 29, 2009, 2:29 AM] muin Downtime

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

[Jan 29, 2009, 1:45 AM] tuzuba, thnad, ur, xi Planned Maintenance

tuzuba (www256) will be taken down shortly for a chassis upgrade. thnad (www121), ur (www30), and xi (www8) 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.

[Jan 28, 2009, 11:34 PM] raitax Downtime

raitax (www171) became unresponsive while in service and was reset. Downtime was about 5 minutes.

[Jan 28, 2009, 9:51 PM] orxul Downtime

orxul (www471) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 28, 2009, 2:28 PM] somkix Downtime

The server somkix crashed due to a high load and was rebooted. The total downtime for the server was approximately 10 minutes.

[Jan 28, 2009, 11:53 AM] masilma Downtime

masilma (www307) crashed due to high load and was reset. Downtime was about 5 minutes.

[Jan 28, 2009, 11:30 AM] ohayou Downtime

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

[Jan 27, 2009, 7:53 PM] or Downtime

or (www34) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 27, 2009, 11:58 AM] masilma Downtime

masilma (www307) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jan 27, 2009, 11:49 AM] fiann Downtime

fiann (www188) experienced high load and was reset. We are currently closely monitoring the server. Downtime was under 20 minutes.

[Jan 27, 2009, 11:21 AM] tuzuba Downtime

tuzuba (www256) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jan 27, 2009, 11:10 AM] fiann Downtime

fiann (www188) encountered high load and was reset. Downtime was under 10 minutes.

[Jan 27, 2009, 5:25 AM] tuzuba Downtime

tuzuba (www256) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 27, 2009, 12:25 AM] muin Downtime

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

[Jan 26, 2009, 8:38 PM] eldfell Downtime

eldfell (www450) crashed and was rebooted. Downtime was under 5 minutes.

[Jan 26, 2009, 8:25 PM] uttu Scheduled Maintenance

uttu (www456) will be taken down briefly to enable a configuration change. Expected downtime is less than 5 minutes.

[Jan 26, 2009, 2:57 PM] fiann Downtime

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

[Jan 26, 2009, 12:08 PM] masilma Downtime

masilma (www307) encountered high load and was reset. Downtime was under 10 minutes.

[Jan 26, 2009, 11:50 AM] aedde Downtime

aedde (www84) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jan 26, 2009, 4:37 AM] mhoh Downtime

mhoh (www191) Encountered an error during operation and was reset. Downtime was about 5 minutes.

[Jan 25, 2009, 6:57 PM] somkix Downtime

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

[Jan 24, 2009, 11:22 PM] hasaya Downtime

hasaya (www364) crashed under high load and was rebooted. Downtime was under 10 minutes.

[Jan 24, 2009, 12:22 PM] thuule Downtime

thuule (www49) encountered an error while in service and was reset. Total downtime was less than 5 minutes.

[Jan 24, 2009, 12:09 PM] masilma Downtime

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

[Jan 24, 2009, 7:51 AM] Telephone System Maintenance Completed

As of 7:50 AM Eastern, all maintenance on our telephone system has been completed. All telephone services are operational at this time.

[Jan 24, 2009, 7:27 AM] Telephone System Maintenance

Beginning at about 7:30 AM Eastern, we will be performing maintenance on our telephone system. During this maintenance, there maybe be several brief periods in which we'll be unable to accept incoming support calls. We expect the maintenance period to last less than 15 minutes. We will, of course, be available via e-mail during this time.

[Jan 24, 2009, 3:49 AM] desu, taupo Downtime

desu (www474) and taupo (www426) encountered errors and were reset. Downtime was about 10 minutes.

[Jan 23, 2009, 8:33 PM] nyartu Downtime

nyartu (www254) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 23, 2009, 6:30 PM] eite Downtime

eite (www38) became unresponsive and was rebooted. Downtime was under 5 minutes.

[Jan 23, 2009, 2:09 PM] peulik Downtime

peulik (www360) became unresponsive while in service and was reset. Downtime was 15 minutes.

[Jan 23, 2009, 1:04 PM] fiann Downtime

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

[Jan 23, 2009, 12:28 PM] masilma Downtime

masilma (www307) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jan 23, 2009, 2:19 AM] borro, dyyme Maintenance Completed

The shadow drive swaps for borro and dyyme are complete. Downtime for each server was about 5 minutes.

[Jan 23, 2009, 1:04 AM] borro, dyyme Emergency Maintenance

borro (www489) and dyyme (www71) will be taken down shortly to swap out failing shadow drives. Downtime for each server should be under 10 minutes. An additional notice will be posted when the swaps are complete.

[Jan 23, 2009, 1:00 AM] fiann Downtime

fiann (www188) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 22, 2009, 11:37 AM] fiann Downtime

fiann (www188) became unresponsive under high load and needed to be rebooted. Total downtime was approximately 15 minutes.

[Jan 22, 2009, 10:00 AM] terfideu Downtime

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

[Jan 22, 2009, 12:20 AM] derba, yuki Downtime

derba (www104) and yuki (www493) encountered errors and were reset. Downtime was about 10 minutes for each.

[Jan 21, 2009, 2:52 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.

[Jan 21, 2009, 10:05 AM] ohayou Downtime

ohayou (www477) crashed due to an error and was reset. Downtime was about 5 minutes.

[Jan 21, 2009, 12:42 AM] yuki Downtime

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

[Jan 20, 2009, 8:16 AM] lehhdi Downtime

lehhdi (www267) experienced high load and was reset. Downtime was under 10 minutes.

[Jan 20, 2009, 6:15 AM] midori Downtime

midori (www492) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 20, 2009, 12:22 AM] yuki Downtime

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

[Jan 19, 2009, 4:11 PM] taupo Downtime

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

[Jan 19, 2009, 9:57 AM] muin Downtime

muin (www23) became unresponsive while in service and was reset. Downtime was under 10 minutes.

[Jan 18, 2009, 9:51 PM] fiann Downtime

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

[Jan 17, 2009, 9:46 AM] flure Downtime

flure (www75) became unresponsive while in service and was reset. Downtime was 10 minutes.

[Jan 17, 2009, 7:56 AM] eite Downtime

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

[Jan 17, 2009, 12:25 AM] wanote Downtime

wanote (www284) encountered an error and reset. Downtime was less than 10 minutes.

[Jan 16, 2009, 7:46 AM] uttu Downtime

uttu (www456) crashed while in service and had to be rebooted. Downtime was less than 5 minutes.

[Jan 16, 2009, 4:47 AM] auma Maintenance Completed

The chassis upgrade for auma is complete. It is now a P4 3.8 with 3GB of RAM. Downtime was under 10 minutes.

[Jan 16, 2009, 4:22 AM] auma Planned Maintenance

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

[Jan 16, 2009, 3:31 AM] ydhu Downtime

ydhu (www83) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 16, 2009, 3:16 AM] okathi, gamsi, muyal, thnad Maintenance Completed

Today's upgrades are complete. okathi and gamsi now have 160GB drives. muyal now has a 250GB drive, and a new shadow drive has been installed in thnad. Downtime for each server was about 5 minutes.

[Jan 16, 2009, 12:56 AM] okathi, gamsi, muyal, thnad Planned Maintenance

okathi (www411), gamsi (www289), and muyal (www236) will be taken down shortly for drive upgrades. thnad (www121) 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.

[Jan 15, 2009, 3:05 PM] fiann Downtime

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

[Jan 15, 2009, 12:13 PM] duwo Downtime

duwo (www219) became unresponsive under high load and needed to be rebooted. Total downtime was less than 10 minutes.

[Jan 15, 2009, 11:33 AM] hidari Downtime

hidari (www346) became unresponsive while in service and needed to be reset. Total downtime was about 5 minutes.

[Jan 15, 2009, 11:05 AM] sallane Downtime

sallane (www263) became unresponsive under high load, and was rebooted. Total downtime was about 20 minutes.

[Jan 15, 2009, 2:24 AM] hyarmen Downtime

hyarmen (www66) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 15, 2009, 12:56 AM] kaba Downtime

kaba (www394) encountered an error and was reset. Downtime was about 10 minutes.

[Jan 14, 2009, 11:40 PM] mhoh Downtime

mhoh (www191) was reset to clear an error condition. Downtime was less than 5 minutes.

[Jan 14, 2009, 3:04 PM] fiann Downtime

The server fiann(www188) crashed due to excessive load and was rebooted. The total downtime for this server was approximately 10 minutes.

[Jan 14, 2009, 11:59 AM] masilma Downtime

masilma (www307) crashed due to high load and was reset. Downtime was about 10 minutes.

[Jan 14, 2009, 6:08 AM] morx Downtime

morx (www198) encountered an error and was reset. Downtime was about 5 minutes.

[Jan 14, 2009, 2:41 AM] yitiya Maintenance Completed

The chassis upgrade for yitiya is complete. It is now a Core2 E6420 with 2GB of RAM. Downtime was about 5 minutes.

[Jan 14, 2009, 2:05 AM] yitiya Planned Maintenance

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

[Jan 14, 2009, 12:25 AM] zais Downtime

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

[Jan 13, 2009, 11:43 PM] lehhdi Downtime

lehhdi (www267) encountered high load and was reset. Downtime was under 10 minutes.

[Jan 13, 2009, 8:40 PM] midori Downtime

midori (www492) crashed and required a manual file system check. Downtime was about 25 minutes.

[Jan 13, 2009, 4:48 PM] sali Downtime

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

[Jan 13, 2009, 2:53 PM] fiann Downtime

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

[Jan 13, 2009, 12:45 PM] fiann Downtime

fiann (www188) crashed due to high load and was reset. Downtime was about 5 minutes.

[Jan 13, 2009, 11:10 AM] PHP 5.2.8

All shared servers will be upgraded to PHP 5.2.8 today. This is a minor upgrade and should not introduce any incompatible changes or cause any problems. Please contact support@pair.com if you have any questions.

[Jan 13, 2009, 10:18 AM] kaarei Downtime

kaarei (www300) encountered high load and was reset. Downtime was under 10 minutes.

[Jan 13, 2009, 8:44 AM] naam Downtime

naam (www114) encountered high load and was reset. Downtime was under 10 minutes.

[Jan 13, 2009, 5:58 AM] wokkil, margum, mhoh Maintenance Completed

Today's maintenance is complete. wokkil, margum, and mhoh each now have 160GB drives. Downtime for each server was about 5 minutes.

[Jan 13, 2009, 2:16 AM] wokkil, margum, mhoh Planned Maintenance

wokkil (www249), margum (www272), and mhoh (www191) 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.

[Jan 12, 2009, 11:41 PM] muin Downtime

muin (www23) became unresponsive while in service and was reset. Downtime was about 10 minutes.

[Jan 12, 2009, 9:03 PM] lehhdi Downtime

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

[Jan 12, 2009, 3:17 PM] midori Downtime

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

[Jan 12, 2009, 3:01 PM] amse Downtime

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

[Jan 12, 2009, 11:51 AM] masilma Downtime

masilma (www307) became unresponsive while in service and was reset. Downtime was under 15 minutes.

[Jan 12, 2009, 9:35 AM] thesel Downtime

thesel (www99) encountered an error and was reset. Downtime was under 10 minutes.

[Jan 11, 2009, 11:37 PM] umbar Downtime

umbar (www46) encountered an error and reset. Total downtime was approximately 10 minutes.

[Jan 11, 2009, 1:13 PM] ilwe Downtime

ilwe (www81) encountered high load and was reset. Downtime was under 15 minutes.

[Jan 10, 2009, 2:01 PM] beeoro Downtime

beeoro (www69) encountered an error and reset. Total downtime was approximately 10 minutes.

[Jan 10, 2009, 7:47 AM] quesse Downtime

quesse (www44) encountered an error and had to be rebooted. Downtime was about 10 minutes.

[Jan 9, 2009, 5:40 PM] bganat Downtime

bganat (www481) was rebooted to clear an error condition. Downtime was under 5 minutes.

[Jan 9, 2009, 4:50 PM] bganat Downtime

bganat (www481) crashed and required a manual file system check. Downtime was about 15 minutes.

[Jan 9, 2009, 8:33 AM] dair Maintenance Completed

The drive swap for dair (www20) has been completed. It now has a 200GB primary drive and a 250GB Shadow Drive. The total downtime was about 5 minutes.

[Jan 9, 2009, 8:11 AM] dair Emergency Maintenance

dair (www20) will be taken down momentarily to swap a failing drive. Another notice will be posted once the maintenance has been completed.

[Jan 9, 2009, 5:21 AM] namt, hyarmen, ittsui, kappa Maintenance Completed

Today's upgrades are complete. namt is now a Core2 E8200 with 2GB of RAM. hyarmen and kappa now have 160GB drives, and ittsui has a 250GB drive. Downtime for each server was about 5 minutes.

[Jan 9, 2009, 2:00 AM] namt, hyarmen, ittsui, kappa Planned Maintenance

namt (www196) will be taken down shortly for a chassis upgrade. hyarmen (www66), ittsui (www323), and kappa (www6) 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.

[Jan 9, 2009, 1:30 AM] iruvul Downtime

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

[Jan 9, 2009, 12:17 AM] muin Downtime

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

[Jan 9, 2009, 12:02 AM] thenge Downtime

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

[Jan 8, 2009, 4:38 AM] ocha, egon, huath Maintenance Completed

Today's upgrades are complete. ocha, egon, and huath all now have 160GB drives. Downtime for ocha and egon was about 5 minutes. A chassis problem was discovered with huath. It is now a P4 3.4 with 2GB of RAM. Downtime was about 20 minutes.

[Jan 8, 2009, 1:53 AM] ocha, egon, huath Planned Maintenance

ocha (www355), egon (www410), and huath (www19) 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.

[Jan 7, 2009, 10:17 PM] ohayou Downtime

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

[Jan 7, 2009, 10:14 PM] kaarei Downtime

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

[Jan 7, 2009, 9:23 PM] DB Server Maintenance Completed

The maintenance on db24, db25, db26, and db27 is now complete. These MySQL servers are now on a Core 2 E8200 with 4GB of RAM. Downtime for each server was less than 10 minutes.

[Jan 7, 2009, 8:37 PM] DB Server Maintenance

db24.pair.com, db25.pair.com, db26.pair.com, and db27.pair.com will each be offline for up to 15 minutes over the next 2 hours, as each is migrated to newer hardware. Another notice will be posted when this maintenance is complete.

[Jan 7, 2009, 3:34 PM] murifwae Downtime

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

[Jan 6, 2009, 9:27 PM] kaba Downtime

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

[Jan 6, 2009, 12:55 PM] ungkohe Downtime

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

[Jan 6, 2009, 3:39 AM] torbaane Maintenance Completed

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

[Jan 6, 2009, 3:12 AM] torbaane Emergency Maintenance

torbaane (www262) 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.

[Jan 5, 2009, 1:26 PM] dotya Downtime

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

[Jan 5, 2009, 1:15 AM] suteki Downtime

suteki (www339) Encountered an error during operation and was reset. Downtime was about five minutes.

[Jan 5, 2009, 1:06 AM] harma Downtime

harma (www50) Encountered an error during operation and was reset. Downtime was about five minutes.

[Jan 4, 2009, 1:12 PM] qatlh Downtime

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

[Jan 3, 2009, 11:18 PM] yinaska Maintenance Completed

The drive swap on yinaska (www363) is completed. It now has a 250GB primary drive. Downtime was under 10 minutes.

[Jan 3, 2009, 11:00 PM] yinaska Emergency Maintenance

yinaska (www363) will be taken down for an emergency drive swap. An additional notice will be posted once the swap is complete.

[Jan 3, 2009, 10:09 PM] sirung Downtime

sirung (www409) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 3, 2009, 9:22 PM] tehun Downtime

tehun (www226) crashed and was rebooted. Downtime was under 10 minutes.

[Jan 2, 2009, 3:59 AM] bellat Downtime

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

[Jan 1, 2009, 3:58 PM] gamma Downtime

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

[Jan 1, 2009, 1:03 AM] yuki Downtime

yuki (www493) crashed under heavy load and had to be rebooted. Downtime was about 5 minutes.

[Dec 31, 1969, 7:00 PM]

STAMP=1254975498 TAGS=249 TITLE=wokkil Downtime wokkil (www249) encountered an error and was reset. Downtime was about 5 minutes.

[Dec 31, 1969, 7:00 PM]

STAMP=1254552480 TAGS=175 TITLE=zulle Downtime zulle (www175) encountered an error and was reset. Downtime was about 5 minutes.

[Dec 31, 1969, 7:00 PM]

STAMP=1254981443 TAGS=122 TITLE=zatz Downtime zatz (www122) encountered an error and was reset. Downtime was about 5 minutes.

[Dec 31, 1969, 7:00 PM]

STAMP=1249623712 TAGS=198 TITLE=morx Downtime morx (www198) encountered an error and was reset. Downtime was about 15 minutes (required manual disk check).

[Dec 31, 1969, 7:00 PM]

STAMP=1256195066 TAGS=355 TITLE=ocha Planned Maintenance ocha (www355) will be taken down shortly to swap a shadow drive. Downtime should be under 10 minutes. An additional notice will be posted when the swap is complete.

[Dec 31, 1969, 7:00 PM]

STAMP=1247644608 TAGS=203 TITLE=shema Downtime shema (www203) encountered an error and was reset. Downtime was about 10 minutes

[Dec 31, 1969, 7:00 PM]

STAMP=1252137914 TAGS=367 TITLE=woolong Downtime woolong (www367) encountered an error and was reset. Downtime was about 5 minutes.

View Notices for 2008



 
» Support Home

» System Notices

» Network Status
» Server Status

» Site Search