Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » OptimumOnline » Lag, Disconnecting in World of Warcraft
Search Topic:
Uniqs:
11803
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
[OOL] Worse Than Dial-Up Tonight? »
« Music hiccups  
page: 1 · 2 · 3 · 4 · 5 · 6
AuthorAll Replies

AdamB2K3

join:2004-03-12
Grand Prairie, TX

1 edit
reply to audious
Re: Lag, Disconnecting in World of Warcraft

This is getting ridiculous already.

46 pages and counting

»forums.worldofwarcraft.com/threa···ageNo=46


Placer

@optonline.net

are you in the NYC area? if so,then i believe its just OOL going through some BS. cause i've never had a problem this bad. this is just UN-RELIABLE right now. my pc works fine surfing and downloading,but when i play a GAME,theres a problem. whether i play a GAME on the PC or the PS2/3....the connection is just F'd up lately.


BLUNTED 1

join:2003-11-13
Floral Park, NY
·Verizon FIOS
·Optimum Online


2 edits
Its not just WOW I get horrible lag on Halo 2 and Halo 3 where my connection goes red bar and when I get host everyone gets red bar connections and the game goes to the reconnecting screen. 2 of my friends with OOL in Suffolk county and the Bronx get this same issue so I wonder WTF they are doing.

rebecca191

join:2008-05-18
Fairfield, CT
reply to ansky08
I haven't noticed any particular lag today, those thousand ping traceroutes look pretty horrible though :-O I hope mine doesn't come back

audious

join:2008-06-03

1 edit
Re: Lag, Disconnecting in World of Warcraft

Still waiting on an update.

AdamB2K3

join:2004-03-12
Grand Prairie, TX

reply to rebecca191
You must have just gotten lucky. How long did you play for and at what time? The problem is still pretty bad for me, every few minutes there is a huge lag spike. I'm not the only one-- this thread on the WoW tech support forum, the majority of replies from cablevision customers, is almost 50 pages long now: »forums.worldofwarcraft.com/threa···pageNo=1

rebecca191

join:2008-05-18
Fairfield, CT
I played all afternoon on one char, then I played for a few hours in the evening on a different char. No d/cs, and I didn't notice spikes either. My ping on one server has always been higher then the other but both were green pings all day.


notme

@optonline.net
reply to ansky08
i think it's them, if you are hosting you get a bunch of requests and they must have something in place to stop the p2p.

MLGTWISTED

join:2007-01-19
Melville, NY
Im getting strange drop outs when hosting now which I've never had before. World of warcraft is getting up to around 8 disconnects per day, its not fun.


BLUNTED 1

join:2003-11-13
Floral Park, NY
MLGTWISTED I am getting this on Halo 2 and 3 with OOL also.\

If you got a friend request from I Vyrax I that is a 1 month trial I made so accept if you want


PetPixel

@optonline.net
reply to ansky08
More of the same tonight. Consistent 550ms latency, which spikes to up to 1600ms and can boot me.

MLGTWISTED

join:2007-01-19
Melville, NY
Tuesday 11:46 pm, June 17th, Huge, huge lag night, disconnects all night. Just got completely cut off, when is it going to end?


WoWPlayer2

@optonline.net

If you have lag in the game (and there was quite a bit last night 10:30pm-2am), please:

a.) call OOL tech support, as called-in identical issues will increase visibility of the scope of the problem for OOL and/or
b.) post to the OOLDirect forum (»/forum/ooldirect)

There seem to be WAY too few posts matching that Subject in the OOLDirect forum (I count about 20 posts since May 25th), vastly lower than the number of posts in THIS thread.

What you will be asked for is essentially the same what Blizzard asked for on the relevant forum thread:

