0

I am currently testing an API as a backend for that I built, with Android and iPhone app as a front-end.

While testing through 5g (Ultra Capacity or not), the connection is extremely slow, and the data is not loading through the App. I have tried at many places at various times of the day, with the same result over again. I also don't have reached my data limit, and other websites and apps work perfectly fine.

However, when I am connected through Wi-Fi (even coffee place's wifi) the App works perfectly, and the data is loading instantly.

I suspect some hidden QoS rules from T-mobile. The API is set on port 443, but I am reaching the API through its IP directly.

Can someone help me figuring what would be the rules to follow to avoid being deprioritized?

Improve this question
4
  • I suspect a problem with your gear. However, software development and protocols above the transport layer are explicitly off-topic here, see the help center. You might want to try on Stack Overflow.
    – Zac67 ♦
    Commented Sep 5 at 8:53
  • 1
    Keep in mind TMo is a native IPv6 network. Any IPv4 connectivity is through 464XLAT, which can make a mess of some things. And cellular networks are usually "one way" - you cannot reach out to the device, no matter what it thinks its address is.
    – Ricky
    Commented Sep 6 at 0:48
  • Thanks @Zac67 I was not sure if this was more of a telecommunications/network question than development. I will post this question there
    – toshiro92
    Commented Sep 6 at 0:59
  • @Ricky Interesting, that is good to know. At the moment, the App is initiating the connection to the API, maybe this has to do with using an IPv4 address instead. I will try to use an ipv6 before I post the question again through Stackoverflow
    – toshiro92
    Commented Sep 6 at 1:02

0

Reset to default

Browse other questions tagged or ask your own question.