Hello mkdobson3,
Please accept my sincere apologies for I find your issue
a bit vague.
However, let me just give you a brief description on how
to differentiate a good tracert from a bad tracert.
A good traceroute:
As the packets travel from point A to point B, each hop
appear on its own line. Traceroute should display the address and name of each
server/router/node along the way and the amount of time (measured in
milliseconds) the packets take to travel on each hop
between point A to point B.
A bad traceroute:
Each line of the traceroute displays three (3) pings and
the server/router/node of that hop. Asterisks (* * *) found in the hops
indicate a timeout. If you see a line with just asterisks on it, that means
that the hop between server/router/node took longer than 200ms.
Several lines of timeouts mean the packets are being held
up, clogged or lost somewhere along the way. An average good response is around
1ms to 80ms. Any response above 300ms could potentially affect traffic through
that hop and would be considered a bad response. If consistent timeouts or bad
responses are found within the AT&T network hops, this an AT&T issue.
If consistent timeouts or bad responses are found outside of the AT&T
network hops, this is not an AT&T issue.
NOTE: Some points on the traceroute will show a timeout
because administrators have restricted pings. This may not necessarily indicate
a fail point. If the destination host is not reachable at all, then failures
will typically be sporadic: * 200ms * (2 timeouts and 1 successful).
Should you need further help regarding your post, please
feel free to reply on this thread.
For additional assistance, you may chat us by accessing
this link:
https://pattta.att.motive.com/netagent/questionnaire_c2c_dsl_se.aspx
Remember to always mark items that you find useful as "Accepted Solutions”, you can even mark multiple
posts in a single thread. This will help other users find this information too!!
ackets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0ms
