Data centres and locations

The public Data centre locations page lists the locations where we have a server in service, and says which products have room in each. Its Bare metal, colocation and IP transit section points to the sales team, which sells those (Bare metal, colocation and IP transit).

The header of the page counts the locations, the ones with room for a server now and the countries they are in. Where you can deploy comes next. Each card shows a location's airport code, such as FRA, its name, its country and its time zone. Under them, the card names the products that have room there now, such as "Room for Cloud Compute and App Deployment", or says "No room right now" when none of them has. A product has room when at least one of its plans can still be ordered there. The Data centres card of an order page lists the same locations, and shows which of them has room for the exact size you choose (Choose a location when you order). If the list cannot load, the page links to the order page instead.

A location appears when we have a server in service there. We list neither a location we are still setting up nor a place where we have no server.

Eight pages at /data-centers/<id> describe buildings as their operators state them, and the list above does not link to them. They show the operator's figures for power, space, certifications and connectivity, and say that these figures do not tell you which Coritan products run in the building. Talk to sales opens the sales contact form, and All locations goes back to the list.

• On the order page, choose a data centre under Data centres. Each location shows its airport code, such as FRA, its country and its local time. Order a service walks through the whole page.
• Choose the data centre closest to the people who will use the service. The address the service gets is local to that location's region.
• A location marked Sold out has no room for the plan you chose. Room differs by plan, so a different size or hardware tier may still fit.
• The list holds only locations where we run servers. Our network also reaches locations with no servers, which answer DNS and carry traffic; they are not listed, because you cannot order a server there.
• A floating IP comes from a pool in one region. Choose a pool in the region where the instance or server you attach it to runs (IP pools and regions).

GET /locations lists the active locations where we run servers, including one whose servers are all full. A location we are still setting up is not listed until it opens. It needs no access token. Add include_pops=true to list our network locations with no servers too, for example to write a DNS load balancing rule for one.

curl https://api.coritan.com/api/v1/locations

[
  {
    "id": 1,
    "code": "fra",
    "name": "Frankfurt",
    "country_code": "DE",
    "timezone": "Europe/Berlin",
    "latitude": 50.1109,
    "longitude": 8.6821,
    "lb_region_code": "WEU",
    "sort_order": 10,
    "is_active": true,
    "created_at": "2026-09-01T00:00:00",
    "updated_at": "2026-09-01T00:00:00"
  }
]

code

The location's airport code in lower case. An order names its location with this code.

country_code

The two-letter country code, such as DE.

timezone

The location's time zone, which the order page uses for its local time.

lb_region_code

The load balancing region the location is in (Region codes).

GET /locations/availability says which locations have room for a size, as Order a service describes.