> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/data-center/data-center-overview/regional-availability.md). # Regional availability *** Glesys operates five data centers across three regions and also has a presence in three partner data centers in three additional regions. {% tabs %} {% tab title="Glesys data centers" %} The following table displays each Glesys data center, its region, and its API/CLI slug: | Data center | Region | Slug | | ----------- | ------------------ | ------- | | FBG1 | Falkenberg, Sweden | dc-fbg1 | | STO1 | Stockholm, Sweden | dc-sto1 | | OUL1 | Oulu, Finland | dc-oul1 | | POR1 | Pori, Finland | dc-por1 | | TAM1 | Tampere, Finland | dc-tam1 | You can view the status of Glesys data centers on the [Glesys status page](https://status.glesys.com/). {% endtab %} {% tab title="Partner data centers" %} The table below lists each partner data center along with its region: | Data center | Region | Slug | | ----------- | ---------------------- | ------- | | AMS1 | Amsterdam, Netherlands | dc-ams1 | | LON1 | London, United Kingdom | dc-lon1 | | OSL1 | Oslo, Norway | dc-osl1 | You can view the status of Glesys data centers on the [Glesys status page](https://status.glesys.com/). {% endtab %} {% endtabs %} ### Products The table below summarizes our product availability, using the following keys: * :green\_circle: **Full availability.** All customers can create this resource in this data center. * :orange\_circle: **Limited availability**. There may be limited capacity in this data center, or the product may be in an earlier phase of the product lifecycle. * :blue\_circle: **Future availability**. We intend to offer the product in this data center in the future, but we don’t currently. * :red\_circle: **No availability**.
ProductFBG1STO1OUL1POR1TAM1AMS1LON1OSL1
VPS
KVM		πŸŸ’πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄πŸ”΄πŸ”΄
VPS
VMware		🟒🟒🟒🟠🟠🟒🟒🟒
VMware Cloud Director as a Service πŸŸ’πŸŸ’πŸ”΄πŸŸ πŸŸ πŸ”΄πŸ”΄πŸ”΄
Dedicated ServerπŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄
Object StorageπŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄πŸ”΄πŸ”΄πŸ”΄
ColocationπŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄
Remote HandsπŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄
FortiGate Firewall as a ServiceπŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄
Load BalancerπŸŸ’πŸŸ’πŸ”΄πŸŸ’πŸŸ’πŸ”΄πŸ”΄πŸ”΄
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.glesys.com/data-center/data-center-overview/regional-availability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.