Regions
Section titled “Regions”Deploy Around the Globe
Section titled “Deploy Around the Globe”Enhance your app's performance by deploying to data centers around the world. Experience reduced latency and improved speed for all your users through our worldwide coverage of compute regions and content delivery network.
Compute Regions
Section titled “Compute Regions”Deploy your app close to your database and users in one of our four compute data centers strategically positioned around the world:
| Region | Location | Data Center Code |
|---|---|---|
| eu-central | Frankfurt, Germany | fsn1 |
| us-east | Ashburn, Virginia, USA | ash |
| us-west | Hillsboro, Oregon, USA | hil |
| ap-southeast | Singapore | sin |
Note: Singapore region (ap-southeast) coming soon. Contact us for more information.
Our global infrastructure is powered by Hetzner, providing reliable and high-performance hosting for your applications.
Content Delivery Network (CDN)
Section titled “Content Delivery Network (CDN)”Accelerate the delivery of static content to your users by leveraging our globally distributed CDN servers, strategically located in over 119 cities across more than 100 countries worldwide.
Our Global CDN is powered by Bunny CDN, ensuring fast content delivery with minimal latency.
CDN Locations
Section titled “CDN Locations”Europe
- Amsterdam
- Athens
- Belgrade
- Bratislava
- Brussels
- Budapest
- Bucharest
- Chisinau
- Copenhagen
- Dublin
- Frankfurt Volume
- Frankfurt
- Helsinki
- Keflavik
- Kyiv
- Lisbon
- Ljubljana
- London
- Luxembourg
- Madrid
- Marseille
- Milan
- Moscow
- Novi Travnik
- Nicosia
- Oslo
- Paris Volume
- Prague
- Riga
- Sofia
- Stockholm
- Vienna
- Vilnius
- Warsaw
- Zagreb
- Zurich
North America
- Ashburn
- Atlanta
- Boston
- Charlotte
- Chicago Volume
- Dallas Volume
- Denver
- Honolulu
- Houston
- Kansas City
- Los Angeles Volume
- Miami Volume
- Minneapolis
- Montreal
- New York
- Ogden
- Phoenix
- Pittsburgh
- San Jose
- Seattle
- Toronto
- Vancouver
Latin America (LATAM)
- Brasilia
- Bogota
- Buenos Aires
- Curitiba
- Fortaleza
- Guatemala
- La Paz
- Lima
- Mexico City
- Porto Alegre
- Quito
- Rio de Janeiro
- Salvador
- San Juan
- San Pedro
- Santiago
- Sao Paulo Volume
- Sao Paulo
Asia
- Almaty
- Baku
- Bangkok
- Bangalore
- Chennai
- Dhaka
- Hong Kong Volume
- Ho Chi Minh
- Istanbul
- Jakarta
- Karachi
- Kathmandu
- Kolkata
- Kuala Lumpur
- Manila
- Mumbai
- New Delhi
- Phnom Penh
- Seoul
- Singapore Volume
- Singapore
- Taipei
- Tbilisi
- Tel Aviv
- Tokyo Volume
- Ulaanbaatar
- Yangon
- Yerevan
Oceania
- Adelaide
- Auckland
- Brisbane
- Hagatna
- Melbourne
- Perth
- Sydney
Middle East & Africa
- Baghdad ISP
- Bahrain
- Cairo ISP
- Cape Town
- Dubai
- Fujairah
- Johannesburg
- Lagos
- Luanda
- Nairobi
- Riyadh
Volume locations indicate high-capacity edge servers for handling larger traffic loads.
ISP locations indicate servers hosted within internet service provider networks.
Egress IP Addresses for Database Whitelisting
Section titled “Egress IP Addresses for Database Whitelisting”When connecting your Sherpa.sh applications to external managed databases (e.g., Digital Ocean, AWS RDS, Azure Database), you may need to whitelist Sherpa.sh's egress IP addresses to allow incoming connections.
Current Status: Each region currently uses multiple IP addresses for outbound connections as applications scale horizontally. We are working to consolidate to a single static IP per region for easier management.
Current IP Addresses by Region
Section titled “Current IP Addresses by Region”eu-central
- 188.34.192.214
- 5.75.159.93
- 91.99.134.71
- 46.224.19.169
- 91.99.70.111
- 91.99.59.5
us-east
- 5.161.90.22
- 5.161.223.90
- 5.161.254.79
- 178.156.187.215
- 5.161.97.136
us-west
- 5.78.155.48
- 5.78.68.80
Wildcard Grant Option
Section titled “Wildcard Grant Option”If your database provider supports wildcard or CIDR block grants, you can use wildcard grants to avoid managing individual IP addresses. This is particularly useful during the transition period before single static IPs are available.
Example configurations:
- PostgreSQL:
host all all 0.0.0.0/0 md5(use with strong authentication) - MySQL:
GRANT ALL ON database.* TO 'user'@'%'(use with strong authentication) - MongoDB: Configure network access to allow all IPs temporarily
Important: When using wildcard grants, ensure you have robust authentication mechanisms in place (strong passwords, certificate-based auth, etc.) since IP filtering is no longer providing a security layer.
Important Security Notes
Section titled “Important Security Notes”- These IP addresses are used exclusively for application traffic within each region
- Add all listed IPs to your database's firewall/allowlist configuration
- Always use secure authentication credentials - IP whitelisting is just one layer of security
- SSL/TLS connections are strongly recommended for all database connections
- Monitor database access logs for unauthorized connection attempts
Need Help? Contact support for the current list of IP addresses for your region or if you need additional networking configuration.
Choosing the Right Region
Section titled “Choosing the Right Region”When deploying your application, consider the following factors for selecting a compute region:
- Location of your database and other infrastructure components. You want to minimize roundtrip latency from your applicaiton to your other infrastructure.
- Geographic location of your primary user base
- Regional compliance and data residency requirements
- Need for redundancy across multiple regions
By default, all CDN locations are enabled on each deployment.
For guidance on selecting the optimal deployment configuration for your specific needs, please contact our support team.