"This launch, at its core, is about taking our existing agents SDK and making it so it's compatible with all of these sandbox providers," Karan Sharma, who works on OpenAI's product team, told TechCrunch.
"We have identified an issue resulting in elevated errors on Claude.ai, including desktop and mobile. Users may experience errors when attempting to login, engaging with voice mode, or completing chats with Claude. We are working to resolve this issue as soon as possible."
From March 13 to March 27, users on Free, Pro, Max, and Team plans will get double the usage limits in a five-hour window when using Claude outside weekday hours between 8 AM and 2 PM ET. According to Anthropic, the promotion is automatic, and users don't have to enable anything to get the benefits.
In recent blog posts, both Uber ( Uber's Rate Limiting System), and OpenAI ( Beyond rate limits: scaling access to Codex and Sora) discuss shifts in their approach to rate limiting: moving from counter-based, per-service limits to adaptive, policy-based systems. Both companies developed proprietary rate-limiting platforms implemented at the infrastructure layer. These systems feature soft controls that manage traffic by asserting pressure on clients rather than utilizing hard stops - either through probabilistic shedding or credit-based waterfalls - ensuring system resilience without sacrificing user momentum.
This is a state where we see that the teams that move fastest will be the ones with clear tests, tight review policies, automated enforcement and reliable merge paths. Those guardrails are what make AI useful. If your systems can automatically catch mistakes, enforce standards, and prove what changed and why, then you can safely let agents do the heavy lifting. If not, you're just accelerating risk,
The issues we are seeing are related to Claude.ai and with the login/logout paths. Anthropic has not yet detailed what caused the outage, though the company said it has identified an issue and is implementing a fix.
Microsoft first acknowledged the issues at 0900 UTC (although the status page for the service stated it spotted the problem at 0922 UTC). At the time, Microsoft blamed the Azure OpenAI Service's availability issues on "an unhealthy backend dependent service, which led to cascading failures." The Windows behemoth noted problems when using modes such as GPT-5.2, GPT-5 Mini, GPT-4.1, and related APIs.
