News for hackers. Stuff that matters.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by toast76 on Thursday April 21, 2011 @09:36PM (#2473018)
504 Gateway Time-out

nginx/0.9.2

You really want to make sure your shit works before you go boasting about how well it works. :)

EDIT: seems to be working now :P Interesting article once I got over the irony of it not working.

Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by emcooke on Thursday April 21, 2011 @10:03PM (#2473061)
Ironically, this highlights one of the main issues we discuss in the post!

The Twilio Engineering blog is hosted off an external Wordpress site with a single IP that's forwarded from ngnix load balancer pool. Since the load balancers assume that the external service can fail, they won't tied resources blocking access to other parts of the site.

Hope you enjoy the post :)

-Evan Twilio.com

Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by aaronblohowiak on Thursday April 21, 2011 @10:31PM (#2473124)
Why not stick an angel-mode Varnish in between? Serving stale blog is usually better than no blog!
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by emcooke on Thursday April 21, 2011 @10:38PM (#2473139)
Yup, good idea. We set up an ngnix proxy to cache the page while the blog hosting provider fixes their server.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by markerdmann on Thursday April 21, 2011 @11:51PM (#2473231)
Evan, I just noticed that your service seems to be running on Slicehost, not the AWS colo in Virginia. Is that correct? I got the opposite impression from your post, which seems to imply that Twilio is hosted on AWS, yet managed to weather the storm because of your design decisions.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by emcooke on Friday April 22, 2011 @12:00AM (#2473244)
Our main infrastructure is deployed on AWS but we have capacity at several cloud providers for load-balancing, redundancy, etc.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by markerdmann on Friday April 22, 2011 @12:29AM (#2473279)
Ah, I see it now. I just got a POST from one of your servers in the AWS US-West region. Is Twilio also hosted in US-East (the region affected by today's outage), and, if so, would Twilio have stayed up if it hadn't been spread across multiple regions?
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by chopsueyar on Friday April 22, 2011 @08:52AM (#2473895)
Eggs and baskets.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by oinksoft on Thursday April 21, 2011 @11:34PM (#2473207)
Speaking of highlighting, something about Disqus' markup/styles causes your blog text to be un-highlightable with mouse (Firefox 3.6.16 Debian 5.0.8).
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by dmor on Thursday April 21, 2011 @11:53PM (#2473232)
Thanks for the heads up, I've disabled Disqus comments for now... was also causing some issues for iPhone/iPad readers. Regular commenting is enabled
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by nopal on Thursday April 21, 2011 @10:14PM (#2473082)
You were born to work at Twillio.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by dpcan on Thursday April 21, 2011 @10:06PM (#2473065)
They mention twilio is working, their blog may be hosted another way.
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by dmor on Thursday April 21, 2011 @10:08PM (#2473071)
yep, our blog is hosted on a third party service completely unrelated to our website and APIs
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by johndyer on Thursday April 21, 2011 @10:28PM (#2473115)
dmor, really? It looks like the blog points to AWS, as does your API?

jdyer@aleph:~ [git:master] <ruby-1.9.2> » host api.twilio.com api.twilio.com is an alias for public-vip374d1ca4e.prod.twilio.com. public-vip374d1ca4e.prod.twilio.com is an alias for ec2-174-129-254-101.compute-1.amazonaws.com. ec2-174-129-254-101.compute-1.amazonaws.com has address 174.129.254.101 ----

jdyer@aleph:~ [git:master] <ruby-1.9.2> » host www.twilio.com www.twilio.com is an alias for public-vip29c4ab3d.prod.twilio.com. public-vip29c4ab3d.prod.twilio.com is an alias for ec2-174-129-253-75.compute-1.amazonaws.com. ec2-174-129-253-75.compute-1.amazonaws.com has address 174.129.253.75

Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by chadrs on Thursday April 21, 2011 @10:37PM (#2473136)
DNS lookups don't tell you anything here. The way a reverse proxy works is that HTTP requests to certain URLs get turned into an HTTP client request by the web server to the 3rd party provider (for caching, URL changing, compressing, terminating SSL, and get around firewalls). You can learn about them here: http://en.wikipedia.org/wiki/Reverse_proxy
Re:Why Twilio Wasn’t Affected by Today’s AWS Issues by johndyer on Thursday April 21, 2011 @10:58PM (#2473161)
True, and I had actually misread dmors' post entirely here; I read the post as stating Twilio's blog was not reliant on AWS in anyway, which would have been a misrepresentation in my mind. However in hindsight this was not the case, and I will certainly admit when I am wrong.