- exact start/end time of the lag/disconnects
- if available: your in-game displayed latency (which is WAY off, and has been observed to be minutes behind the actual lagtime
- provide OOL IP (go to »whatsmyip.org/) and WoW game server IP
- provide traceroute data at the time of the lag, and if you happen to be the attentive kind that is constantly tracerouting around: a traceroute before and after the lag occurred might be useful.

To find the game server IP:
Start->Run->cmd.exe
run `netstat -n`
Find the line where the "Foreign IP" is x.x.x.x:3724 (that's the WoW TCP game port).
run `tracert x.x.x.x` for that IP

Copy&paste (command shell pulldown menu: Edit->Copy) the result for posting/emailing to support - a tad easier than redirecting it to a file and then looking for it (the way Blizzard suggested to do it)

The standard Windows traceroutes will never complete, because Blizzard's game servers are not replying to tracert's packets - once you see more than 3 hops that show "* * *" (unreachable), you can hit CTRL-C to abort. You can't ping them with a standard Windows ping either - a 'security' choice on Blizzard's part.

You can safely ignore, and stop feeling paniccy about a few routers on OOL's network not responding during the traceroute at all. They are busy forwarding more important packets, and generally don't want to disclose certain interface IPs - move along, nothing to see here :
if interested, google for the traceroute(8) man page, editions 1996 or later, for an explanation that has been unchanged before the majority of today's WoW players were born.


ooltech

join:2001-04-04
Woodbury, NY

Hi All,

This issue is supposedly resolved. Please let us know how it goes this weekend. Thanks.

ansky08

join:2005-07-11
New Milford, NJ
I had pretty insanely high ping this weekend. Don't know if it was attributable to bad weather or to the same issue. There haven't been many replies here nor @ the wow forums, I am wondering if the issue is resolved for others.

mute11

join:2008-06-05
Floral Park, NY


2 edits
reply to ansky08
This issue just recurred, disconnect from WOW and unable to get back. The trace shows we're now once again being routed through Cogentco in some crazy new trace that takes 30 hops to hit the destination. It was rock solid perfect until this.

EDIT: Route is back to the new route (Level 3 to AT&T). Any idea why the route would change suddenly like that, and then revert back? Is this going to be a common occurrence?

EDIT: And doing it again. It's some issue with their new route, it eventually reverts back but the route continually changes to some permutation of the old Cogent one. In the past 10 minutes the route has changed probably a dozen times. Ignore the top two hops, the meat is in the trace.

Correct trace:
Trace to: N/A 63.241.255.49
Repeated every 15 seconds

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.13 rtr3-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 12.123.3.57 tbr1.n54ny.ip.att.net
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:33:31 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:33:46 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.14.102 verio.lon02.atlas.cogentco.com
12 129.250.3.254 as-0.r20.nycmny01.us.bb.gin.ntt.net
13 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 12.122.86.98 tbr1.n54ny.ip.att.net
16 -
17 12.122.3.38 cr2.wswdc.ip.att.net
18 12.122.1.173 cr1.attga.ip.att.net
19 12.122.28.174 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:35:01 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 -
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
16 -
17 12.122.86.98 tbr1.n54ny.ip.att.net
18 -
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.1.173 cr1.attga.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 -
23 12.123.16.213 br2.dlstx.ip.att.net
24 12.122.255.226 --------------

Route changed since last log (most recently, 6/26/2008 1:35:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.1.22 te4-2.ccr01.par01.atlas.cogentco.com
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 -
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
16 -
17 12.122.86.98 tbr1.n54ny.ip.att.net
18 -
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.1.173 cr1.attga.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 -
23 12.123.16.213 br2.dlstx.ip.att.net
24 12.122.255.226 --------------

Route changed since last log (most recently, 6/26/2008 1:36:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.1.22 te4-2.ccr01.par01.atlas.cogentco.com
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 154.54.12.82 verio.ord03.atlas.cogentco.com
14 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
15 192.205.35.77
16 -
17 12.122.17.237 cr2.cgcil.ip.att.net
18 12.122.2.22
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.3.221 cr2.dlstx.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 12.123.16.213 br2.dlstx.ip.att.net
23 12.123.16.213 br2.dlstx.ip.att.net
24 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:36:31 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
14 192.205.35.77
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:37:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 154.54.5.209 te9-2.mpd03.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
14 192.205.35.77 --------------
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:37:46 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com
14 192.205.35.77 --------------
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
24 -
25 -
26 -
27 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

Route changed since last log (most recently, 6/26/2008 1:38:01 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.242 te2-2.ccr02.bos01.atlas.cogentco.com
10 154.54.6.22 te2-2.ccr02.ord01.atlas.cogentco.com
11 154.54.5.10 vl3499.ccr02.ord03.atlas.cogentco.com
12 154.54.3.237 gi9-0-0.core01.ord03.atlas.cogentco.com
13 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com
14 12.123.4.246 tbr1.cgcil.ip.att.net
15 12.122.17.149 cr2.cgcil.ip.att.net
16 12.122.2.22 cr2.sl9mo.ip.att.net
17 12.122.2.217 cr1.sl9mo.ip.att.net
18 12.122.3.221 cr2.dlstx.ip.att.net
19 12.122.18.198 tbr2.dlstx.ip.att.net
20 12.123.16.213 br2.dlstx.ip.att.net
21 12.122.255.226 --------------
22 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
23 -
24 -
25 -
26 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

Route changed since last log (most recently, 6/26/2008 1:38:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.13 rtr3-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 12.123.3.57 tbr1.n54ny.ip.att.net
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
19 -
20 -
21 -
22 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

km278

join:2001-04-12
Budd Lake, NJ

reply to ansky08
I'm having a lot of trouble staying connected today.

Tracing route to worldofwarcraft.com [12.129.242.22]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1

2 8 ms 6 ms 7 ms xx.xx.xxx.x

3 7 ms 5 ms 6 ms dstswr2-vlan2.rh.rndhnj.cv.net [67.83.249.162]

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 10 ms 9 ms 9 ms ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]

9 8 ms 9 ms 9 ms 192.205.33.93

10 81 ms 81 ms 82 ms tbr2.n54ny.ip.att.net [12.123.0.94]

11 81 ms 82 ms 81 ms cr2.n54ny.ip.att.net [12.122.16.205]

12 82 ms 81 ms 85 ms cr2.wswdc.ip.att.net [12.122.3.38]

13 87 ms 81 ms 81 ms cr1.attga.ip.att.net [12.122.1.173]

14 83 ms 80 ms 80 ms cr2.dlstx.ip.att.net [12.122.28.174]

15 83 ms 81 ms 84 ms cr2.la2ca.ip.att.net [12.122.28.178]

16 81 ms 81 ms 82 ms tbr2.la2ca.ip.att.net [12.122.19.198]

17 84 ms 84 ms 84 ms 12.127.3.189

18 81 ms 81 ms 81 ms 12.122.255.74

19 81 ms 81 ms 82 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.
Forums » US Cable Support » OptimumOnline[OOL] Worse Than Dial-Up Tonight? »
« Music hiccups  
page: 1 · 2 · 3 · 4 · 5 · 6


Wednesday, 02-Dec 07:54:49 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [153] Comcast Releasing Promised Usage Meter
· [69] Baltimore To Ban Lazy Cable Installs
· [59] Latest Consumer Reports Survey Not Kind To AT&T
· [56] Broadband Killed The Game Console
· [52] Rogers Unveils The ISP Dream Model
· [45] ACTA: Global Three Strikes
· [41] Rural Carriers Quickly Embracing Fiber
· [35] Charter Exits Chapter 11
· [33] AT&T Top Lobbyist Cicconi Has His Feelings Hurt
· [26] Vivendi Agrees, Comcast/NBC Deal Soon
Most people now reading
· IMG 1.7 (IMG Updates and Discussion) [Verizon FIOS TV]
· Windows 7 boot manager editing questions [Microsoft Help]
· [Newsgroups] Newzleech down? [Filesharing Software]
· Ooma changing features [VOIP Tech Chat]
· Patch 3.3 [World of Warcraft]
· [Phish] email from CDC "personal vaccination profile" [Spam, Scam and Phishbusters]
· Heating - my dad gave me this advice... [Home Repair & Improvement]