Network Issue

turbotoast

turbotoast

Registered User
Joined
Jan 5, 2014
Messages
244
Age
38
So I thought my computer was the problem, but every device on my network refuses to load any YouTube video that has an ad, and I also can't get on a single Rust server. I can't think of a single thing that would cause this since obviously either something is wrong with the modem or the ISP. I already reset the modem and it didn't change anything (didn't really expect it to). My speed is fine and will buffer any video without an ad. I also tested my ping on youtube and it's fine. This is stressing me out. Mostly because I know it's something the ISP will probably have to fix. Any suggestions are welcome.
 
Last edited:
traceroute (from your pc on the command line not a web tool) to the rust ip's then trace to something you can connect to see what backbones you go through for each.
 
Depending on who your ISP is I'm aware of lots of chatter around Youtube peering/quality across N. America, you could also tracert to youtube.com. Do you use any Ad blocking in your browser, could try toggling it to see if that has an effect to?
 
Traceroute results from the TBG Rust server (Can't connect) EDIT (Can now connect with exact same results)
tracert 162.221.192.120

Tracing route to 162.221.192.120 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 7 ms 7 ms 99-194-16-1.dyn.centurytel.net [99.194.16.1]
3 9 ms 8 ms 9 ms 66-79-78-29.stat.mebtel.net [66.79.78.29]
4 17 ms 17 ms 17 ms 208.110.241.193
5 20 ms 17 ms 17 ms bb-rcmtncxa-jx9-01-ae0.core.centurytel.net [208.
110.248.65]
6 27 ms 27 ms 27 ms bb-atlngamv-jx9-01-ae3.0.core.centurytel.net [20
8.110.248.78]
7 28 ms 28 ms 32 ms 99.xe-0-1-0.cr1.atl1.us.nlayer.net [198.32.132.6
8]
8 28 ms 27 ms 27 ms ae0-60g.cr1.atl1.us.nlayer.net [69.31.135.129]
9 42 ms 42 ms 42 ms xe-0-2-1.cr2.ord1.us.nlayer.net [69.22.142.45]
10 41 ms 41 ms 42 ms ae3-60g.cr1.ord1.us.nlayer.net [69.31.111.153]
11 42 ms 42 ms 42 ms as32181.ae1-108.cr1.ord1.us.nlayer.net [69.31.11
0.106]
12 43 ms 43 ms 43 ms po-12.csr2.Chi3.Servernap.net [66.252.0.69]
13 43 ms 43 ms 43 ms te-9-4.ddr4.Chi3.Servernap.net [66.252.0.163]
14 * * * Request timed out.
15 44 ms 43 ms 43 ms 162.221.192.120

Trace complete.

Traceroute result from google.com (Can connect)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Tracing route to google.com [74.125.228.38]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 7 ms 7 ms 99-194-16-1.dyn.centurytel.net [99.194.16.1]
3 8 ms 8 ms 8 ms 66-79-78-29.stat.mebtel.net [66.79.78.29]
4 17 ms 17 ms 17 ms 208.110.241.193
5 25 ms 55 ms 24 ms bb-asbnvacy-jx9-02-ae3.0.core.centurytel.net [20
8.110.248.170]
6 24 ms 26 ms 24 ms bb-asbnvacy-jx9-01-ae0.0.core.centurytel.net [20
8.110.248.117]
7 25 ms 25 ms 43 ms 72.14.219.254
8 26 ms 24 ms 26 ms 216.239.46.250
9 25 ms 25 ms 25 ms 72.14.238.175
10 25 ms 25 ms 24 ms iad23s06-in-f6.1e100.net [74.125.228.38]

Trace complete.
 
Last edited:
Avery78 said:
Depending on who your ISP is I'm aware of lots of chatter around Youtube peering/quality across N. America, you could also tracert to youtube.com. Do you use any Ad blocking in your browser, could try toggling it to see if that has an effect to?
Click to expand...

Tried toggling ad blocker and it made no difference. I have tried on every platform in my house (Windows 7, Windows 8, iOS, Android, OSX) and none of them can load the videos while on the network.

I can also now connect to Rust so that may have just been an unrelated issue.
 
Here is mine to Rust from Alberta, Canada:
C:\>tracert 162.221.192.120

Tracing route to 162.221.192.120 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 10 ms 15 ms rc3no-tge0-11-0-32-1.cg.shawcable.net [64.59.132.69]
4 33 ms 31 ms 35 ms rc3sc-tge0-0-0-14.wp.shawcable.net [66.163.64.138]
5 48 ms 45 ms 50 ms rc4ec-hge0-9-0-0.il.shawcable.net [66.163.77.206]
6 52 ms 47 ms 51 ms pr1.chi2.servernap.net [206.223.119.108]
7 44 ms 46 ms 45 ms po-12.csr2.Chi3.Servernap.net [66.252.0.69]
8 49 ms 47 ms 46 ms te-9-4.ddr4.Chi3.Servernap.net [66.252.0.163]
9 * * * Request timed out.
10 45 ms 54 ms 54 ms 162.221.192.120

Trace complete.
 
It's randomly started working again. I haven't changed a single thing lol. Thanks for the quick replies trying to help though. Much appreciated.
 
The reason I wanted a trace route is just to see what its connecting through. Like I have Comcast and if I have trouble with STO and something else but other things are fine maybe cogents backbone is screwing me but some server are going through at&t and was curious as to if YouTube was going through the same backbone as rust. But it would be difficult to get the IP for the content since YouTube is a CDN type setup.

Sent from my Nexus 5 using Tapatalk
 
RainMotorsports said:
The reason I wanted a trace route is just to see what its connecting through. Like I have Comcast and if I have trouble with STO and something else but other things are fine maybe cogents backbone is screwing me but some server are going through at&t and was curious as to if YouTube was going through the same backbone as rust. But it would be difficult to get the IP for the content since YouTube is a CDN type setup.

Sent from my Nexus 5 using Tapatalk
Click to expand...


bOmhVhl.gif
 
You must log in or register to reply here.
Back
Top