1. Available regions
| Region | Location |
|---|---|
Europe (eu) | European Union |
United States (us) | North America |
Asia (asia) | Asia Pacific |
The create form shows which regions are open and how many sites each has; a region that is not open yet shows as Coming soon. With the API, GET /api/v1/regions returns the same list. If you leave the region out when creating a database through the API, it is created in the EU.
2. Your data stays in the region you choose
- The database runs on servers in that region.
- The standby of a high-availability database is in a second site of the same region, never on another continent.
- Backups are stored in that region, encrypted with a key per database.
- Restores are created in the same region as the database they come from.
- Failover, recovery and plan changes never move your database to another region.
We do not replicate databases across regions. A synchronous standby on another continent would add a long round trip to every commit; keeping both servers in one region keeps commits fast while still protecting you from the loss of a site.
Keeping data in the EU
Databases in the EU region, and their backups, stay in the EU. If your databases hold personal data, our Data Processing Agreement under article 28 GDPR applies as part of the Terms of Service. Databases you create in the US or Asia region, and their backups, are stored there because you chose that region; the transfer safeguards for that are described in the DPA and the Privacy Policy.
Account data, such as your login and billing details, is handled as the Privacy Policy describes. The companies we use, what each one does and where, are listed on the Sub-processors page.
3. How to choose a region
Pick the region closest to the servers that run your application. Every query pays the network round trip between your application and the database, so the distance matters more than anything else.
To measure it, use Check latency from your servers on the create page: enter your server's public IP address and our servers in each region ping it five times. You see the result for each region, rated Good (under 50 ms) or Poor, before you choose. Your server must answer ICMP echo (ping) requests; some cloud firewalls block them by default, so allow ICMP echo from the internet for the check. With the API, send POST /api/v1/latency-checks with target (the IP address) and region, then poll GET /api/v1/latency-checks/{id}.
4. Changing region
A database cannot move between regions. Create a new database in the region you want and move your data with standard PostgreSQL tools such as pg_dump and pg_restore.
5. Region status
The status page shows each region's health, measured from our own monitoring, with 90 days of history and any open notices. You can follow incidents with its Atom feed.
More guides
- Quickstart: create a managed PostgreSQL database and connectCreate a managed PostgreSQL database on ElectraDB and connect from psql, Python, Node.js, Go or Java with verified TLS.
- Backups and point-in-time restoreHow ElectraDB backs up PostgreSQL continuously, and how to restore a database to any second of the last 7 days, even after deleting it.
- High availability and replication modesHow ElectraDB keeps PostgreSQL online with a standby in a second site, automatic failover, and sync, write or async replication.
- Security: TLS, passwords, IP allowlist and encryptionHow ElectraDB secures managed PostgreSQL: verified TLS, one-time passwords, IP allowlists, encrypted backups, API keys and two-factor sign-in.
- Plans, resizing and storage limitsChoose an ElectraDB PostgreSQL plan, change plans without downtime, and learn what happens when a database reaches its storage limit.
- When your database is fullA database that reaches its plan's storage becomes read-only. How to free space and get writes working again.
- Frequently asked questionsAnswers about ElectraDB managed PostgreSQL: high availability, backups, point-in-time restore, regions, security, plans and billing.