GCP news and engineering summaries

Users report that Claude Code on a Pro Max 5x plan experiences rapid quota exhaustion, likely because cache_read tokens count at full rate against rate limits rather than at a reduced 1/10 rate. Background sessions and automatic context compaction further amplify token consumption, making the 1M context window unsustainable under current rate-limiting logic.

Usage-based services should enable hard monthly budget caps by default, automatically pausing applications or returning errors once limits are reached, rather than merely sending alerts. Runaway coding and personal agents can generate enormous API, compute, or storage bills. AWS has begun rolling out spend limits, while Google Cloud offers Spend Caps; broader availability and agent recommendations are encouraged.

Railway is recovering from a significant service disruption caused by a Google Cloud account suspension. The team successfully restored access to their compute workloads but is actively addressing persistent networking issues. Service is gradually returning, with temporary build throttling in place for non-enterprise users to ensure stability during the recovery process.

Google Cloud Console is experiencing issues loading essential JavaScript sources from gstatic.com. This failure typically occurs due to network administrator blocks on the domain or IP range, or temporary restrictions imposed by Google following excessive automated requests. Users are advised to contact their network administrators to resolve connectivity restrictions.