<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: DSL problems in MN 55369? in Embarq</title>
<link>http://www.dslreports.com/forum/r20406474</link>
<description></description>
<language>en</language>
<pubDate>Fri, 21 Nov 2008 11:05:25 EDT</pubDate>
<lastBuildDate>Fri, 21 Nov 2008 11:05:25 EDT</lastBuildDate>

<item>
<title>Re: DSL problems in MN 55369?</title>
<link>http://www.dslreports.com/forum/remark,20406474</link>
<description><![CDATA[<A HREF="/useremail/u/1513000"><b>embarq_cesar</b></A> : Hello Bill<br>This is Cesar from Embarq Customer Support.<br>Sorry for not getting to your post sooner, but I am happy to see that your connection is back to normal.<br>If you experience any further problems with your connection or any of our services please let me know.<br>Thanks<br>Cesar L<br>Embarq Social Media & Networking Customer Support<br>smnp.cesar.l@embarq.com<br>For additional support and live chat please visit www.myembarq.com/contact_us.php <br>Voice | Data | Internet | Wireless | Entertainment]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20406474</guid>
<pubDate>Tue, 29 Apr 2008 16:11:38 EDT</pubDate>
</item>

<item>
<title>Re: DSL problems in MN 55369?</title>
<link>http://www.dslreports.com/forum/remark,20399059</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : 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.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20399059</guid>
<pubDate>Mon, 28 Apr 2008 11:00:23 EDT</pubDate>
</item>

<item>
<title>DSL problems in MN 55369?</title>
<link>http://www.dslreports.com/forum/remark,20394928</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I've been experiencing DSL problems since yesterday.  I'm a static IP customer.  <br><br>Customer service on the phone told me that everything is fine. <br><br>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.<br><br>Help??<br><br>Pinging www.l.google.com [64.233.167.147] with 32 bytes of da<br><br>Reply from 64.233.167.147: bytes=32 time=187ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=187ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=188ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=184ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=187ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=186ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=175ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=180ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=175ms TTL=248<br>Request timed out.<br>Reply from 64.233.167.147: bytes=32 time=185ms TTL=248<br>Request timed out.<br>Request timed out.<br>Request timed out.<br>Reply from 64.233.167.147: bytes=32 time=181ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=186ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=172ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=189ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=177ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=186ms TTL=248<br>Request timed out.<br>Reply from 64.233.167.147: bytes=32 time=176ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=181ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=188ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=186ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=189ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=189ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=186ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=205ms TTL=248<br>Request timed out.<br>Reply from 64.233.167.147: bytes=32 time=174ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=188ms TTL=248<br>Reply from 64.233.167.147: bytes=32 time=172ms TTL=248<br><br>Ping statistics for 64.233.167.147:<br>    Packets: Sent = 33, Received = 27, Lost = 6 (18% loss),<br>Approximate round trip times in milli-seconds:<br>    Minimum = 172ms, Maximum = 205ms, Average = 183ms<br><br>Tracing route to www.l.google.com [64.233.167.104]<br>over a maximum of 30 hops:<br><br>  1   178 ms   173 ms   174 ms  mn-66-247-107-1.sta.embarqhsd.net [66.247.107.1]<br><br>  2     *      163 ms   171 ms  mn-69-34-66-1.sta.embarqhsd.net [69.34.66.1]<br>  3   169 ms   171 ms   174 ms  64.214.140.193<br>  4   184 ms     *      180 ms  te9-2-10G.ar2.CHI2.gblx.net [67.17.109.114]<br>  5     *      202 ms   189 ms  74.125.48.133<br>  6   172 ms   186 ms   187 ms  216.239.48.154<br>  7   186 ms   183 ms   190 ms  72.14.238.89<br>  8   183 ms   182 ms   182 ms  72.14.232.70<br>  9   185 ms   187 ms     *     py-in-f104.google.com [64.233.167.104]<br> 10   182 ms   177 ms   184 ms  py-in-f104.google.com [64.233.167.104]<br><br>Trace complete.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20394928</guid>
<pubDate>Sun, 27 Apr 2008 12:42:52 EDT</pubDate>
</item>

</channel>
</rss>
