echoing-kilobyte-69895
04/01/2026, 9:17 AMtall-airline-16756
04/01/2026, 9:18 AMtall-airline-16756
04/01/2026, 9:18 AMlk agent create --region ...).
• You can view the region for existing agents with the LiveKit CLI.
Steps to check the region (CLI)
1. Open a terminal where the LiveKit CLI (lk) is configured and authenticated for your account.
2. Run:
lk agent status
• This command shows the deployment status and includes the region where that agent is running.
1. If you have multiple agents or need to inspect versions, run:
lk agent versions
• This will list deployed versions and deployment context; region information may appear there as well.
Notes and related info
• The project/server URL (for example, wss://your-project.livekit.cloud) does not indicate the agent region — agents can be deployed to regions independently of the project hostname.
• Available agent regions are: us-east (Virginia, USA), eu-central (Frankfurt, Germany), and ap-south (Mumbai, India).
• You can deploy multiple agents in different regions under the same project; each agent’s region is shown via the CLI commands above.
• Region pinning (locking media routing to a geographic region) is a separate feature and available on the Scale plan or higher.
If you’d like, tell me:
• Whether you’re using the CLI now and see any output from lk agent status (paste it here, redacting sensitive info), or
• If you prefer, I can walk you through authenticating the lk CLI and running the commands step‑by‑step. Sources: examples/drive-thru | livekit/livekit_composite | DeepWiki | Agents on LiveKit Cloud | Deploy voice AI on global infrastructure | LiveKi... | Understand and Improve Agent Latency | LiveKit | Checklist for Regional Deployments | LiveKit | Data Processing Addendum | LiveKit, with interactive elementsechoing-kilobyte-69895
04/01/2026, 9:19 AMtall-airline-16756
04/01/2026, 9:20 AMlk agent status).
What you can do in the UI
• Region pinning (media routing restrictions) can be viewed/changed in the dashboard on the Scale plan or higher. That setting controls where media servers route traffic, but it does not indicate where an AI agent was deployed.
What to do next
• Use the CLI to check agent regions:
a. Run lk agent status to see the agent’s deployment region.
b. Optionally run lk agent versions if you have multiple agents/versions.
If you’d like, I can:
• Walk you through authenticating and running lk agent status step‑by‑step, or
• Help interpret the output if you paste the command results (please redact any secrets)., with interactive elementsechoing-kilobyte-69895
04/01/2026, 9:20 AM