We're experiencing problems contacting our email server (dreamhost.com). We contacted the webhost, and they asked us to do a trace route. Turns out something is happening at twtelecom.net, and asked us to contact our ISP. We're currently running Comcast Business 50. Can anyone help?
Thanks in advance, trace route below:
Tracing route to dynastygallery.com [184.108.40.206]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms uc320w [192.168.10.1]
2 1 ms 1 ms 2 ms 10.1.10.1
3 10 ms 17 ms 9 ms 220.127.116.11
4 8 ms 8 ms 8 ms te-7-1-ur02.sffolsom.ca.sfba.comcast.net [68.85.
5 10 ms 10 ms 11 ms te-1-14-0-7-ar01.oakland.ca.sfba.comcast.net [68
6 11 ms 15 ms 15 ms be-90-ar01.sfsutro.ca.sfba.comcast.net [68.85.15
7 13 ms 15 ms 18 ms he-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68
8 17 ms 22 ms 17 ms pos-0-2-0-0-pe01.11greatoaks.ca.ibone.comcast.ne
9 16 ms 18 ms 20 ms as4323-pe01.11greatoaks.ca.ibone.comcast.net [75
10 85 ms 78 ms 82 ms atl1-ar3-ge-0-1-0-0.us.twtelecom.net [66.192.243
11 78 ms 87 ms 77 ms 66-193-162-94.static.twtelecom.net [18.104.22.168
12 * * * Request timed out.
13 * * * Request timed out.
14 82 ms 78 ms 80 ms 22.214.171.124
Solved! Go to Solution.
Traceroute results are always interesting. Traceroute uses tailored pings with increasing hop count for each query. Intermidiate responses come from routers along the path where the hop count expires. The last response comes from the target system. The significant conclusions from the results you posted include:
1. 126.96.36.199 is reachable from your system with a Round Trip Time (RTT) of about 80 milliseconds. This is not fantastically small or unreasonably large. It is certainly not large enough to adversly affect connections to a mail or web server.
2. The RTT increases as the path crosses from Comcast to Twtelecom.net. This indicates that some part of twtelecom.net is somewhat slower than Comcast. Again, the RTT numbers are not large enough to be considered a problem.
The "* * * Request timed out." messages indicate that the router queried either was too busy to handle ICMP Echo requests or was programmed to ignore them. The significant number is the end-to-end RTT.
So, something is indeed happening at twtelecom.net:
1. Your packets are reaching and and answered by 188.8.131.52.
2. The part of twtelecom.net you traverse is apparently not as fast as Comcast but still appears commercially viable.
Hey great info!! Thanks for taking the time to explain.
So I guess the end user has no say in how fast a request needs to be routed, right? Does this mean that even if I subscribe to 150mbps, I'll still hit the same RTT?
lawrencelane asked, "So I guess the end user has no say in how fast a request needs to be routed, right? Does this mean that even if I subscribe to 150mbps, I'll still hit the same RTT?"
You are paying Comcast, not twtelecom.net. Most of the RTT is in twtelecom.net.
So, yes. within some small limits.