quay.io was down: https://status.redhat.com
AWS multiple services outage in us-east-1
331–340 of 1001 posts
Re: AWS multiple services outage in us-east-1
#332Re: AWS multiple services outage in us-east-1
#333Careful: NPM _says_ they're up ( https://status.npmjs.org/ ) but I am seeing a lot of packages not updating and npm install taking forever or never finishing. So hold off deploying now if you're dependent on that.
Re: AWS multiple services outage in us-east-1
#334Re: AWS multiple services outage in us-east-1
#335Re: AWS multiple services outage in us-east-1
#336Re: AWS multiple services outage in us-east-1
#337In this moments I think devs should invest in vendor independence if they can. While I'm not to that stage yet (cloudlfare dependence) using open technologies like docker (or Kubernetes), Traefik instead of managed services can help in this disaster situations by switching to a different provider in a faster way than having to rebuild from zero. as a disclosure I'm not still to that point on my infrastructure But I'm…
Re: AWS multiple services outage in us-east-1
#338Nowadays when this happens it's always something . "Something went wrong." Even the error message itself is wrong whenever that one appears.
"Too many requests. Your request has been rate limited, please take a break for a couple minutes and try again."
Re: AWS multiple services outage in us-east-1
#339funny that even if we have our app running fine in AWS europe, we are affected as developers because of npm/docker/etc being down. oh well.
What's the point of all the auto-healing node-graph systems that were designed in the 70s and refined over decades: if we're just going to do mainframe development anyway?