This has got to be the biggest screw up ever by any cloud provider in history by sending customers into a panic, raising questions about aws accurate billing, wasting customer resources to desperately try and determine the source of the aws issue, causing customer cybersecurity investigations launched, canceled customer meetings to troubleshoot, no phone support for many affected, customers left with taking production services down rapidly in a effort to mitigate, ongoing poor communication by aws even as incorrect billing estimates are still emailed out and the website lists outrageous charges, and the very real health impact to any customer paying attention as they sort through all of this. This thread is literally full of people that claim they were close to having a heart attack. I can’t think of a worse customer experience. I will be deactivating my AWS account and finding a new cloud service provider. It is simply not worth this for aws.
@AWSSupport It's all fun and laughs until someone gets a heart attack.
AndI'm pretty sure someone did.
Unlike previous outages, heads MUST roll for this one.
Own your shit
@DivineNFTs_@MemeJobFun Not in the immediate future, unfortunately. After a token is created, we don't have the keys to change the token meta anymore (including socials and art work). We are looking into options to mitigate this, but it will take some time.
Shoutout to @BuilderLabs! For my latest project, https://t.co/YtRnzgvlfX, I used hashgraph-react-wallets, and the integration was seamless. Adding #Hedera wallets has never been easier.
@DudeInDaHoodie@MemeJobFun Sorry for that. There was an outage with the data feed. We had no choice but to suspend everything. Resolved as quickly as we could
@CyclopsIsBack@MemeJobFun Sorry for that. There was an outage with the data feed that was out of our control. We had no chance but to pause everything until we sorted it out.