DeepInfra

Inference locations

Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.

usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.

Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.

Declared countries or regions

United States; Canada (Toronto, announced capacity)
DeepInfra describes US infrastructure and announced its first international data center in Toronto on July 8, 2026. This is a provider footprint, not an exhaustive or model-specific placement list. DeepSeek V4.1 Flash placement has not been confirmed; do not declare this route US-only.

Can locations change?

Individual request placement and cross-country failover are not verified.

Provider region pinning

No self-service per-request region pin verified for this shared route.

Pinning through TrustedRouter

Not supported by the current TrustedRouter integration.

Infrastructure declaration

US infrastructure plus announced Canadian capacity; model-specific residency unconfirmed.

Evidence

Public provider statement. Reviewed 2026-09-27.

• DeepInfra infrastructure statement
• DeepInfra Toronto announcement

Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.