Delays Starting Cloudflare Workers Builds

Google Cloud has made Spanner queues generally available, letting applications commit database changes and queued tasks together in one transaction. Messages support delayed delivery, SQL consumption and transactional acknowledgments for agent handoffs and other asynchronous workflows. Google specifies at-least-once delivery and at-most-once acknowledgment. External calls still need safeguards such as the idempotency key used in Google's example.

Google Cloud is previewing CPU startup boost for GKE, which temporarily increases container CPU requests and lowers them after readiness without restarting the container. It requires GKE 1.36.0-gke.4447000 or later; Standard clusters need Vertical Pod Autoscaling enabled, while Autopilot enables it by default. Boost policies support multipliers or fixed additions, and Autopilot workloads must still satisfy CPU-to-memory ratios.

Cloudflare has closed a network-performance incident affecting Madrid after reporting a fix on September 30. Its incident timeline records monitoring from 14:06 UTC that day and a resolved update at 05:42 UTC on October 2. The provider classified the incident as minor; its notice does not identify a root cause or quantify customer impact.

Cloudflare marked its Workers build-delay incident resolved at 21:27 UTC on October 1. The company had opened an investigation at 15:33 UTC on September 30, warning of potential effects on multiple customers, then moved to monitoring after implementing a fix at 17:42 UTC on September 30.

Cloudflare reports that an incident involving increased Durable Objects and R2 errors in Amsterdam was resolved on October 1 at 21:18 UTC. Its status history records an investigation beginning at 20:59 UTC and a fix entering monitoring at 21:06 UTC. Those updates do not identify a root cause or quantify affected customers.

In a Google Cloud customer account, PayPal describes migrating analytics workloads from on-premises Hadoop systems to Managed Service for Apache Spark. The company says the move consolidated fragmented workflows, shortened cluster provisioning and improved integration with Cloud Storage and BigQuery. PayPal reports a 25% improvement in core workload processing times, alongside lower operational overhead; those results reflect its own deployment.