Your services are all deployed and running normally on our side. NXDOMAIN on .up.railway.app domains means the DNS resolver on the affected network is failing to return records for those hostnames, not that anything changed with your services or plan. Railway serves *.up.railway.app via wildcard DNS, so the records exist but AT&T's resolver is not returning them. You can confirm this by switching the affected devices to a public DNS resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8), which should resolve the domains immediately.

I appreciate the quick response. Unfortunately, switching DNS resolvers on my browser is the first think I tried and I saw no resolution. I understood the services were all deployed correctly, but this is a big issue if a significant portion of US network traffic is unable to access API services that are not deployed behind non-railway domains. Please escalate if you can.

To correct our earlier reply, we understand AT&T mobile data is also affected, not just WiFi. Your services are all deployed and healthy. Railway's wildcard DNS for *.up.railway.app resolves correctly from public resolvers, confirming this is AT&T's network filtering those domains at the resolver level. On mobile carrier networks, DNS is often transparently proxied by the carrier, which is why changing the resolver on-device or in-browser did not help. This is not something we can fix from our side since the filtering is happening within AT&T's infrastructure. The most reliable path forward for your users is to put a custom domain in front of your services, since ISP-level filters target *.up.railway.app specifically and would not affect a custom domain pointing at Railway.