5 ms·

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 no

by toast76 16y ago

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.

emcooke 16y ago
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
- nopal 16y ago
  You were born to work at Twillio.
- aaronblohowiak 16y ago
  Why not stick an angel-mode Varnish in between? Serving stale blog is usually better than no blog!
  - emcooke 16y ago
    Yup, good idea. We set up an ngnix proxy to cache the page while the blog hosting provider fixes their server.
- oinksoft 16y ago
  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).
  - dmor 16y ago
    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
- markerdmann 16y ago
  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.
  - emcooke 16y ago
    Our main infrastructure is deployed on AWS but we have capacity at several cloud providers for load-balancing, redundancy, etc.
    - markerdmann 16y ago
      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?
    - chopsueyar 16y ago
      Eggs and baskets.
dpcan 16y ago
They mention twilio is working, their blog may be hosted another way.
- dmor 16y ago
  yep, our blog is hosted on a third party service completely unrelated to our website and APIs
  - johndyer 16y ago
    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
    - chadrs 16y ago
      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 http://en.wikipedia.org/wiki/Reverse_proxy
      - johndyer 16y ago
        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.
deleted 16y ago
[deleted]

by toast76 16y ago

emcooke 16y ago

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

nopal 16y ago
You were born to work at Twillio.
aaronblohowiak 16y ago
Why not stick an angel-mode Varnish in between? Serving stale blog is usually better than no blog!
- emcooke 16y ago
  Yup, good idea. We set up an ngnix proxy to cache the page while the blog hosting provider fixes their server.
oinksoft 16y ago
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).
- dmor 16y ago
  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
markerdmann 16y ago
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.
- emcooke 16y ago
  Our main infrastructure is deployed on AWS but we have capacity at several cloud providers for load-balancing, redundancy, etc.
  - markerdmann 16y ago
    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?
  - chopsueyar 16y ago
    Eggs and baskets.

dpcan 16y ago

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

dmor 16y ago
yep, our blog is hosted on a third party service completely unrelated to our website and APIs
- johndyer 16y ago
  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
  - chadrs 16y ago
    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 http://en.wikipedia.org/wiki/Reverse_proxy
    - johndyer 16y ago
      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.

deleted 16y ago

[deleted]