maybe you should host it with Azure?
-
-
Thanks. Twitter will use this to make your timeline better. Undo
-
-
-
What devastation for the clients who rely heavily on their service.
Thanks. Twitter will use this to make your timeline better. Undo
-
-
-
the company I work for is paralyzed thanks to your outage. It's unbelievable that
@Amazon doesn't have a fail over remote backup. -
no, *you* are supposed to have a failover setup, perhaps using another AWS region
-
go explain that to a company that generates millions of $ on daily and has a service that stretch across over 70 countries.
-
Well that's one more reason, if your company is doing so much money it should invest in a highly available setup.
-
you have a good point and that's the main reason of why they relay on Amazon. Anyways I am not the network manager.
-
AWS is great because it makes *possible* that kind of redundancy. But you have to use it & pay for it!
@Kedare@nicolas09F9
End of conversation
New conversation -
-
-
-
why do we have to politicize EVERY. FRICKING. THING.
-
tends to happen when your entire democracy is falling apart at the seams.
-
I can't help but feel that you are being a little melodramatic.
End of conversation
New conversation -
-
-
maybe CloudFront could have helped? :)
-
Not sure I would want to put a cache in front of a status page (which has to be very dynamic by definition).
-
I mean, at least for static assets?
-
For the static assets, for sure. But the "meat" of the status page are the status themselves :-)
-
and I'm sure those are not hosted on S3, we were talking about green vs. red icons :)
-
Not sure how this works but I assume this page is generated regularly with the correct statuses and stored on S3.
-
Because this is supposed to be the most reliable way of publishing a status page.
-
maybe we have a new anti-pattern now :)
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.