19 comments

[ 0.22 ms ] story [ 54.6 ms ] thread
Also Github seemed down for parts of the morning.
I'm unable to resolve github.com currently from France, using Google DNS resolvers.
Say, is someone also DDoSing the npm registry? I get a bunch of 5xx errors...
Might just be a result of the dns issues?
related to DNS, having the same issue here trying to build a node app
Meanwhile, worker productivity mysteriously ticks up.
not everyone (I understand that might be a joke :-))

Right now I can't build nodejs apps because of unreachable external dependencies

Suddenly I feel the pain of having infrastructure-as-code hosted on github. Pagerduty was hosed too.
I'm seeing major sites like Paypal, Braintree and Twitter down. Is any of you noticing that too?
PayPal is down here in Dallas, TX. Twitter is having issues loading images.

Was going to move our websites over to a new server today but something tells me the timing might not be ideal...

Heroku was/is down. Apparently they missed the memo where a service provider like them is supposed to handle things like this for us and not keep all their eggs in one basket.

What cloud provider of PaaS uses a single company for their DNS? Pitiful.

I don't think Heroku has actually gone down.

We are on Heroku and have had some of our customers have access issues, but only a few.

Probably because GitHub was down? I could not attach buildpacks, but could change configs.
They use DynDNS to resolve all their internal services to AWS, so yes they were/are.

None of the toolbelt commands were working for us.

192.30.253.113 github.com 151.101.44.133 assets-cdn.github.com 54.236.140.90 collector.githubapp.com 192.30.253.116 api.github.com 192.30.253.122 ssh.github.com 151.101.44.133 avatars0.githubusercontent.com 151.101.44.133 avatars1.githubusercontent.com 151.101.44.133 avatars2.githubusercontent.com 151.101.44.133 avatars3.githubusercontent.com