[Fixed] Intermittent connectivity to Web346

Posted in Problems by

A new DDOS attack has commenced against Web346. The upstream threat mitigation system has been activated to try to identify and block the specific packets and flows responsible for the attack while allowing legitimate transactions to pass. Connectivity may be intermittent due to the scale of the attack. We’ll update this post as the situation progresses.

2013-03-20 17:26 UTC: The attack has subsided and normal connectivity has been restored.

-
-

[Fixed]Network Problems with Web346

Posted in Downtime by

Web346 is unresponsive as its network is affected by what look likes a bandwidth saturation attack as of now.

We are working to mitigate this problem with our datacenter now.

2013-02-26 13:22 UTC: We are still working on this issue.

2013-02-26 15:07 UTC: We block all malicious traffic to Web346 and all systems are back and online at the moment

2013-02-27 00:16 UTC: The attack on Web346 has resumed, and service is intermittent at this time. We are working to mitigate the effects of the attack at this time.

2013-02-27 01:06 UTC: The attack as subsided and Web346 is stable at this time. We’ll leave this post open until this issue is fully resolved.

2013-02-27 06:25 UTC: The attack is back again and we are working on it.

2013-02-27 10:50 UTC  The attack is still going  and the datacenter has not been able to stop it so we have decided to move this server to a datacenter which has better protection against denial of service attacks like this one. We are backing up the data and prepping the new machine now.

2013-02-27 11:00 UTC  There is a lot of data to migrate to the new server. If you would like your account to be migrated as a higher priority open a support ticket.

2013-02-27 17:07 UTC Some accounts have been re-enabled and we’re working on the other ones

s2013-02-27 18:12 UTC: The new server is now online and fully enabled.

-
-

[Fixed] Network outage affecting multiple servers

Posted in Downtime by

The following servers are currently offline due to a networking issue with our upstream provider:  web245, web246, web247, web345, web346, web347, web348, web349

We’ll update this post when we have more information.

2013-02-25 22:31 UTC: web245, web246, web247, web345, web347, web348, and web349 are back online. Web346 remains offline at this time.

2013-02-25 23:55 UTC: web346 is booting to a kernel panic, so our system administrators are booting it to a rescue environment for further troubleshooting.

2013-02-26 00:57 UTC: web346 is back online with a new kernel.

-
-

[Fixed] Intermittent network routing issues affecting several US servers

Posted in Problems by

Several of our US servers are currently experiencing intermittent network routing issues. Affected servers may include: Dweb100 Dweb101 Dweb102 Dweb104 Dweb105 Dweb110 Dweb111 Dweb112 Dweb113 Dweb114 Dweb115 Dweb116 Dweb117 Dweb118 Dweb119 Dweb120 Dweb121 Dweb122 Dweb123 Dweb124 Dweb125 Dweb126 Dweb127 Dweb128 Dweb129 Dweb130 Dweb133 Dweb134 Dweb135 Dweb137 Dweb140 Dweb141 Dweb142 Dweb143 Dweb144 Dweb145 Dweb146 Dweb147 Dweb149 Dweb150 Dweb151 Dweb152 Dweb153 Dweb154 Dweb158 Dweb160 Dweb161 Dweb162 Dweb163 Dweb164 Dweb91 Dweb92 Dweb93 Dweb94 Dweb95 Dweb96 Dweb97 Mailbox8 Web102 Web105 Web106 Web108 Web11 Web114 Web117 Web119 Web12 Web122 Web126 Web129 Web143 Web148 Web15 Web151 Web155 Web162 Web174 Web175 Web178 Web180 Web182 Web183 Web186 Web187 Web198 Web199 Web200 Web213 Web219 Web220 Web226 Web227 Web228 Web229 Web230 Web231 Web232 Web233 Web234 Web235 Web236 Web237 Web238 Web239 Web24 Web240 Web241 Web243 Web244 Web245 Web246 Web247 Web25 Web27 Web28 Web30 Web300 Web301 Web302 Web307 Web308 Web309 Web31 Web310 Web311 Web312 Web313 Web318 Web319 Web320 Web324 Web328 Web329 Web330 Web335 Web336 Web337 Web338 Web34 Web341 Web342 Web343 Web344 Web345 Web346 Web347 Web348 Web349 Web35 Web37 Web39 Web4 Web40 Web42 Web48 Web49 Web5 Web55 Web57 Web65 Web69 Web70 Web72 Web74 Web75 Web80 Web83 Web91 Web95 Web99

We’re working to resolve this issue and will update this post when we have more information.

2012-10-15 6:07 UTC: The problem was an issue with an upstream network carrier and has been resolved.

-
-