Slow upload speed and T Mobile home Internet

make sure to test different locations.  They have some localized capacity issues… if you are only testing locally, you may not be getting an accurate picture of how things pan out for how you are actually using it.

for example, I am in the Carolinas, and while the localized testing around the Charlotte area often looks reasonable, it is prone to bouts of bad congestion.  BUT… my usage rarely actually is hitting Charlotte area endpoints, so those results are mostly irrelevant for my needs.

One of my main uses is for games…. games that are NOT hosted in the Carolinas.  Otherwise, it is a lot of streaming--and those CDN's are not in the Charlotte area either.

When I test to the areas where most of those games are hosted, I tend to see quite a contrast---most often much better throughput to those locations further out.  That is right… I can actually get better results testing to Seattle, Montreal, NY, Dallas, Even areas around Southern California than I do to sites within my more immediate region of NC/SC.

If you see a HUGE shift when comparing results like that, it can be important info to pass on to tech support somehow… as there may be a backhaul issue, or other peering issues that need to be addressed at a higher tier, possibly even with a third party partner.

Just as an example, here are some results from some tests done close together in my history:

Notice how the one all the way up in Montreal faired better than the one that was just 50 miles away that Speedtest defaults to.