GitHub is down

[justsaysmthng]

I hope the world realizes that clouds are not just fluffy white things in the blue sky, but can create destructive storms too, with wind, rain and so on.

Make sure your infrastructure is ready to weather such storms - have local backups and fallbacks, make sure your code is available even if github (or the Internet) goes down.

The more I hear 'cloud', the more I try to depend only on tools that work offline.

[eric001]

Metaphors like that only makes it even more confusing. It's a marketing scam, let's call it for what it is. Servers. They are servers.

[taneq]

Cloud have silver linings. They also evaporate or blow away without warning.

[robodale]

Well, then you need RainCloud.io™!!

It's the cloud-based offline tool storage platform that gives you access to your offline tools...from the cloud!!

[mserdarsanli]

Phew, I can't develop anymore but http://left-pad.io/ is still up so my systems continue operating.

[colinbartlett]

It's interesting to me to see all the services that depend on or integrate with GitHub in some way, as they all have problems at times like this.

My side project https://statusgator.com shows currently a dozen different services all posting warnings or down notices on their status pages. It's mostly CI services and the like, all which break in some way when GitHub is down.

[TeMPOraL]

> It's mostly CI services and the like, all which break in some way when GitHub is down.

It boggles my mind. If you're not adding a new dependency to the project, your CI server should never hit GitHub when doing builds. Who sets those things up without local cache?

[napsterbr]

And so is all Github-dependent deployment...

[zuppy]

We're using satis to create a mirror with all the required composer packages and we're deploying from there. https://github.com/composer/satis

The main reason that we switch to that was exactly to avoid deployment issues. Security is also a bonus (in case somebody modifies existing packages).

Probably there are tools like this for all type of packages.

[diegorbaquero]

Got here because of that haha, can't deploy. EDIT: Why downvote fellas?

[Bino]

Haha, I always feel guilty when this happens, I'm doing something and suddenly start getting errors, which just escalates on refresh and now everything is down :P

[chtoric]

You can also follow githubstatus on twitter: https://twitter.com/githubstatus

[oneeyedpigeon]

Interesting that one of the tweets uses identical wording to one of the status messages, and one doesn't. I would have assumed the tweets would be automated, but maybe there's a thinking that the message for the status bar isn't necessarily appropriate for Twitter, so it can be 'overridden'?

[dvhh]

updates : https://status.github.com/messages

[kome]

SourceForge is doing fine ;)

[dijit]

keeping a server running with a load average of 0 is easier than keeping a server running with a load average of 40.

[zodiakzz]

And so are my free private repositories on Bitbucket. :)

[Jean-Philipe]

Once the office router was down, we just pushed our commits to a USB stick. Worked pretty well.

[maccard]

The common complaint is that when github goes down so do issue trackers/project management/docs etc. What are the equivalent alternatives for these systems that are distributed, so tolerant to downtime.

If you are in a situation that you're using a DVCS but relying on centralised everything else, and saying that you're unable to work because your Issue tracker/CI server is down, have you really gained anything over the alternatives?

[CMay]

http://fossil-scm.org/

[akerro]

You can setup gitlab with clones, if one server goes down, second has a copy. You know, git is a distributed system, unlike github.

[Ianvdl]

The Web UI is still accessible for me, just extremely slow.

[romanovcode]

GitLab to the rescue!

[voctor]

Momentarily, yes. But it's just another central hub.

[rcarmo]

Or gogs, which is actually simpler to manage.

[paradite]

I pinged GitHub and it seems to be responding but the web UI is taking a few minutes to respond.

[jimjimjim]

Just a friendly reminder to store source locally.

Generally try not to put external services in a critical path.

[vacri]

Amazon oregon is down for me - can't get the EC2 status page... and the service outage page also has trouble loading...

http://status.aws.amazon.com/

[tiernano]

Status page[1] is now saying everything is operating normally... now waiting for the post mortum...

[1]:https://status.github.com/messages

[joncampbelldev]

Taking bets on if this is the chinese government testing out GreatCannon v2.0.0

[tankenmate]

Panama Papers anyone?

[tlrobinson]

git is decentralized, but a bunch of the supporting infrastructure GitHub provides, like Issues and PRs, isn't. It would be neat if that stuff were tracked in a git repository as well.

[qznc]

Is HN traffic significantly above average at the moment?

[kchoudhu]

If only we had a version control system that didn't rely on a central hub...

[cytzol]

We do, it's called Fossil! http://fossil-scm.org/

Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. You can then respond to tickets and perform repo maintenance offline, syncing everything to the server when you're back up.

Edit: A few weeks ago I got a job a one-hour train ride away. I can commit, close tickets, and write docs on my way in, sync everything to the internet when I get to work, then do the same on my way back - even though I don't have a net connection during my commute. It works great. (Ok, not as good as not having to travel at all, but great nonetheless!)

[petetnt]

We do. It's called Git.

[amelius]

See IPFS.

https://ipfs.io/

[sureshn]

its better to use fossil locally and have a mirror sync to github to run in the background. Its sad that git being distributed and github being a central place , sort of undermines the very purpose git was built for