DNS Issues with t-mobile's default DNS server

I'm not able to access console.storage.dev or t3.storage.dev through t-mobile's network. Is this a known issue? It was working fine last week so something changed. Switching to google's 8.8.8.8 or cloudflare's 1.1.1.1 works fine. Disabling that override and using my cellphone's default DNS (t-mobile) all of my assets are now broken image links. Is Tigris working to resolve this or do I need to work towards a workaround? Thanks!

@lethargicgeek Thanks for flagging this. We will take a look at it. Based on what you shared, it is possible that T-Mobile’s default DNS may be blocking our domain.

We’ll reach out to them about it but in the meantime, is it possible to use alternate DNS resolver like 8.8.8.8 or 1.1.1.1 that is working for you to avoid disruption while this is being sorted out?

We’ll keep you posted as we learn more.

@lethargicgeek OP•4/1/26, 12:11 PM

I'm using t3.storage.dev to serve presigned links from my app. It's hard to tell/instruct someone browsing the web to change their DNS settings. Should I be using some other domain or link through a proxy?

Hi,

A good test would be using other networks to access the service, it's very likely t-mobile has some wrong configs.

Are you using t-mobile wireless or home internet?

Would it be possible for you to setup custom domain? That should work for you. Instructions are here - Custom Domains

You can also use a custom domain with your bucket. To do this, the following

@lethargicgeek did you get a chance to try the workaround, or do you still see the issue?

Please let us know how it goes, also it'll be great if you can confirm it is t-mobile wireless for t-mobile internet.

Thanks.

Ended up switching to fly.storage.tigris.dev and have been good so far.