Page 1 of 1

ping probs.

Posted: November 15th, 2016, 6:56 pm
by zanshin1
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Brian>tracert 8.12.64.130

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 8 ms 7 ms 7 ms 96.120.40.245
3 9 ms 7 ms 7 ms Te7-2-ur02.shelby.mi.michigan.comcast.net [69.13
9.240.17]
4 10 ms 8 ms 13 ms te-0-8-0-23-ar02.pontiac.mi.michigan.comcast.net
[68.87.190.229]
5 14 ms 18 ms 16 ms be-33668-cr02.350ecermak.il.ibone.comcast.net [6
8.86.90.45]
6 14 ms 15 ms 14 ms hu-0-12-0-6-pe01.350ecermak.il.ibone.comcast.net
[68.86.89.242]
7 100 ms 118 ms 109 ms ae12.chi11.ip4.gtt.net [199.229.229.249]
8 144 ms 149 ms 137 ms xe-2-0-0.dal20.ip4.gtt.net [141.136.111.58]
9 163 ms 165 ms 161 ms ip4.gtt.net [173.205.43.82]
10 143 ms 143 ms 129 ms 8.12.64.130

Trace complete.

C:\Documents and Settings\Brian>
C:\Documents and Settings\Brian>


Refresh my memory......is it comcast thats the problem or GTT.net?

Ill be gone fer a week....address then.

TY

Re: ping probs.

Posted: November 16th, 2016, 5:44 pm
by Trench
Being right at the point where the traffic left Comcast and entered GTT, technically the literal "fault" could actually be either one of them. (Comcast's edge hardware might be slow is getting the packets out or back in; or maybe it's GTT's end being slow to accept them.)

But to me that still means its in Comcast's court and worth time trying to call them, since they're your ISP and control their side of this "edge" connection to GTT. Even if Comcast thought it was GTT's problem, Comcast is the one who is connected to them (not you), and Comcast technically might have the ability to use a different peer if they confirm GTT is having issues.

Since you're gone for a week, the first first thing will of course be to see if the issue even still exists.

-Trench