Is anyone else having internet problems?  Several areas in Jefferson County are having very slow service or no service at all.  It's been going on since yesterday mid-morning.

"It's Happening!"  TEOTWAWKI!

charter- yes

My charter was out from 1700-2300 or so.

same, but much better today.

My charter was out yesterday.  I was rocking the 3G on my old IPad.

Yep.

Our Charter crapped out a good portion of the day yesterday and was slow and choppy prior to it going out. I'm in the St. Charles area.

I just figured the NSA was installing some new hardware.  

Supposedly charter had major DNS problems. I didn't even notice. Having your own DNS server has advantages.

My connection doesn't go through Charter.  The first two hops are my wide area wireless and are confidential.  The 69.xxx.xxx.xxx are my ISP, who has a connection with Level 3.  The 98.xxx.xxx.xxx and 216.xxx.xxx.xxx addresses belong to Yahoo.  I checked the DNS server settings and they are not Charter either.  I'm questioning my ISP's routing.  I know it well because I sold them the business five years ago.  It shouldn't ever take six slow hops to get to Level3.

Tracing route to ds-any-fp3-real.wa1.b.yahoo.com [98.138.253.109]
over a maximum of 30 hops:

 1     4 ms     3 ms     2 ms  xx.xx.1.153
 2   293 ms    35 ms    24 ms  xx.xx.1.21
 3    18 ms    12 ms    18 ms  69.44.6.1
 4   197 ms    56 ms    70 ms  69.44.4.129
 5    31 ms    29 ms    99 ms  69.44.4.233
 6   156 ms  1141 ms   629 ms  69.44.6.37
 7   139 ms    31 ms    55 ms  209.40.238.85
 8   593 ms    64 ms    35 ms  69.44.4.3
 9    23 ms     *       37 ms  ge-8-37.car2.StLouis1.Level3.net [4.53.162.249]

10    64 ms    62 ms    64 ms  ae-5-5.ebr1.Chicago2.Level3.net [4.69.201.1]
11   534 ms   175 ms    40 ms  ae-1-51.edge3.Chicago3.Level3.net [4.69.138.136]

12   326 ms   148 ms    73 ms  YAHOO-INC.edge3.Chicago3.Level3.net [4.53.96.158
]
13   434 ms   124 ms   123 ms  ae-7.pat1.nez.yahoo.com [216.115.104.124]
14   239 ms   267 ms   240 ms  ae-1.msr1.ne1.yahoo.com [216.115.100.5]
15   140 ms   106 ms   249 ms  ae-0.clr1-a-gdc.ne1.yahoo.com [98.138.144.21]
16   386 ms   182 ms   134 ms  UNKNOWN-98-138-97-X.yahoo.com [98.138.97.27]
17   232 ms   136 ms   220 ms  po-11.bas1-7-prd.ne1.yahoo.com [98.138.240.8]
18   154 ms   247 ms  1060 ms  ir1.fp.vip.ne1.yahoo.com [98.138.253.109]

Trace complete.

Pinging ds-any-fp3-real.wa1.b.yahoo.com [98.139.183.24] with 32 bytes of data:

Reply from 98.139.183.24: bytes=32 time=123ms TTL=40
Reply from 98.139.183.24: bytes=32 time=107ms TTL=40
Reply from 98.139.183.24: bytes=32 time=170ms TTL=40
Reply from 98.139.183.24: bytes=32 time=97ms TTL=40
Reply from 98.139.183.24: bytes=32 time=76ms TTL=40
Reply from 98.139.183.24: bytes=32 time=88ms TTL=40
Reply from 98.139.183.24: bytes=32 time=104ms TTL=40
Reply from 98.139.183.24: bytes=32 time=95ms TTL=40
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Looks like you have something else going on. That is definitely a crazy looking trace.

There is definitely some latency going on, on several of those hops...  I'd forward that on to your buds there and have them take a look at those...



I haven't seen or heard anything as I've been at the cabin all weekend, but from what I gather its a DNS issue...  



Must be either a large scale DOS attack or something poisoning the tables, whether accidental or on purpose...  I'm hearing people change their DNS server address to something else and that fixing the issue, but could cause other issues later...
 

Charter's DNS servers are having serious issues switching to google's DNS servers fixed the problem instantly.

Charter's wonky again.

Not saying there isn't anything going on in your area, but I've not seen anything global going on in email and I'm not having any issues...