MiniMax runs data centers across four continents. US West, US East, EU Frankfurt, and Asia Singapore provide full-service API access with latency-optimized routing, data residency controls, and multilingual language support for 18 languages.
MiniMax operates four fully independent data centers worldwide, each delivering the complete MiniMax service catalog with region-specific latency profiles.
US West (Oregon) anchors the North American West Coast and Pacific traffic. This region serves customers from Vancouver to San Diego with p50 latency of 30-50ms for standard API calls. The Oregon facility runs on NVIDIA H100 GPU clusters with redundant power and cooling. Peak capacity handles 12,000 concurrent inference requests across all model variants. The US West endpoint also serves as the primary failover target for Asia Singapore during scheduled maintenance windows.
US East (Northern Virginia) covers the Eastern United States, Canada, and Latin America. Latency from New York, Toronto, and Miami averages 25-45ms. This region hosts the largest GPU deployment across all MiniMax facilities with 18,000 concurrent request capacity. Video generation workloads are concentrated in US East due to the higher GPU memory requirements of the diffusion pipeline. Enterprise customers with North America-only traffic often pin to US East for the lowest p95 latency within the continent.
EU Frankfurt serves the European Economic Area, the United Kingdom, and parts of the Middle East and Africa. Intra-EU latency runs 20-40ms from major cities including London, Paris, Berlin, and Amsterdam. The Frankfurt data center complies with GDPR data processing requirements and maintains ISO 27001 certification with annual third-party audits. Data residency controls are available for all EU Frankfurt deployments — API requests and model outputs remain within the EU region when residency is enabled per project.
Asia Singapore covers Southeast Asia, East Asia, South Asia, and Oceania. Intra-region latency is 15-35ms from Singapore, Jakarta, Bangkok, and Manila. Connections from Tokyo, Seoul, and Shanghai range from 60-85ms. Connections from Sydney and Melbourne average 95-120ms. The Singapore facility handles the highest volume of multilingual traffic, with Chinese, Japanese, and Korean language requests comprising 55% of regional API calls. Cross-region routing from Asia Singapore to US West adds approximately 140ms of network latency.
MiniMax global infrastructure spans four regions: US West (Oregon, 30-50ms West Coast), US East (Virginia, 25-45ms Eastern NA), EU Frankfurt (Germany, 20-40ms intra-EU, GDPR compliant), and Asia Singapore (15-35ms Southeast Asia). All four regions run identical MiniMax software stacks with cross-region failover and data residency configuration per project.
MiniMax latency varies predictably by region and geographic distance. Choose the closest region or use the global endpoint for automatic DNS-based routing.
Latency to each MiniMax region follows a predictable pattern based on network distance. US West handles West Coast traffic fastest, US East for Eastern North America, EU Frankfurt for Europe, and Asia Singapore for APAC. The global endpoint api.minimax.gr.com uses DNS geolocation to resolve to the nearest healthy region. When a region experiences elevated latency above 200ms p95, the global endpoint automatically fails over to the next closest region. Failover typically completes within 60 seconds of threshold breach.
For latency-sensitive applications, pin requests to the closest region by using its dedicated subdomain: us-west.api.minimax.gr.com, us-east.api.minimax.gr.com, eu.api.minimax.gr.com, or asia.api.minimax.gr.com. Pinned traffic does not fail over automatically — you must handle region fallback in your application code. The platform hub displays current p50 and p95 latency to each region from your approximate location, updated every 60 seconds. Historical latency data is available as CSV export for the trailing 30 days.
MiniMax generates text in 18 languages with English-optimized models achieving the highest quality. Data residency controls let enterprises restrict processing to specific regions.
MiniMax-Text-01 produces content in 18 languages. English output scores highest across all benchmarks; Chinese, Japanese, Korean, French, German, and Spanish follow.
MiniMax-Text-01 handles text generation in 18 languages: English, Chinese (Simplified and Traditional), Japanese, Korean, French, German, Spanish, Italian, Portuguese, Dutch, Russian, Arabic, Hindi, Vietnamese, Thai, Turkish, Polish, and Swedish. English-language generation achieves the strongest benchmark scores across all evaluation categories. Multilingual performance tiers: Chinese, Japanese, Korean, French, German, and Spanish score within 5-8% of English on MMLU-style evaluations. Italian, Portuguese, Dutch, Russian, and Polish score within 10-15%. Arabic, Hindi, Vietnamese, Thai, Turkish, and Swedish score within 15-22%.
Language quality varies significantly by task type. Translation between supported languages performs well across all pairs, with English as the strongest pivot language. Code generation works best when prompts and output are in English; non-English code generation often produces mixed-language results. Mathematical reasoning in Chinese, Japanese, and Korean approaches English-level accuracy. Creative writing and summarization quality correlate with the volume of training data available for each language. The developer resources section includes per-language quality benchmarks and recommended prompt strategies for non-English use cases.
Configure data residency per project to restrict all processing to a specified region. EU Frankfurt supports GDPR-compliant deployment with full audit trail.
Data residency is configured in the platform hub under Project Settings. When enabled for a specific region, all inference requests, fine-tuning jobs, video generation batches, and model outputs are processed and stored exclusively within that region's data centers. No data crosses regional boundaries. Usage logs and billing metadata can be configured to remain within the designated region or centralized for consolidated reporting. Residency settings apply to all API keys within a project and cannot be overridden per key — this prevents accidental cross-region data egress.
EU Frankfurt provides GDPR-compliant infrastructure with documented data processing agreements, Data Protection Impact Assessments, and Standard Contractual Clauses for cross-border transfers where applicable. The Frankfurt facility undergoes annual SOC 2 Type II and ISO 27001 audits with reports available to enterprise customers under NDA. US regions maintain SOC 2 Type II compliance for customers subject to US data protection frameworks. Asia Singapore complies with Singapore's Personal Data Protection Act and supports ASEAN cross-border data flow frameworks. Custom compliance documentation for specific regulatory regimes is available through enterprise support.
Complete reference of MiniMax data center locations with supported languages, latency tiers, and API endpoint URLs.
| Region | Location | Languages Supported | Latency Tier |
|---|---|---|---|
| US West | Oregon, United States | All 18 languages | 30-50ms (West Coast NA) |
| US East | Northern Virginia, United States | All 18 languages | 25-45ms (Eastern NA) |
| EU Frankfurt | Frankfurt, Germany | All 18 languages | 20-40ms (Intra-EU) |
| Asia Singapore | Singapore | All 18 languages | 15-35ms (Southeast Asia) |
MiniMax operates data centers in four regions: US West (Oregon), US East (Northern Virginia), EU Frankfurt (Germany), and Asia Singapore. Each region provides full access to all MiniMax services including text generation, chat completion, video generation, and model fine-tuning. Regional API endpoints route requests to the nearest data center. Enterprise customers can select specific regions for dedicated deployment with reserved GPU capacity and data residency guarantees.
MiniMax latency varies by region and endpoint proximity. US West serves North American West Coast at 30-50ms p50. US East covers Eastern NA at 25-45ms. EU Frankfurt handles European traffic at 20-40ms within the EU and 70-100ms from North America. Asia Singapore serves APAC at 15-35ms within Southeast Asia and 90-130ms from North America. Cross-region failover automatically routes traffic to the next closest available region if latency exceeds 200ms.
MiniMax supports data residency controls that let enterprise customers specify which regions process and store their data. When data residency is enabled, all API requests, model inference, and generated outputs are processed exclusively within that region's infrastructure. Batch jobs, fine-tuning runs, and video generation outputs remain within the specified region. Usage logs and billing data can stay within the same region or consolidate centrally. Data residency is configured per project in the platform hub.
MiniMax supports text generation in 18 languages: English, Chinese (Simplified and Traditional), Japanese, Korean, French, German, Spanish, Italian, Portuguese, Dutch, Russian, Arabic, Hindi, Vietnamese, Thai, Turkish, Polish, and Swedish. English-optimized models deliver the highest quality output scores. Multilingual performance is strongest for Chinese, Japanese, Korean, French, German, and Spanish. Language quality varies by task — code generation and mathematical reasoning work best in English.
MiniMax provides regional API endpoints with dedicated subdomains for each region. For automatic routing to the nearest healthy region, use the global endpoint which resolves to the closest data center based on DNS geolocation. You can pin requests to a specific region by using its dedicated subdomain. The platform hub displays current latency to each region. Enterprise accounts can configure custom CNAME records for branded API endpoints.