711–720 of 1001 posts
Technology leads to technology (and wealth) monopolies, in other words: more centralization. Which has always been bad.
Just like with Cloudflare leaking highly sensitive data all over the Internet, a couple of days ago.
When I go to my orders I get "There's a problem displaying some of your orders right now. If you don't see the order you're looking for, try refreshing this page, or click "View order details" for that order."
It seems that Amazon is eating its own dog food.
A piece of hard-earned advice: us-east-1 is the worst place to set up AWS services. You're signing up for the oldest hardware and the most frequent outages. For legacy customers, it's hard to move regions, but in general, if you have the chance to choose a region other than us-east-1, do that. I had the chance to transition to us-west-2 about 18 months ago and in that time, there have been at least three us-east-1 ou…
Earlier quoted context omitted.
(Disclaimer: I work for AWS.) The dashboard is not changing color due to the S3 issue. We're updating the banner in place of that. Edit: Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we u…
Maybe you could encourage your colleagues to host the status page outside of AWS?
Here we go again: Technology leads to technology (and wealth) monopolies, in other words: more centralization. Which has always been bad. Just like with Cloudflare leaking highly sensitive data all over the Internet, a couple of days ago.
But wait. Isn't S3 "the cloud". Everyone promised the cloud would never go down, ever. It has infinite uptime and reliability. Well good thing I have my backups on [some service that happens to also use S3 as a backend].
From https://status.aws.amazon.com/ : "Update at 12:52 AM PST: We are seeing recovery for S3 object retrievals, listing and deletions. We continue to work on recovery for adding new objects to S3 and expect to start seeing improved error rates within the hour." (I think the AM means PM)
> Update at 1:12 PM PST: S3 object retrieval, listing and deletion are fully recovered now. We are still working to recover normal operations for adding new objects to S3.
A piece of hard-earned advice: us-east-1 is the worst place to set up AWS services. You're signing up for the oldest hardware and the most frequent outages. For legacy customers, it's hard to move regions, but in general, if you have the chance to choose a region other than us-east-1, do that. I had the chance to transition to us-west-2 about 18 months ago and in that time, there have been at least three us-east-1 ou…
It's interesting to note the cascading effects. For example, I was immediately hit by three problems: * Slack file sharing no longer works, hangs forever (no way to hide the permanently rolling progress bar except quitting) * Github.com file uploads (e.g. dropping files into a Github issue) don't work. * Imgur.com is completely down . * Docker Hub seems to be unavailable. Can't pull/push images.