Hey, ky0n! This is a known issue caused by IPv6 connections. In order to workaround the issue, the connection needs to allow IPv4 data. We’ve provided some workarounds here:
Our team is working on resolving these issues individually, but each mobile network needs to be done individually and there’s no way to mass resolve these situations. We are aware and working on it, but the workarounds should help in the mean time.