Guides / Working with data / Contexts and egress
Contexts and egress
Calls run in isolated, pre-warmed device contexts with city-level egress in 84 cities, so sessions stay consistent and results stay local.
LeanPool and FullPool
Gateway reads and primitives run on LeanPool contexts that we manage and rotate. Connected sessions run on FullPool: one dedicated context per session.
Supported cities
| Region | Cities |
|---|---|
US | miami, chicago, houston, dallas, phoenix, philadelphia, austin, jacksonville, columbus, charlotte, indianapolis, seattle, denver, boston, detroit, nashville, portland, atlanta, orlando, tampa, minneapolis, cleveland, baltimore, milwaukee, albuquerque, tucson, sacramento, oakland, fresno, irvine, anaheim, riverside, omaha, raleigh, louisville |
GB | london, manchester, birmingham, glasgow, liverpool, leeds, edinburgh, bristol |
DE | berlin, munich, hamburg, cologne, stuttgart, dusseldorf |
FR | paris, marseille, lyon, toulouse, nice |
CA | toronto, montreal, vancouver, calgary, edmonton, ottawa, winnipeg |
AU | sydney, melbourne, brisbane, perth, adelaide |
IT | rome, milan, naples, turin |
ES | madrid, barcelona, valencia, seville |
NL | amsterdam, rotterdam, utrecht, eindhoven |
BR | brasilia, fortaleza |
JP | tokyo, osaka, yokohama, nagoya |
Your own device
To keep requests on one device in your own client, provision one with POST /v1/devices/provision and reuse its device_id.