Assumptions are the mother of all fuck ups-- This is a problem on your side the VU has not been timing out at all I attach from many different sourcesJust thought id report this, it has been happening all the time for about the past week. this is the screen i get
View attachment 9729
View attachment 9729
Simply use Ping and figure out the route times.Assumptions are the mother of all fuck ups-- This is a problem on your side the VU has not been timing out at all I attach from many different sources
I would check your web browser if thats not the problem call your ISP its on your side
yes I was going to say use traceroute and see if there are any bottle necks at any of the access points but I made the assumption woopsSimply use Ping and figure out the route times.
How helpfull you are I was too lazy to get a web based traceroute link I have been bad againYeah, if you did a traceroute to vapingunderground.com from your computer you're having trouble with, it would identify if the issue exists on your end or the site's end.
http://www.mediacollege.com/internet/troubleshooter/traceroute.html
Since the site is hidden completely behind CloudFlare, we won't be able to tell for sure if it's just an issue with the CloudFlare node you get redirected to (which is very much a possibility, as we all get sent through different nodes dependent on our geographic location and thus might not experience the same issue), or if it's a problem with your ISP, or if the issue actually lies with the VU hosting beyond the CloudFlare wall of fire. Regardless, there's not much you or anyone else can do about it I believe, it would take some investigation from the backends of each service to identify the true culprit.Thanks for the help. Tried what was suggested got results but don't understand them. As follows
Tracing route to vapingunderground.com [162.159.249.230]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
4 11 ms 9 ms 11 ms rc2nr-hge0-19-0-0.wp.shawcable.net [66.163.73.19
7]
5 32 ms 34 ms 43 ms 66.163.76.22
6 34 ms 34 ms 37 ms 66.163.66.58
7 32 ms 33 ms 31 ms gw-cloudflare.torontointernetxchange.net [206.10
8.34.208]
8 36 ms 31 ms 31 ms 162.159.249.230
Trace complete.
162.159.248.230 is from United States(US) in region North America
TraceRoute from Network-Tools.com to 162.159.248.230 [vapingunderground.com]
Hop(ms)(ms)(ms) IP AddressHost name
1 0 0 0 206.123.64.46 -
2 1 0 1 173.219.246.92 173-219-246-92-link.sta.suddenlink.net
3 252 282 238 173.219.225.54 173-219-225-54-link.sta.suddenlink.net
4 0 0 0 206.223.118.145 xe-0-0-3.edge01.dfw01.as13335.net
5 0 0 0 162.159.248.230 -
Trace complete
Ugh. Having really awful flashbacks to BGP issues in the NOC. The network engineers who keep us all connected don't get enough credit.Or, a peering issue..Shaw is rather crappy... ;-)
Yeah, that would help troubleshoot for sure. Same with trace routing from online services like CaFF just did.If I setup a vpn that said I was in say california wouln't that direct me to a different node ? Maybe that would help to troubleshoot.
Yeah, that would help troubleshoot for sure. Same with trace routing from online services like CaFF just did.
No, in a trace route it's okay if intermediate steps in a trace time out, some of these routers we hit on the way to our endpoint don't respond to ping packets but still pass on our traffic, and since the ping doesn't respond it gets registered as a timeout even though it continues on just fine. It's similar to how when you measure packet loss between two points, all the packet loss in between the beginning and the end is irrelevant as long as the last hop has no packet loss. IT can be weird like that.1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out. Thats the issue, right after your local address of 192.168.0.1, it times out
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
Are you running a local firewall or firewall on your cable router?
"Just have to disable for peer2peer". That might be the issue with your local isp possibly blocking p2p connections.Just setup openvpn on us1 located in washington. Connects perfect. Wow you realize how well this site really works till it doesn't.
Must be something wrong with the node to VU server I was defaulting to. This will work for me. Just have to diasble for peer2peer
"Just have to disable for peer2peer". That might be the issue with your local isp possibly blocking p2p connections.