Most large companies simply have no way to escalate a real bug report.
I'd recommend just calling them ;)
When I tried to activate my new account online, I got to a form for payment that was demanding I fill out fields that didn't exist on the page. This is insane from a major carrier. I then had to call in to activate, and after having me on hold for half an hour, they made me verify with one of those things where they want to know a nearby intersection from where you lived six years ago - which of course I couldn't answer. I hung up on that guy, called again, and they let me verify my card through my bank. And now that I had an account, I tried checking out their account management site, and it was so broken as to be nigh unusable. And then I found out like the OP that a noticeable amount of sites are broken or just plain unreachable on their network.
I now understand why they can offer such a great-sounding plan for $30/month.
I came from AT&T and can't compare T-Mo to much else. Do any of the telcos have what you would consider to be fantastic support?
But when Tmobile forces me to call, which I was trying to avoid, because their web engineering is so completely terrible, and then I have to wait on hold for half an hour, and then the cust service guy acts like I'm a criminal when I'm going through all this pain to give them money - a saner person would've given up.
I realize that's probably just local circumstances and I know Tmobile's network is a fair bit smaller, but I can't personally complain about that aspect.
Are people really expecting customer-support-representatives that normally deal with "my facebook doesn't post on my android-iphone" problems to decipher "It's such is routing of web cache that your DNS has.", "I've tried to use the phone as hotspot and connect via pc and iPad and didn't works."
(1) I think the problem was not unambiguously described.
I think that the user "rbianco" tried to convey that ICMP/ping and TCP connections to ports other than 80 worked quite well, only on port 80 was a connection redirected to a misbehaving/broken (not-so-)transparent proxy.
(2) The methods used to determine these facts, and to reproduce the observed problems were not described (or rather: information spread over several messages).
Some other user gave hints how to reproduce the behaviour with different invokations of curl, this, and maybe even a prepared test-file on the webserver for the support-staff to play with, would have been most useful.
http://www.wordsforreading.com/blog/2012/07/19/let-bogons-be...
Doing a little research on some internal tooling, I found an IP close to www.viclone.com (5.135.96.195), namely gemclotures.com (5.135.96.102) that is also unreachable over t-mobile's 4g connection (tried it myself).
They're both hosted by OVH.
We contacted OVH, we have the private cloud there, they checked everything with our team. They couldn't find anything. Then I asked to other T-Mobile users and saw that the problem only occurs under T-Mobile networks... We were very very clear in the post, but the few responses of solutions were like "did you read my problem?"
