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

You may sign up to receive these notices via e-mail; this assures that you will see each notice as soon as it is posted. The notices are also posted to the "pair.notices" newsgroup on our customer news server, and available as an RSS feed.

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

FreeBSD 6.2 Upgrade Announcement - we will be upgrading all user servers to FreeBSD 6.2 over the coming months.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

View Older Notices



 
» Support Home

» System Notices

» Network Status
» Server Status

» Site Search