Hey, How can i know the region of my project deplo...
# ask-ai
e
Hey, How can i know the region of my project deployment, can i know it post creation, if yes walk me through the steps and tell me where.
✅ 1
t
Thanks for reaching out, Nilay. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I can help with that. You’re asking how to find the region where your LiveKit agent/project was deployed and whether you can check it after creation. Short answer: yes — you can see an agent’s deployment region after creation using the LiveKit CLI. What to check • The agent deployment region is set when you create the agent (via
lk 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:
Copy code
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:
Copy code
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 elements
e
Cool will do this, also can i know it from ui somehow?
t
Thanks — good follow-up. You’re asking whether the LiveKit Cloud UI can show the agent deployment region. Short answer: the LiveKit Cloud UI does not currently show the agent deployment region. The confirmed way to see an agent’s region after creation is with the CLI (
lk 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 elements
e
Thanks mate, appreciate it