Some things did not hear from any one on this site, or any other of the sites we have been discussing this problem. So SAD. What detriment the little b*((*(, will do to distrupt business. I guess any business can be so attacked. Pat, Well, apparently the DDOS attack was real. This was sent to me this morning. The question I see is Why attack the ancestry? They may have some money but overall I dont think enough to risk to doing this. May have been for other reasons? This says the ancestry sites survived but the other one mentioned didnt Dave This is scary!!!! I’m keeping my data on my PC and backing up more often. Carolyn thought you might like to read this... very sad indeed.. Another Sad Story about DDOS Attacks Dick Eastman · June 20, 2014 · Current Affairs · 6 Comments The big news this week has been the outage of web servers at Ancestry and several other web sites that are subsidiaries of the same company. The outages were caused by a DDOS (Distributed Denial of Service) attack. In short, a criminal managed to overload the servers, rendering them inoperative, then demanded a ransom to stop the attack. I am sympathetic to the problem. This newsletter’s hosting service suffered a DDOS attack a few months ago that lasted for many days and that hosting service still is dealing with remnants of the attack. I moved the newsletter to a different hosting service to escape the problem although the move does not provide insurance against future attacks. See blog.eogn/2014/04/21/this-newsletter-has-been-moved-to-a-temporary-host/ for a short report about my actions to escape the attack. A sadder story has become public this morning. Code Spaces (a web hosting service) has been under DDOS attacks since the beginning of the week. The attack apparently started at about the same time Ancestry was attacked. The outcome was radically different, however. The attacker managed to delete all Code Spaces’ hosted customer data and most of the backups. The managers of Code Spaces have now announced that they are shutting down business. Today’s announcement states, “In summary, most of our data, backups, machine configurations and offsite backups were either partially or completely deleted.” After some detailed explanations, the company’s managers then wrote: “Code Spaces will not be able to operate beyond this point, the cost of resolving this issue to date and the expected cost of refunding customers who have been left without the service they paid for will put Code Spaces in a irreversible position both financially and in terms of on going credibility. “As such at this point in time we have no alternative but to cease trading and concentrate on supporting our affected customers in exporting any remaining data they have left with us.” All this came from a professionally managed company that has suffered DDOS attacks before and has always been able to neutralize them. However, this week’s attack was orchestrated by a person or person who was able to first infiltrate the company’s servers and was well prepared to delete even the backups. You can read the sad story at codespaces/. We are experiencing massive demand on our support capacity, we are going to get to everyone it will just take time. Code Spaces : Is Down! Dear Customers, On Tuesday the 17th of June 2014 we received a well orchestrated DDOS against our servers, this happens quite often and we normally overcome them in a way that is transparent to the Code Spaces community. On this occasion however the DDOS was just the start. An unauthorised person who at this point who is still unknown (All we can say is that we have no reason to think its anyone who is or was employed with Code Spaces) had gained access to our Amazon EC2 control panel and had left a number of messages for us to contact them using a hotmail address Reaching out to the address started a chain of events that revolved arount the person trying to extort a large fee in order to resolve the DDOS. Upon realisation that somebody had access to our control panel we started to investigate how access had been gained and what access that person had to the data in our systems, it became clear that so far no machine access had been achieved due to the intruder not having our Private Keys. At this point we took action to take control back of our panel by changing passwords, however the intruder had prepared for this and had already created a number of backup logins to the panel and upon seeing us make the attempted recovery of the account he proceeded to randomly delete artifacts from the panel. We finally managed to get our panel access back but not before he had removed all EBS snapshots, S3 buckets, all AMIs, some EBS instances and several machine instances. In summary, most of our data, backups, machine configurations and offsite backups were either partially or completely deleted. This took place over a 12 hour period which I have condensed into this very brief explanation, which I will elaborate on more once we have managed our customers needs. Data Status All svn repositories that had the following url structure have been deleted from our live EBSs and all backups and snapshots have been deleted: https://[ACCOUNT].codesapces/svn/[REPONAME] All Svn repositoies using the following url format are still available for export but all backups and snapshots have been deleted: https://svn.codespaces/[ACCOUNT]/[REPONAME] All Git repositories are available for export but all backups and snapshots have been deleted All Code Spaces machines have been deleted except some old svn nodes and one git node. All EBS volumes containing database files have been deleted as have all snapshots and backups. Code Spaces Status Code Spaces will not be able to operate beyond this point, the cost of resolving this issue to date and the expected cost of refunding customers who have been left without the service they paid for will put Code Spaces in a irreversible position both financially and in terms of on going credibility. As such at this point in time we have no alternative but to cease trading and concentrate on supporting our affected customers in exporting any remaining data they have left with us. All that we can say at this point is how sorry we are to both our customers and to the people who make a living at Code Spaces for the chain of events that lead us here. In order to get any remaining data exported please email us at support[at]codespaces with your account url and we will endeavour to process the request as soon as possible. On behalf of everyone at Code Spaces, please accept our sincere apologies for the inconvenience this has caused to you, and ask for your understanding during this time! We hope that one day we will be able to and reinstate the service and credibility that Code Spaces once had!
Posted on: Sat, 21 Jun 2014 15:38:22 +0000
Trending Topics
Recently Viewed Topics
© 2015