4 ms·
Heroku is partially down (my site unresponsive)
- jgilliam 16y agoAmazon is having problems, it's impacting Heroku and many others.
- msie 16y agoLike Reddit.
- erikpukinskis 16y agoNewRelic is also having trouble: http://rpmstatus.newrelic.com/2011/02/17/having-trouble-with-a-database/ http://rpmstatus.newrelic.com/2011/02/17/having-trouble-with... Not sure if these things are related.
- thetrumanshow 16y agoI saw this blip as well. Spreedly was telling me it couldn't talk to my server for around 17 minutes. 8:04pm-8:21pm PST
- nathanh 16y agoI removed New Relic temporarily and redeployed, and Heroku is working for one of my sites now (also not working for another site though).
- towelrod 16y agoThat's interesting. Installing New Relic makes your site dependent on New Relic's availability? That's kinda scary... Of course its also possible that you just got lucky and Heroku came back up for you when you redeployed. Could be a coincidence.
- mickeyben 16y agoWe had the same issue at the Seesmic Web launch 2 years ago and uninstalling new relic fixed the issue. But the guys at New Relic helped us and fixed the issue, according to them it should not happen anymore.
- Serbocro 16y agoThe New Relic agent should never have an affect on whether or not your application runs. If you think this is happening, please email us at support@newrelic.com so we can help figure out what is going on.
- erikpukinskis 16y agoSupposedly fixed now (see OP).
- jessor 16y agohttp://status.aws.amazon.com/ http://status.aws.amazon.com/
- kowsik 16y agoOkay, geolookup on Heroku's proxy IP says seattle, but EC2 doesn't have a region there! Is Heroku running their own data center there? Curious...
- diego 16y agoproxy.heroku.com -> 75.101.145.87 NetRange: 75.101.128.0 - 75.101.255.255 CIDR: 75.101.128.0/17 OriginAS: NetName: AMAZON-EC2-4 (from whatismyip.com)