Bill in MN
@embarqhsd.net
| DSL problems in MN 55369?
I've been experiencing DSL problems since yesterday. I'm a static IP customer.
Customer service on the phone told me that everything is fine.
I'm getting awful latency, response times and time outs. When I ping almost any IP address I get 200+ms repsonse times and occasional time outs. Every once in a while things get better and I get 60ms response times, but then it goes back to being slow.
Help??
Pinging www.l.google.com [64.233.167.147] with 32 bytes of da
Reply from 64.233.167.147: bytes=32 time=187ms TTL=248
Reply from 64.233.167.147: bytes=32 time=187ms TTL=248
Reply from 64.233.167.147: bytes=32 time=188ms TTL=248
Reply from 64.233.167.147: bytes=32 time=184ms TTL=248
Reply from 64.233.167.147: bytes=32 time=187ms TTL=248
Reply from 64.233.167.147: bytes=32 time=186ms TTL=248
Reply from 64.233.167.147: bytes=32 time=175ms TTL=248
Reply from 64.233.167.147: bytes=32 time=180ms TTL=248
Reply from 64.233.167.147: bytes=32 time=175ms TTL=248
Request timed out.
Reply from 64.233.167.147: bytes=32 time=185ms TTL=248
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.167.147: bytes=32 time=181ms TTL=248
Reply from 64.233.167.147: bytes=32 time=186ms TTL=248
Reply from 64.233.167.147: bytes=32 time=172ms TTL=248
Reply from 64.233.167.147: bytes=32 time=189ms TTL=248
Reply from 64.233.167.147: bytes=32 time=177ms TTL=248
Reply from 64.233.167.147: bytes=32 time=186ms TTL=248
Request timed out.
Reply from 64.233.167.147: bytes=32 time=176ms TTL=248
Reply from 64.233.167.147: bytes=32 time=181ms TTL=248
Reply from 64.233.167.147: bytes=32 time=188ms TTL=248
Reply from 64.233.167.147: bytes=32 time=186ms TTL=248
Reply from 64.233.167.147: bytes=32 time=189ms TTL=248
Reply from 64.233.167.147: bytes=32 time=189ms TTL=248
Reply from 64.233.167.147: bytes=32 time=186ms TTL=248
Reply from 64.233.167.147: bytes=32 time=205ms TTL=248
Request timed out.
Reply from 64.233.167.147: bytes=32 time=174ms TTL=248
Reply from 64.233.167.147: bytes=32 time=188ms TTL=248
Reply from 64.233.167.147: bytes=32 time=172ms TTL=248
Ping statistics for 64.233.167.147:
Packets: Sent = 33, Received = 27, Lost = 6 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 205ms, Average = 183ms
Tracing route to www.l.google.com [64.233.167.104]
over a maximum of 30 hops:
1 178 ms 173 ms 174 ms mn-66-247-107-1.sta.embarqhsd.net [66.247.107.1]
2 * 163 ms 171 ms mn-69-34-66-1.sta.embarqhsd.net [69.34.66.1]
3 169 ms 171 ms 174 ms 64.214.140.193
4 184 ms * 180 ms te9-2-10G.ar2.CHI2.gblx.net [67.17.109.114]
5 * 202 ms 189 ms 74.125.48.133
6 172 ms 186 ms 187 ms 216.239.48.154
7 186 ms 183 ms 190 ms 72.14.238.89
8 183 ms 182 ms 182 ms 72.14.232.70
9 185 ms 187 ms * py-in-f104.google.com [64.233.167.104]
10 182 ms 177 ms 184 ms py-in-f104.google.com [64.233.167.104]
Trace complete. |
|
Bill in MN
@embarqhsd.net
| Things are better again today. Not sure if the Embarq network is congested or what. I hate talking to their customer service reps. One guy I spoke to yesterday told me that it can't be a Embarq problem since my line tested OK. Apparently he has never heard of upstream providers or DNS servers. |
|
embarq_cesar
join:2007-12-19
Carlisle, PA
| reply to Bill in MN
Hello Bill
This is Cesar from Embarq Customer Support.
Sorry for not getting to your post sooner, but I am happy to see that your connection is back to normal.
If you experience any further problems with your connection or any of our services please let me know.
Thanks
Cesar L
Embarq Social Media & Networking Customer Support
smnp.cesar.l@embarq.com
For additional support and live chat please visit www.myembarq.com/contact_us.php
Voice | Data | Internet | Wireless | Entertainment |
|
