Cox → [CT] Disconnects, Routing Changes, Pauses...

Still no answers here in CT regarding the events of the last couple of days. The Cox Network Status page does not indicate any issues at all, even though the connection is not a very healthy one. A comparison of ping plots with friends in Southington and Wethersfield indicates identical patterns of dropouts lasting from 5 to 10 seconds every minute, with corresponding route changes taking place once or twice a minute. It would appear that everything passing through Rhode Island is whacked. A call to tech support with a direct question about the packet loss/disconnect issue resulted in the comment that "Cox is aware of the problem and expects a resolution very shortly." Heh, they didn't even bother to have me unplug my modem! I suggested that they might reduce their volume of calls to tech support if they updated the network status page for CT and the tier one man thanked me for the suggestion... Okaaayyy.

Have a nice day!

Ender

It didn't help either that parts of Meriden just had the 2nd two hour power outage in about two weeks.

totally crazy here in Cheshire. What the hell gives?????

jkk

...And then, at just about 10pm, someone, somewhere, throws a switch, and... "CLICK" ...things go back to normal. Same scenario as last night. It all falls apart at just about 7:00pm, and then at 10pm, things look just peachy. What's up with that? What are you up to Cox???

Ender

Yup, same here, everything fine again.

And all of a sudden...POOF, it's GREAT again. Just GREAT. Now i mysteriously have a stable ping. Except with me...it stopped at 12:00 midnight eastern, exactly at this time. Cox needs to get their act together, cuz their service is looking more and more like a high school networking assignment. Anyway...i have a CS match tomorrow and i'd bet a hefty ammount of my savings that the entire state will packet ALL over again beginning at or around 7 PM east. I hate these guys =(

2:30 AM est, packet loss starting again.

We performed some traffic engineering last night that should remedy the issue, even in the event of a MyDoom attack.

Please let me know if there are still issues this evening.

Thanks.

P.S. This would have explained the packet loss at 2:30...

whatever you did last night at 2:30am did now work...
Im showing connection reset at 5:34am and another at 6:46am

68.14.80.1 gateway......

Im going to monitor this all day long of course.

said by ridataguy:

---

We performed some traffic engineering last night that should remedy the issue, even in the event of a MyDoom attack.

Please let me know if there are still issues this evening.

Thanks.

P.S. This would have explained the packet loss at 2:30...

---

Thank you for addressing the issue. Our frustration rises when we think no one is aware, so it is reassuring to have a contact person from Cox step into the thread. Your efforts are appreciated.

Regards,

Ender

said by ridataguy:

---

We performed some traffic engineering last night that should remedy the issue, even in the event of a MyDoom attack.

---

It has been back to normal here in Northern CT this evening. Low pings, no pauses, no rapid routing changes, no packet loss in the Cox end of the equation. Well done!

Ender

As i figured you fixed didnt do anythign...
its midnight and PER ususal here we go this is the third outage now since midnight its 12:10am

----68.14.80.1 PING Statistics----
133 packets transmitted, 101 packets received, 24% packet loss
round-trip (ms) min/avg/max = 23/26/82

NICE

I Am Also Experiencing The Same Problems Here, Massive Packet Loss, High Latency...

You know whats funny....
Is I tell the tech people at cox these outages Happen the same times every year..... and here I am looking at the last time i was so pissed off I was ready to switch to dsl and joined this forum EVERYONE look at my JOIN date........
Joined 01-29-2002

You think its a coincidence?

I dont think so i have been logging these outtages for 2+ years now....
Gee now the gateway is totally down....

----68.14.80.1 PING Statistics----
554 packets transmitted, 70 packets received, 87% packet loss
round-trip (ms) min/avg/max = 23/25/96

thankgod I have emergency dialup

I've been on the phone with Cox all day for the past 3 days. Service went completely dead at around 12:00am this morning. I play professional poker online and got completely taken out of yet another tournament. Cox has costed me over $500 in lost buy-ins this week. I even adjusted my sleep schedule to sleep during the 5-10pm primetime hotzone where it's non-stop disconnects. Other ISPs aren't having these issues, or at least not as bad. At times, I want to go absolutely postal on these people with a sawed off shotgun. VIGILANCE! I had one customer service rep have the nerve to tell me I should sign up for their service assurance plan. As if insulating my wires with aluminum foil is going to fix the problem. Another said that the mydoom virus is the cause and it expires on the 12th. If I have to wait another 7 days blood will be spilled. Ok, maybe not, but I will scream and yell and maybe even use some 4-letter words. And then they will credit my account or get more 4-letter words.

Cox you suck!

just loss packets for 10seconds there again..............
that would be the 1am loss time slot...
now we jsut need to watch 2am and 3am.........

I have one computer on dialup now and the other on cox....

the dialup is way better!

im sorry mydoom has nothign to do with this...

These packet losses started exactly 1/1/04 at midnight....

I play online games till 3am so i know every single time cox has these probs and they started 1/1/04 and its gotten worse everyday since....

of course all day today was CLEAN....
but per ususal i dont give that any merit because until they REALLY fix the problem its GOING to happen after midnight again.... until they REALLY fix the problem

the 2am disconnects have now arrived....
awlays internal cox network cant get to 68.8.9.8.117

Request timed out.
Reply from 68.9.8.117: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 208.222.148.11: bytes=32 time=20ms TTL=238
Request timed out.
Request timed out.

06/2002
68.9.8.33 was unreachable back then....

Request timed out.

Reply from 68.9.8.33: Destination host unreachable.

Request timed out.
Ping statistics for 208.222.148.11:
Packets: Sent = 480, Received = 468, Lost = 12 (2% loss),

Definately not fixed here in Cheshire.. What is going on here?

jkk4, coxisbroke, and vigilance3...IM your MAC addresses to me, and I'll take a look...

Thanks.

yeah I'm in cheshire, they changed my ip over to that new one with that new gateway its all the same stuff.....

When I get home I can get that info.

but your saying last night after midnight that 20 minute black out wasnt service being done?
The cable modem was not able to find the network and from my dialup connection the gateway was not online nor was any modems that I checked.

Ridataguy, how do I get my MAC address and how do I IM it to you. On Yahoo or AOL IM? Sorry about that...

jkk

You get to a dos window
start-run-cmd for nt win2k xp

type ipconfig /all
you will see
Physical Address. . . . . . . . . : ??-??-??-??-??-??

that is your mac address and this assumes you are directly connected to your cable modem, if not then u need the mac address of the router.... which will look like that also somewhere in its config.

win98 you would do start-run-winipcfg
select the correct tcp/ip adapter and you will see this in adapater address
this address is your unique id in the cox network.

»ridataguy

is Ridataguy contact info from the topic in here how to contact the techs in here.

said by coxisbroke:

---

You get to a dos window
start-run-cmd for nt win2k xp

type ipconfig /all
you will see
Physical Address. . . . . . . . . : ??-??-??-??-??-??

that is your mac address and this assumes you are directly connected to your cable modem, if not then u need the mac address of the router.... which will look like that also somewhere in its config.

win98 you would do start-run-winipcfg
select the correct tcp/ip adapter and you will see this in adapater address
this address is your unique id in the cox network.

---

Actually, that will give you the MAC address of the Ethernet card in your computer.

We need the MAC address of your cable modem...it is how we lookup your account since that info isn't available on this forum

The MAC address of your Cable Modem is usually on the modem itself

ah ok, the question didnt specify the modems mac address.
I will get that tonight.

I will get the info also tonight. Since I'm running through a Linksys Router, then you need the MAC address of the router and not the modem?

jkk

said by jkk4:

---

I will get the info also tonight. Since I'm running through a Linksys Router, then you need the MAC address of the router and not the modem?

jkk

---

No, he'll need the MAC address of the Cable Modem (see above) to locate your equipment. The router address won't help.

said by dg2:

---

said by jkk4:

---

I will get the info also tonight. Since I'm running through a Linksys Router, then you need the MAC address of the router and not the modem?

jkk

---

No, he'll need the MAC address of the Cable Modem (see above) to locate your equipment. The router address won't help.

---

They can also get that information from your primary email account if you don't feel comfortable giving out your MAC addy......

Plasticman

Can you guys clear one thing up?

As far as I can tell ever since the redirecting of port 25 went into effect which i think ALL cable/dsl companies should be doing since I am in control of 4 email servers and the spam from these modems is unrelenting, you also blocked tracerouting....
I can not traceroute from work to a cable modem in cox and I can not traceroute out from home.
I can traceroute to the my gateway and the cable modems gateway of course... thats 1 hop....
But I can not traceroute beyond the 10.4.126.1 the cable modems gateway.
One tier2 guy obviously clueless 1st told me 10.4.126.1 was my cable modem, then told me since i cant traceroute beyond my cable modem then my cable modem is bad.....
never amazes me some of the things people say.
I was like um, I can ping fine which means my packets are going out then coming back totally fine the cable modem is not flawed and in fact was just tested 100% working the day before by a tech at my house, I did not even bother pointing out its a good guess an with .1 at the end is pretty much NOT my cable modem.

so anyway.... tracerouting is blocked on purpose or by accident?