Why Twilio Wasn’t Affected by Today’s AWS Issues

Post by emcooke » Fri, Apr 22, 2011, 1:47 AM UTC

Post by egon_ » Fri, Apr 22, 2011, 1:59 AM UTC

Post by dpcan » Fri, Apr 22, 2011, 2:06 AM UTC

toast76 wrote: post #6

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.

Post by nopal » Fri, Apr 22, 2011, 2:14 AM UTC

emcooke wrote: post #15

toast76 wrote: post #6

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.

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

Post by johndyer » Fri, Apr 22, 2011, 2:28 AM UTC

dmor wrote: post #17

dpcan wrote: post #16

Earlier quoted context omitted.

They mention twilio is working, their blog may be hosted another way.

yep, our blog is hosted on a third party service completely unrelated to our website and APIs