> For the complete documentation index, see [llms.txt](https://docs.neverinstall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neverinstall.com/server-locations.md).
# Server Locations
Neverinstall's global reach is facilitated by a network of servers located in various strategic locations around the world.
We initially launched with four server locations and, due to the high traffic we've been receiving, we've added more servers over time.
As of now, we have servers in the following nine locations:
1. 🇺🇸 **United States** - With servers in New York, Dallas, and North Virginia, we cover a broad swathe of the US, offering robust service to users across the country.
2. 🇮🇳 **India** - With servers in Bengaluru, Mumbai, Delhi, and Pune, we provide reliable and fast service to users in different parts of India.
3. 🇯🇵 **Japan** - Our Tokyo server provides service to our users in Japan, ensuring low latency and high performance.
4. 🇬🇧 **United Kingdom** - Our server in London caters to users in the UK and nearby regions.
5. 🇩🇪 **Germany** - Our Frankfurt server provides service to users in Germany and surrounding areas, ensuring optimal performance.
6. 🇫🇮 **Finland** - Our Finland server ensures our Nordic users enjoy low latency and high performance.
7. 🇨🇦 **Canada** - Our server in Montreal caters to our users in Canada, ensuring robust service across the country.
Our objective is to continue expanding our server locations to provide the best possible service to users worldwide. Stay tuned for more updates!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.neverinstall.com/server-locations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.