Hello!
To use the forum, login or register above.
(If you are already logged in above, please click here)
Site's non-accessibility from Sprint
Lawrence, my wireless carrier is Sprint in the US. I noticed that I can't access BrickOwl.com from my phone (and thus also not via hotspot through the phone). A traceroute shows that Sprint seems to be purposefully dropping packet routes early in the hops, like barely 2 or 3. I'm guessing that the IP block your host uses for your server(s) have at one point been on a blacklist that Sprint is using. You may want to talk to your host and Sprint - it may be a small slice of your audience that's affected but a lot of people now use their phones for Internet browsing and millions of Sprint customers are in the US.
Powered by Vanilla
Comments
Did anyone ask Sprint about it?
Thanks
I made sure to give the 2nd tech a hard time about the first tech who didn't call me back, as I'm not above complaining if someone doesn't follow through on support & also made sure to tell him that other Sprint users I've spoken to have been having the same issue since July of last year. Kept emphasizing that it's a routing issue on their end (not a device, issue, not a browser issue, not a 4G or 3G issue) so that they didn't come back to me later shrugging their shoulders - one of their route hops is clearly dropping connections to a block of IPs, they just need to find that hop and un-block them.
I deal with tech issues all day long, this should be a brain-dead one for them to find & resolve -- but it's a wireless carrier in the US, so we're mostly dealing with 90% drones who couldn't ping their way out of a paper bag.
Sprint is using this fact to claim it must be an issue with the site, otherwise I would not be able to load any pages. Does that tell anyone anything?
Another possibility - when I do an IP check on my phone on various sites, it returns the IPV6 address instead of IPV4 - which could mean that there is a router somewhere in the path between Sprint & you that is barfing on the IPV6. That doesn't exactly help you to know that but if someone else calls Sprint about this, make sure they are aware a lot of people are having the issue and it's very likely THEM (when I do a trace hop test, my connections get dropped at barely TWO hops). 2 hops is not normal, if it were on Lawrence's side it would not drop the hops until the very end (usually 6-15 hops depending on network path).
Bluedragon, can you check to see if you have the same behavior? Specifically, go to:
https://www.whatismyip.com/
I am going to confidently predict that if you use Chrome or Firefox you will get back an IPV6 address (a long string of alphanumeric characters with semi-colons) but if you use Opera Mini you will get a normal IP address (4 dotted numbers).
http://ipv6test.google.com
or this:
http://test-ipv6.comcast.net
I get different responses when using Opera vs the others. When using the others I get information that tells me I'm using an IPV6 address & that it's tunneled. When using Opera it says I'm not using IPV6 but that I should be OK with web sites that add IPV6 support.
Make sure you're using your 4G when testing on your phone & not your WiFi.
chrome/safari/opera- all show you don't have IPv6 but that should be OK...
I have decided what do do now that everyone is aware of the issue: I will give Sprint 1 month, then switch if the problem persists.
I updated my Android last night to Nougat and just tried hotspot from work and that finally works (before only just the phone was working for me). So now, at least in my testing, it's working both directly on the phone and via hotspot acting as a hotspot. I don't know if it's because Sprint actually fixed something or if the updated Android somehow played a role.
The negative is that my mail application I use for work Exchange email doesn't succeed in sending email.