Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

GitHub: We're sorry (again) about (another) outage

Sky blue, oceans wet, code sharer unstable

GitHub has issued a mea culpa for the latest outage that left users unable to access the code-sharing site.

The company said that a power outage was to blame for Thursday's downtime. The issue did not go unnoticed.

On Friday, the text repository issued an explanation for the downtime.

"A brief power disruption at our primary data center caused a cascading failure that impacted several services critical to GitHub.com's operation," wrote systems director Sam Lambert.

"While we worked to recover service, GitHub.com was unavailable for two hours and six minutes. Service was fully restored at 02:29am UTC."

This wouldn't be the first time GitHub has gone down to the dismay of developers. The site has been a favorite target for DDoS attacks and staff wer recently criticized by users for being slow to fix its own code. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like