Regions
Request the browser placement your workflow needs.
Coming soon
Public dual-region deployment is not available yet. The routing API and local dual-region tests are implemented; deployment and qualification on both cloud providers are still pending.
With an initialized client:
await client.withSession({ region: "asia", timeoutSeconds: 300 }, async (session) => {
console.log(session.region);
});| Value | Behavior |
|---|---|
auto | Use trusted request location; fallback is west |
west | Request the instance's western pool |
asia | Request the instance's Asian pool |
Confirm enabled regions with your instance operator. An explicit region can have no free capacity; routing support does not mean both public pools are enabled.
Region is fixed for a session. Reconnecting returns to the original browser. Credits and concurrency remain shared across regions.
Timezone and egress location are separate settings; see configuration and proxies.