Runtime changelog, 28 October 2026

What shipped in Runtime Cloud on 28 October 2026: sandboxes paused for more than an hour resume in under a second; sites that block by address are paced per outbound address; and a create whose sandbox is deleted while it starts returns 410 deleted.

Sandboxes paused for more than an hour resume in under a second

A paused sandbox's memory and disk now stay on its server until that server needs the room. Before, they were moved to off-site storage one hour after the pause, and a resume after that took 20 to 50 seconds while they were copied back. A sandbox whose server does need the room still resumes from its off-site copy, with its files and running programs intact.

Sites that block by address are paced per outbound address

Each outbound address shared by more than one account now opens at most 150 new connections an hour to Google, Bing, Amazon and the other sites that block by address, for all accounts together, and at most 100 an hour for any one account. This includes the addresses kept for scrapers, which had no limit, so one account's traffic could get such an address blocked for every account sent from it. Past a limit, a connection returns 429 Too Many Requests with X-Runtime-Egress: rate-limited:guarded-site and Retry-After. Before, one account could open 300 an hour from a shared address. A dedicated outbound address is not limited.

A create whose sandbox is deleted while it starts returns 410 deleted

If a sandbox is deleted before its own POST /v1/sandboxes returns, that create now returns 410 deleted with details.sandboxId. It previously returned 404 not_found. A create with getOrCreate: true whose name's holder is deleted while the create waits for it now creates a new sandbox instead of returning 404. See names.