Skip to main content

Regions

Tigris is deployed globally across multiple regions. All regions are accessible through a single endpoint — t3.storage.dev — which handles routing automatically. You never need to specify a region in your SDK or CLI configuration; set the region to auto and Tigris takes care of the rest.

Bucket Locations

A bucket's location type controls how your data is distributed across regions. You choose a location type when you create a bucket, and it determines data placement, consistency, and availability.

Location TypeDescriptionRegions Used
Global (default)Data distributed globally, follows access patternsAll regions — data moves to where it's accessed most
Multi-regionTwo or more copies across regions in a chosen geography.Automatically selected within the geography
Dual-regionData residency across two specific regions of your choiceYour chosen regions
Single-regionData redundancy across availability zones in one regionOne region

For full details on each location type — including consistency models, availability guarantees, and cost — see Bucket Locations.

Available Regions

t3.storage.dev

GeographyCodeLocation
USAsjcSan Jose, California
USAordChicago, Illinois
USAiadAshburn, Virginia
EURamsAmsterdam, Netherlands
EURfraFrankfurt, Germany
EURlhrLondon, United Kingdom
Asia-PacificsinSingapore
Asia-PacificnrtTokyo, Japan

fly.storage.tigris.dev

GeographyCodeLocation
USAsjcSan Jose, California
USAordChicago, Illinois
USAiadAshburn, Virginia
EURamsAmsterdam, Netherlands
EURfraFrankfurt, Germany
EURlhrLondon, United Kingdom
Asia-PacificsinSingapore
Asia-PacificnrtTokyo, Japan
Asia-PacificsydSydney, Australia
South AmericagruSão Paulo, Brazil
AfricajnbJohannesburg, South Africa
note

If you need a region that isn't listed, contact us at help@tigrisdata.com to discuss your requirements.