••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
I feel bad for the people working on this. It sounds like desperation is increasing. From the 10:11:39 PM UTC update: Current status: We're continuing to pursue all available pathways to restore service, as our actions taken thus far have not provided the anticipated relief. Our investigation has found that a core process on the affected servers is becoming overwhelmed, which causes the servers to stop responding and contributes to the capacity loss. To validate a potential recovery approach, we're fully isolating a portion of our service infrastructure, restarting the affected components, and gradually reintroducing traffic to confirm our services remain stable before applying this approach more broadly. We're also analyzing traffic patterns across our entire service infrastructure and evaluating whether isolating traffic within each region may allow affected regions to recover independently. From the 9:41:46 PM UTC update: Current status: We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process. In parallel, we're assessing whether reverting the small number of recent configuration updates we identified could help accelerate recovery. From the 9:01:14 PM UTC update: Current status: We've validated an alternative health check method on a subset of affected infrastructure, which allowed the servers in that subset to successfully return to service, and we're now applying this change more broadly. We're also preparing an automated recovery process to continually detect and restart unresponsive servers, to help keep them in service while this change progresses. Additionally, our review of recent changes has identified a small number of configuration updates that we're investigating as potential contributors to the issue. From the 8:44 PM UTC update: Current status: While validating the targeted change, we found that many of the affected servers have become unresponsive, which is preventing us from confirming whether the change is effective. We're restarting these servers so they can come back online with the change in place, and we're applying the same approach to additional affected portions of our infrastructure to validate the results more broadly. Previous Status: While we haven't identified any recent changes that correlate with the start of impact, our investigation indicates the failed health checks may originate from a specific component on the affected servers that's responsible for processing them. We're deploying a targeted change to bypass this component on a subset of servers to validate whether this restores availability, and we've taken steps to prevent additional servers from being removed from service while we work to return the affected servers to service. We're also investigating why affected servers are experiencing elevated processor usage while handling requests.
•••••••••••••••••••••••••••••
It doesn't matter. The courts are entirely unfair. Take the copyright office's arguments: it states the court should explicitly address "Market Harm". Essentially, ANY fair use, such as AI training should be illegal, if it harms the market for the original authors EVEN WHERE THE LICENSE WOULD NORMALLY ALLOW THAT USE. That was reasoning applied to protect billionaire profits from the horror of library lending. The copyright office's position documents this extensively. https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-3-Generative-AI-Training-Report-Pre-Publication-Version.pdf See IV. Fair use, D. Factor Four In other words, no matter the license , the fact that OpenAIs fair use of the works for training MIGHT take opportunities from the plaintiffs should, BY ITSELF, be an argument to make that AI training illegal. Even if the software programmers agreed to allow AI training, then still sued OpenAI, that is a valid argument accepted from billionaire companies. In case you're wondering how the court argued that in this decision? It didn't. Not covered at all. Obviously brought up by the plaintiffs, not adressed. The weirdest pro-billionaire arguments are just accepted by the court (the big one is accepting AI models as making new works despite the copyright act clearly stating, 50+ times, only "natural persons" can make new works), and the most reasonable, long established principles, such as market harm (if the use of a copyrighted work harms its authors in the smallest way, even lost sales, even lost job opportunities, lost licensing opportunities, ...) is enough to forbid it's use EVEN WHERE THE LICENSE STATES DIFFERENTLY. This was required because they wanted to forbid digital lending out of Disney's movies, where the lending software would guarantee that only one copy is actually in circulation (ie. use of DRM to let a library just show a movie without the patron coming to the library to get it). In other words: when billionaires want to make money of works, and the first sale doctrine as well as long standing fair use principles for libraries were in the way, the courts declared that market harm superseded fair use. And, of course, suddenly, when it protects programmers from billionaires, it doesn't apply anymore. The courts deciding this way has done incredible damage to the availability of older works, to the point of destroying them entirely, since libraries cannot legally keep collections of older works and make those available over the internet, and it is impossible to keep the physical media in working condition and available over a large area, like the united states, for example. Repeating theme here: absurd arguments to protect billionaire profits, silently rejecting and ignoring reasonable arguments to protect normal people.
••
 Top