Introducing t3.tigrisfiles.io for public content

Fresh Produce
1

:mega: Announcement

New Tigris accounts now serve public content from a dedicated domain: t3.tigrisfiles.io. This separates public content delivery from API infrastructure.

If you’re signing up today, your public buckets and public objects are served from t3.tigrisfiles.io automatically. All authenticated operations (uploads, SDK calls, CLI) continue to use t3.storage.dev — the only thing that changes is the URL you share for public access.

A few things to know:

  • Existing accounts are unaffected; your current URLs keep working
  • For production public content, we recommend setting up a custom domain
  • fly.storage.tigris.dev, used by many Fly.io users, follows the same rules. New accounts should use t3.tigrisfiles.io for public content instead.

Full details: Introducing t3.tigrisfiles.io for public content | Tigris Object Storage

3 Likes
Recurring TLS / ISP blocking on `t3.storage.dev`: what is the supported long-term endpoint for browser/public traffic?
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.