Practically unusable for large parts of the day. Becoming a real annoyance. Looks like their move to Rackspace is not a moment too soon. If I was paying for this, I would not be happy.
Posts Tagged ‘github’
GitHub’s really fucked today
Friday, September 18th, 2009More Github failures
Sunday, August 24th, 2008Output from my trusty svn_up script, which also pulls git:
git detected in arkx executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in arkx, retry manually? git detected in couchrest executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in couchrest, retry manually? git detected in globalite executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in globalite, retry manually? git detected in masquerade executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in masquerade, retry manually? git detected in rack executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in rack, retry manually? git detected in relaxdb executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in relaxdb, retry manually? git detected in rest-client executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in rest-client, retry manually? git detected in thin executing: git pull github.com[0: 65.74.177.129]: errno=Connection refused fatal: unable to connect a socket (Connection refused) !!! command ‘git pull’ failed in thin, retry manually?
Does anyone else think that it is not really acceptable for a large number of important source repositories to just go down at the drop of a hat?
UPDATE: from github.wordpress.com:
github 7:46 pm on August 23, 2008 | 0 | # |
We’ve taken the site down for approximately 3 hours while we’re upgrading our servers.
THREE HOURS??!!!
Github becoming more unreliable
Sunday, August 3rd, 2008
Gee, I guess centralising source control around a single website might have some downsides after all.