[fixed] web530 and web561 offline

Posted in Downtime by

We are currently investigating the issue and will update as soon as we have further details.

2017-06-22 19:06 UTC: The servers are accessible again. There was a network issue that caused the temporary interruption.

-
-

[fixed] Partial incoming mail service disruption

Posted in Problems by

2017-06-20 20:44 UTC: A networking issue in one of our US data centers is affecting incoming mail service and webmail logins for some customers. We’re working to restore service and will update this post when more information is available.

2017-06-20 20:59 UTC: Service has been restored – we’ll continue to monitor.

2017-06-21 14:36 UTC: There have been no further disruptions, and the data center confirms that the networking issue is resolved.

-
-

[fixed] MySQL down on Web231

Posted in Problems by

2017-05-26 00:59 UTC: MySQL on Web231 is currently down. We’re working to restore service and will update this post when more info is available.

2017-05-26 01:13 UTC: We’re dumping and reloading all MySQL databases on Web231. The reload is halfway complete.

2017-05-26 01:25 UTC: All MySQL databases on Web231 have been restored and the MySQL service is now operational.

-
-

[Fixed] Multiple US servers offline

Posted in Problems by

2017-05-17 22:01 UTC: Several US shared and cloud servers in our St. Louis data center are currently offline We’ll update this post as soon as more info is available.

2017-05-17 22:07 UTC: The following servers are affected:

  • Shared: web537, web538, web539, web540, web541, web542, web543, web544, web545, web546, web547, web548, web549, web550, web551, web552, web553, web554, web555, web556, web557, web559, web560, web563, web590, web591, web592, web593, web594, web595, web596, web597, web598
  • Cloud: wf-207-38-86-39, wf-207-38-86-40, wf-207-38-86-43, wf-207-38-86-47, wf-207-38-86-48, wf-207-38-86-49, wf-207-38-86-73, wf-207-38-86-75, wf-207-38-86-76, wf-207-38-86-78, wf-207-38-86-79, wf-207-38-86-85, wf-207-38-86-88, wf-207-38-86-90, wf-207-38-86-92, wf-207-38-86-93, wf-207-38-86-94, wf-207-38-86-98, wf-207-38-86-102, wf-207-38-86-103, wf-207-38-86-104, wf-207-38-86-105, wf-207-38-86-106, wf-207-38-86-107, wf-207-38-92-110, wf-207-38-86-110, wf-207-38-86-111, wf-207-38-86-112, wf-207-38-86-114, wf-207-38-86-115, wf-207-38-86-116, wf-207-38-86-117, wf-207-38-86-118, wf-207-38-86-120, wf-207-38-86-121, wf-207-38-86-122, wf-207-38-86-123, wf-207-38-86-124, wf-207-38-86-125, wf-207-38-86-126, wf-207-38-86-127, wf-207-38-86-128, wf-207-38-86-129, wf-207-38-86-130, wf-207-38-86-131, wf-207-38-86-132, wf-207-38-86-134, wf-207-38-86-137, wf-207-38-86-139, wf-207-38-86-77, wf-207-38-86-135, wf-207-38-86-138, wf-207-38-86-140, wf-207-38-86-145, wf-207-38-86-147, wf-207-38-86-149, wf-207-38-86-150, wf-207-38-86-159, wf-207-38-86-160, wf-207-38-86-164, wf-207-38-86-165, wf-207-38-86-166, wf-207-38-86-167, wf-207-38-86-168, wf-207-38-86-170, wf-207-38-86-171, wf-207-38-86-175, wf-207-38-86-178, wf-207-38-86-180, wf-207-38-86-191, wf-207-38-86-193, wf-207-38-86-194, wf-207-38-86-195, wf-207-38-86-196, wf-207-38-86-197, wf-207-38-86-198, wf-207-38-86-199, wf-207-38-92-219, wf-207-38-92-220, wf-207-38-92-221, wf-207-38-92-222, wf-207-38-92-223, wf-207-38-92-224

2017-05-17 23:09 UTC: We’re still working with the data center to identify and resolve this issue. We’ll update this post as soon as more information is available.

2017-05-17 23:20 UTC: web537, web538, web539, web540, web541, web542, web543, web544, web545, web546, web547, web548, web549, web550, web551, web552, web553, web554, web555, web556, web557, web559, web560, web563, web590, web591, web592, web593, web594, web595, web596, web597, web598 are all back online.

2017-05-17 23:40 UTC: All US servers are back online at this time. We will continue to monitor and update this post if there are further developments.

-
-

[fixed] web513 inaccessible

Posted in Downtime by

The server is currently not accessible. We are looking into this and will update as soon as we have further details.

2017-05-15 14:59 UTC: We are still investigating the issue.

2017-05-15 17:20 UTC: Our datacenter technicians are working directly to power on the server.

2017-05-15 20:17 UTC: The server is accessible again.

-
-

[Done] Emergency network maintenance affecting several EU servers

Posted in Downtime by

2017-04-27 00:20 UTC: At the present time, emergency network maintenance in our EU datacenter has caused several EU servers to go offline. We’ll update this post as more information becomes available.

2017-04-27 00:29 UTC: Connectivity has been restored, we’ll continue to monitor.

-
-

[Fixed] web567 inaccessible

Posted in Downtime by

The server is currently not accessible. We are looking into this and will update as soon as we have further details.

2017-04-26 00:04 UTC: The servers is back online.

-
-

[Fixed] Web474 inaccessible

Posted in Downtime by

The server is currently not accessible. We are looking into this and will update as soon as we have more details.

2017-04-21 17:37 UTC: The servers is back online.

-
-

[Fixed] Incoming mail service disruption

Posted in Problems by

2017-04-03 19:03 UTC: At the present time, some of our mail.webfaction.com IMAP/POP proxies are not functioning. We’re working to resolve this and will update this post as soon as more information is available.

2017-04-03 20:14 UTC: The problem was caused by a fault in our monitoring systems. The fault has been corrected and IMAP/POP services are functioning normally.

-
-

[Fixed] Web346 offline

Posted in Downtime by

2017-03-16 20:01 UTC: The networking services on Web346 are currently down and the machine is offline. We’re working to restore service at this time and will update this post when more information is available.

2017-03-16 22:06 UTC: Web346 is back online after our upstream network provider reconfigured a switch. We’ll continue to monitor for signs of trouble.

2017-03-16 22:26 UTC: Web346 has gone offline again. We’re working to restore service at this time and will update this post when more information is available.

2017-03-16 23:25 UTC: We’re still investigating the connectivity issue.

2017-03-17 00:24 UTC: We’re still investigating the connectivity issue.

2017-03-17 01:44 UTC: We’ve switched Web346 to a different OS kernel and it seem to be stable now. We’ll continue to monitor.

2017-03-17 15:43 UTC: Several hours ago, we determined that Web346 was being attacked. At that time, we took steps to mitigate the attack, and the server has been stable since then. We’ll continue to monitor.

2017-03-24 15:22 UTC: We’ve not seen any further issues over the past several days.

-
-