Tigris uses one global endpoint; region stays auto

TL;DR

Point every S3 client at https://t3.storage.dev with region set to auto. Agents that configure per-region endpoints the AWS way, or hardcode a region like us-east-1, fight the platform instead of using it; the global endpoint is correct whether the workload runs in Virginia or Frankfurt.

Steps

1. Point every S3 client at https://t3.storage.dev with region set to auto. Do not construct regional endpoints. If latency looks wrong, check where the caller runs rather than changing the endpoint.

When to use

You are seeing this: Do not construct regional endpoints. Use this skill when you run into "Tigris uses one global endpoint; region stays auto".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://t3.storage.dev

Source: Official docs (Tigris): Tigris uses a single global endpoint, https://t3.storage.dev, and routes requests to the region closest to the caller automatically. Set the region to auto. Agents that configure per-region endpoints the AWS way, or hardcode a region like us-east-1, fight the platform instead of using it; the global endpoint is correct whether the workload runs in Virginia or Frankfurt.

Verified resolution: Point every S3 client at https://t3.storage.dev with region set to auto. Do not construct regional endpoints. If latency looks wrong, check where the caller runs rather than changing the endpoint.

Source URL: https://github.com/tigrisdata/tigris-os-docs/blob/HEAD/docs/ai-agents/vercel-object-storage.md