Contributor
•
2 Messages
bad hop belonging to ATT.
I have called numerous times and can't seem to get anyone to fix this issue.
I will cancel my account in 3 days if this router is still acting up.
you can reach me @ ***
fldfl1401me3.ip.att.net (12.123.153.113)
is a bad hop. fix it as it is slowing down my connection.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\j>ping yahoo.com
Pinging yahoo.com [98.138.253.109] with 32 bytes of data:
Reply from 98.138.253.109: bytes=32 time=88ms TTL=45
Reply from 98.138.253.109: bytes=32 time=87ms TTL=45
Reply from 98.138.253.109: bytes=32 time=90ms TTL=45
Reply from 98.138.253.109: bytes=32 time=90ms TTL=45
Ping statistics for 98.138.253.109:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 90ms, Average = 88ms
D:\Documents and Settings\j>tracert google.com
Tracing route to google.com [173.194.115.39]
over a maximum of 30 hops:
1 7 ms 3 ms 3 ms homeportal [192.168.1.254]
2 28 ms 31 ms 26 ms
107-214-156-3.lightspeed.miamfl.sbcglobal.net [1
07.214.156.3]
3 29 ms 27 ms 26 ms 99.167.141.158
4 30 ms 29 ms 27 ms 12.83.70.41
5 30 ms 245 ms 29 ms fldfl401me3.ip.att.net [12.123.153.113]
6 * * * Request timed out.
7 29 ms 30 ms 30 ms 209.85.253.120
8 59 ms 57 ms 58 ms 209.85.142.47
9 59 ms 58 ms 57 ms 64.233.175.149
10 57 ms 57 ms 59 ms 209.85.254.125
11 57 ms 57 ms 56 ms dfw06s40-in-f7.1e100.net
[173.194.115.39]
Trace complete.
D:\Documents and Settings\j>tracert 12.123.153.113
Tracing route to fldfl401me3.ip.att.net [12.123.153.113]
over a maximum of 30 hops:
1 5 ms 6 ms 5 ms homeportal [192.168.1.254]
2 27 ms 31 ms 26 ms
107-214-156-3.lightspeed.miamfl.sbcglobal.net [1
07.214.156.3]
3 28 ms 26 ms 26 ms 99.167.141.158
4 12.83.70.41 reports: Destination net unreachable.
Trace complete.
D:\Documents and Settings\j>tracert 12.123.153.113
Tracing route to fldfl401me3.ip.att.net [12.123.153.113]
over a maximum of 30 hops:
1 10 ms 4 ms 3 ms homeportal [192.168.1.254]
2 25 ms 34 ms 26 ms
107-214-156-3.lightspeed.miamfl.sbcglobal.net [1
07.214.156.3]
3 28 ms 26 ms 27 ms 99.167.141.158
4 12.83.70.41 reports: Destination net unreachable.
Trace complete.
D:\Documents and Settings\j>tracert google.com
Tracing route to google.com [173.194.115.39]
over a maximum of 30 hops:
1 4 ms 4 ms 3 ms homeportal [192.168.1.254]
2 26 ms 26 ms 27 ms
107-214-156-3.lightspeed.miamfl.sbcglobal.net [1
07.214.156.3]
3 28 ms 26 ms 26 ms 99.167.141.158
4 29 ms 35 ms 27 ms 12.83.70.41
5 30 ms 27 ms 27 ms fldfl401me3.ip.att.net [12.123.153.113]
6 * * * Request timed out.
7 31 ms 29 ms 28 ms 209.85.253.120
8 59 ms 57 ms 58 ms 209.85.142.47
9 59 ms 57 ms 57 ms 64.233.175.149
10 57 ms 58 ms 57 ms 209.85.254.125
11 58 ms 57 ms 57 ms dfw06s40-in-f7.1e100.net
[173.194.115.39]
Trace complete.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
D:\Documents and Settings\j>ping google.com
Pinging google.com [216.58.217.206] with 32 bytes of data:
Reply from 216.58.217.206: bytes=32 time=89ms TTL=49
Reply from 216.58.217.206: bytes=32 time=90ms TTL=49
Reply from 216.58.217.206: bytes=32 time=90ms TTL=49
Reply from 216.58.217.206: bytes=32 time=91ms TTL=49
Ping statistics for 216.58.217.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 91ms, Average = 90ms
D:\Documents and Settings\j>tracert google.com
Tracing route to google.com [216.58.217.206]
over a maximum of 30 hops:
1 4 ms 4 ms 3 ms homeportal [192.168.1.254]
2 26 ms 27 ms 25 ms
107-214-156-3.lightspeed.miamfl.sbcglobal.net [1
07.214.156.3]
3 28 ms 25 ms 26 ms 99.167.141.158
4 27 ms 27 ms 28 ms 12.83.70.41
5 27 ms 27 ms 26 ms fldfl401me3.ip.att.net [12.123.153.113]
6 * * * Request timed out.
7 30 ms 29 ms 25 ms 209.85.253.116
8 58 ms 57 ms 57 ms 209.85.142.45
9 91 ms 104 ms 90 ms 64.233.174.142
10 92 ms 89 ms 89 ms 209.85.248.124
11 88 ms 88 ms 89 ms 216.239.51.55
12 90 ms 89 ms 91 ms lax17s05-in-f206.1e100.net
[216.58.217.206]
[Edited for privacy-please do not post personal or unique information such as but not limited to full names, employee ID numbers, email addresses, phone numbers, account numbers, etc.]
Darknessrise
Professor
•
2.4K Messages
9 years ago
@saabnut
There aren't any obvious issues with the tracerts you posted(unless I accidentally glanced over it) except for one thing.
Sometimes certain devices don't prioritize ping requests as high priority and will often drop them/depriortize in the case of tracerts.
I do notice that your latency to your gateway is a little bit high compared to what it should be. Are you using wireless? Have you tried using a wired connection?
I did notice your "destination net unreachable" messages. I don't commonly see that in a tracert. I believe that may just be another result of them not allowing direct pings to the devices across their network.
0
0
ms_unicorn
Former Employee
•
4.9K Messages
9 years ago
Hello, @saabnut!
Thanks for posting. If you're still having this issue, please click here to send us a private message with your contact information, the best time to reach you, and a brief summary. We'd appreciate the opportunity to look into this further!
You can expect a reply within two business days, so keep an eye on the little blue envelope icon in the top right corner of your screen. In the meantime, feel free to messae me with any other questions or concerns.
-Mariana
0
0
saabnut
Contributor
•
2 Messages
9 years ago
I don't understand why you say my internal network latency is high with the hop to the router averaging less than 5 seconds. I think that is OK for wireless WPA. I have the same issues wired.
I truly believed that the copper is bad in my neighborhood. it is approaching 60 years old. However technicians have been here numerous times, and have not resolved the issue.
Additionally I have issues with streaming netflix. ( tracert points to an amazon server)
I went from 6mb dsl to 15mb uverse.
Other than an improved speedtest there does not seem to be any improvement and the internet connection still hangs at times. My Tmobile phone is faster.
I believe I have an issue with the router cited.Techicians have indicated that it does not seem right.
0
0