Available Regions
Select from our high-performance data centers around the world:NORWAY-1
Europe RegionLocation: Norway, Europe
Available GPU Types: All GPUs Available
Best For: European users, GDPR compliance
Latency: Optimized for European traffic
CANADA-1
North America RegionLocation: Canada, North America
Available GPU Types: All GPUs Available
Best For: North American users
Latency: Low latency for Canadian and northern US users
US-1
United States RegionLocation: United States
Available GPU Types: All GPUs Available
Best For: US-based users and applications
Latency: Optimized for US traffic
Regional Specifications
| Region | Location | GPU Availability | Network | Compliance |
|---|---|---|---|---|
| NORWAY-1 | Europe | All GPU types | High-speed European network | GDPR compliant |
| CANADA-1 | North America | All GPU types | North American backbone | Privacy-focused |
| US-1 | United States | All GPU types | US domestic network | US data residency |
GPU Availability by Region
All regions support the complete range of GPU types:- H100 Series
- A100 Series
- Professional GPUs
Available in All Regions
- H100-SXM5-80GB
- H100-PCIe-NVLink-80GB
- H100-PCIe-80GB
- High demand GPU types
- Availability varies by time and region
- Check real-time availability during deployment
Region Selection Factors
Performance Considerations
Latency Optimization
Latency Optimization
Choose Based on User Location
- NORWAY-1: Best for users in Europe, UK, Middle East, and parts of Africa
- CANADA-1: Optimal for Canada, northern US states, and Alaska
- US-1: Best for continental United States and parts of Mexico
- Network round-trip time affects interactive applications
- SSH connections and real-time applications benefit from low latency
- Batch processing workloads are less sensitive to latency
Network Performance
Network Performance
Regional Network Characteristics
- European Network (NORWAY-1): High-speed connections to European internet exchanges
- North American Networks: Optimized routing for continental traffic
- Cross-region Traffic: Higher latency for intercontinental access
- Data transfer speeds for large datasets
- Real-time streaming and video processing
- API response times for web applications
Resource Availability
Resource Availability
Regional Capacity
- GPU availability varies by region and time
- Popular GPU types may have limited availability
- Consider backup region options
- Check availability during peak usage hours
Compliance and Legal
Data Residency
Geographic Data Requirements
- GDPR Compliance: NORWAY-1 for European data
- US Data Laws: US-1 for US-specific requirements
- Cross-border Restrictions: Consider data transfer regulations
- Industry Compliance: Healthcare, finance sector requirements
Privacy Regulations
Regional Privacy Laws
- European GDPR: Strict data protection in NORWAY-1
- Canadian PIPEDA: Privacy protection in CANADA-1
- US State Laws: Various state-specific regulations in US-1
- International Transfers: Consider data flow implications
Regional Pricing
Pricing is consistent across all regions for the same GPU types:Uniform Pricing: All regions offer the same pricing for identical GPU configurations. Choose based on performance and compliance needs, not cost differences.
Currency by Region
While pricing is uniform, billing currency is determined by your account country setting:- USD Billing
- EUR Billing
- INR Billing
US Dollar Accounts
- Most countries default to USD
- Consistent pricing across regions
- Standard international currency
Storage and Volume Considerations
Regional Storage
Important Storage Limitations:
- Storage volumes and snapshots are region-specific
- Volumes can only be attached to VMs in the same region
- Cross-region data transfer requires manual migration
- Plan your storage allocation based on primary region
Volume Management by Region
1
Plan Storage Strategy
- Choose primary region for most workloads
- Consider data gravity and access patterns
- Plan for disaster recovery needs
- Evaluate cross-region backup requirements
2
Create Regional Resources
- Create volumes in the same region as VMs
- Establish snapshots for backup and recovery
- Set up cross-region replication if needed
- Monitor regional storage usage
3
Optimize Access Patterns
- Keep data close to compute resources
- Minimize cross-region data transfers
- Use local storage for temporary data
- Plan for regional failover scenarios
Network and Connectivity
Regional Network Features
NORWAY-1 Network
European Connectivity
- Direct connections to major European internet exchanges
- Low latency to UK, Germany, France
- High-speed connections to Scandinavia
- Optimized for European CDN access
CANADA-1 Network
North American Connectivity
- Direct connections to Canadian internet infrastructure
- Low latency to northern US regions
- Optimized for cross-border North American traffic
- Good connectivity to major US cities
US-1 Network
US Domestic Network
- Direct connections to major US internet exchanges
- Optimized for continental US traffic
- Low latency to major metropolitan areas
- High-speed connections to cloud providers
Internet Connectivity Performance
Expected latency ranges from each region:| Source Region | To Europe | To North America | To Asia-Pacific |
|---|---|---|---|
| NORWAY-1 | 10-50ms | 100-150ms | 200-300ms |
| CANADA-1 | 80-120ms | 20-80ms | 150-250ms |
| US-1 | 100-150ms | 20-100ms | 150-250ms |
Latency values are approximate and depend on specific locations, network conditions, and routing paths.
Region Selection Best Practices
Decision Framework
1
Identify Primary Users
- Determine geographic location of primary users
- Consider time zones for interactive applications
- Evaluate access patterns and usage times
- Plan for global vs. regional applications
2
Assess Compliance Requirements
- Review data residency requirements
- Check industry-specific regulations
- Evaluate privacy law implications
- Consider cross-border data transfer restrictions
3
Evaluate Technical Requirements
- Assess latency sensitivity of applications
- Consider data transfer volumes
- Evaluate integration with other services
- Plan for disaster recovery needs
4
Test and Validate
- Deploy test VMs in candidate regions
- Measure actual performance characteristics
- Test connectivity from user locations
- Validate compliance and legal requirements
Multi-Region Strategy
Regional Redundancy
Regional Redundancy
Disaster Recovery Planning
- Deploy critical workloads in multiple regions
- Create cross-region backup strategies
- Plan for regional failover scenarios
- Test disaster recovery procedures regularly
Global Applications
Global Applications
Worldwide Service Delivery
- Deploy VMs in regions closest to user bases
- Use load balancing across regions
- Implement global content delivery strategies
- Consider data synchronization requirements
Development vs. Production
Development vs. Production
Environment Separation
- Use cost-effective regions for development
- Deploy production in regions closest to users
- Consider staging environments in production regions
- Plan for environment promotion workflows
Common Region Selection Scenarios
- European Business
- North American Startup
- Global SaaS
- AI Research
NORWAY-1 Primary ChoiceUse Case: EU-based company with European customers
Benefits:
- GDPR compliance by default
- Low latency for European users
- Data residency in Europe
- Integration with European services
- Higher latency for non-European access
- Plan for global expansion
Changing Regions
Current Limitations
Region Migration Constraints:
- VMs cannot be moved between regions
- Storage volumes are region-specific
- Snapshots cannot be transferred between regions
- Network configurations are regional
Migration Strategies
If you need to change regions after deployment:1
Plan Migration
- Create snapshots of current VMs
- Export important data and configurations
- Plan for service downtime
- Prepare new region resources
2
Recreate in New Region
- Deploy new VMs in target region
- Create new storage volumes as needed
- Restore data from backups
- Reconfigure applications and services
3
Update Configurations
- Update DNS and networking configurations
- Test connectivity and performance
- Update monitoring and logging
- Validate application functionality
4
Cleanup Old Resources
- Delete old VMs and volumes
- Clean up networking configurations
- Update documentation and procedures
- Monitor for any remaining dependencies
Choose your region carefully during initial deployment. While migration is possible, it requires significant effort and may involve service downtime.