Only when they would have thought the situation is under control, the world-famous code sharing website - GitHub got under a DDoS attack twice in a row in last two days. Launched with an aim of making software development more collaborative, GitHub has been the number one code repository for many programmers and tech enthusiasts. So, it being disrupted by distributed denial-of-service (DDOS) attacks often over the last few months, the word didn't take time to spread. In October 2012, the service has went down due to malicious hackers and later in March 2013, GitHub faced a "major service outage" because of a brief DDoS attack. However, during September, things appeared to have cooled down, the last attack being reported in late August.

Now, on October 2nd, 2013, the site was hit once again. The first issues were reported at 19:54 UTC. A few minutes later, the GitHub status page showed that the website was hit by a "large scale DDOS attack." The website was up and about in just ten minutes. We now know that the folks behind have managed to restore services so quickly because of their expertise on the solution, thanks to the repeated nature of the attacks. Check out the following series of status messages from the GitHub officials -
“The site remains available as we continue to mitigate a large and growing DDoS attack. There may be some isolated problems as we apply different mitigation strategies,” read a message posted at 20:23 UTC. Currently, GitHub appears to be working properly. We are sure that the brains on the back of the site are working hard to make sure that the frequency of the down-time is reduced, if not getting them eliminated completely.
In Feburary 2012, the site revealed a sustained attack that lasted for nearly a week. "This attack is global, and has been very intense at times. Yesterday morning, for example, github.com suddenly received requests from 10,000 times the number of clients it had handled the minute before," Jesse Newland wrote on GitHub’s blog. Let us just be sure that no data has been compromised during these or any previous DDoS incident.