@logonaut.eth

My VPN provider no longer surfaces its Salt Lake City server in the app UI as of May 1 — days before Utah’s new VPN liability law takes effect. But: 👉 Hostnames still resolve in DNS 👉 Traceroute still reaches SLC (Zayo backbone) 👉 Connection attempts to VPN ports just hang (no response) So this isn’t a clean removal. The endpoint still appears in DNS and routing, but isn’t responding to connection attempts from this vantage point — effectively taken out of service. That kind of partial withdrawal — visible in infrastructure, absent in the product — is exactly what you’d expect if a provider were reducing exposure without fully tearing down a location. Utah’s law goes into effect May 6, per EFF: ❝Next week, on May 6, 2026, Utah will become, to EFF’s knowledge, the first state in the nation to target the use of VPNs to avoid legally mandated age-verification gates. While advocates in states like Wisconsin successfully forced the removal of similar provisions due to constitutional and technical concerns, Utah is proceeding with a mandate that threatens to significantly undermine digital privacy rights.❞ https://www.eff.org/deeplinks/2026/04/utahs-new-law-regulating-vpns-goes-effect-next-week No direct confirmation these are related — but the timing and behavior line up in a way that’s hard to dismiss.

1 reply

0 recast

2 reactions