You aren't the only one, trust me. I just got off the phone with Tier2 support at Cox, I think they're getting tired of hearing from me. Another batch of test results emailed to them, along with Brad's explanation of the problem from above (with the word "competent" edited out -- I ain't trying to change the world here, just fix the problem). We'll see what, if anything, happens.

Do this, though, read Brad's long post above and do the workaround suggested in the last paragraph. It DOES work. It won't help your CUSTOMERS who are Cox users and can't reach your server... but at least YOU will be able to get some work done, while retaining at least a modicum of sanity.

Still unreachable in Kansas through Cox
I have a very good connection.. I always make them run a new drop and I use a DC tap.. Plus I use good heavy center conductor drop wire throughout my home. It's wired perfectly. The good side of the tap goes to my modem, the weaker side goes directly to a signal booster AT THE BOX and then out to the televisions.

Also the part I don't have knowledge of at all, the pole to pole lines, that is all very very good in my area.

Also unreachable via Cox in Scottsdale, AZ.

not reachable from AZ cox.

Guys & gals, please do this if you can't access MojoHost through Cox, it's simple and fun (instructions are for Windows users, Mac users... well, do whatever's the equivalent):


Part 1

1) Open up a DOS window (Start button, Run, cmd)

2) Type

tracert mojohost.com

and press Enter.


Part 2

When it's complete, you'll have a list of IP addresses along the way. For each of the IPs that come up in the list (except the first one if you're using a wireless router), type

ping -l 1500 xxx.xxx.xxx.xxx

replacing the x's with the IP and press Enter. This shoots a 1500 MTU packet through to that IP. If it's successful, repeat with the next IP until you get to one that times out.


Part 3

Once you've got one with a timeout, right-click somewhere in the window and pick Select All. Everything will be highlighted. Then right-click again and the highlight should disappear. You just copied everything to the clipboard. Paste it into a new email.


Part 4

Call Cox Internet Tech Support and tell them you're in the middle of an issue that Tier2 support is working on. If they won't immediately transfer you, tell the frontline tech that PMTUd is being broken by one of Cox's routers along the tracert and you have ping information that Tier2 needs. Get to Tier2 however you can, the frontline guys are pretty clueless.

When you get a Tier2 tech, tell them that you're experiencing the MTU packet loss problem that Cox has had the past few days. This will establish with the tech that there's a current problem, in case they aren't aware.

Next, tell them that normal size 1500 MTU packets are being dropped when you try to access THE SERVER THAT YOUR BUSINESS WEBSITE IS ON. This will establish that you aren't just having problems playing Warcrack.

Finally, tell them you did a traceroute to your host, then ping'ed a 1500 MTU packet to each hop's IP. You have the point at which the packet is being dropped, you'd like to email the results to them, and to what email should you send it.

If enough people do this, from enough different cities/regions, maybe there'll be some definitive action taken on this.

Goodnight and good luck. :thumbsup

Note: This is bouncing around the upper limits of my tech knowledge in this area. If I'm incorrect on something or there's a better way, someone feel free to post a correction and call me a dipshit or whatever's on your mind at the moment.

Fucking cox had to decrease my packet size to get to my servers. I would cancel if I actually had a fucking alternate service in my area.

Brings back memories of the first DSL trials and initial takeup in Australia around the start of the millenium... at that time many sites simply blocked all ICMP, which breaks MTU discovery. No problems on analog modems, but those pesky PPPoE customers suddenly found they couldn't load their favourite sites. If you think it's hard getting a single ISP to remove or modify a firewall rule, imagine trying to educate hundreds of sites on why blocking *all* ICMP is a bad idea..... hey dude, it works off the office LAN, it works on my modem at home, GGF

Yep, problem still exists. This is really getting old. Time for more phone action.

Anyone on COX experiencing this problem please email [email protected] with your IP address and also a trace to mojohost.com

Unbelievable.

Thank you,

Brad

It's all reachable, for me, now..

Here is a pathping in case you want to see a WORKING route and packetloss from europe


pathping mojohost.com

Sporer rute til mojohost.com [64.59.69.66]
over et maksimum af 30 hop:
0 sdt001.opasia.dk [192.168.0.100]
1 192.168.0.1
2 xxxxxxxxxxxxxxxxxxxxxxxxxxx]
3 xxxxxxxxxxxxxxxxxxxxxxxxxxx]
4 ge-1-0-0-1000M.virnqu2.ip.tele.dk [83.88.29.254]
5 xe-1-0-0.virnxu5.dk.ip.tdc.net [83.88.4.161]
6 xe-0-0-0.virnxu4.dk.ip.tdc.net [83.88.2.253]
7 pos0-1-3-0.alb2nqh2.dk.ip.tdc.net [83.88.2.250]
8 ge-5-1-0.alb2nxu7.dk.ip.tdc.net [83.88.31.158]
9 kbn-b1.telia.net [195.215.109.2]
10 kbn-bb1-pos1-0-0.telia.net [213.248.65.9]
11 nyk-bb1-link.telia.net [80.91.249.21]
12 ash-bb1-pos6-0-0-0.telia.net [213.248.80.68]
13 atl-bb1-link.telia.net [80.91.252.214]
14 mai-bb1-link.telia.net [80.91.251.29]
15 mojohost-ic-124233-mai-b1.c.telia.net [213.248.104.166]
16 sh04.mojohost.com [64.59.69.66]

Beregner statistik i 400 sekunder...
Kilde tilher Dette node/Dette link
Hop RTT Tabt/Sendt = Pct Tabt/Sendt = Pct Adresse
0 sdt001.opasia.dk [192.168.0.100]
0/ 100 = 0% |
1 30ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 43ms 0/ 100 = 0% 0/ 100 = 0% xxxxxxxxxxxxxxxxxxxxx
0/ 100 = 0% |
3 40ms 0/ 100 = 0% 0/ 100 = 0% xxxxxxxxxxxxxxxxxxxxxx
0/ 100 = 0% |
4 33ms 0/ 100 = 0% 0/ 100 = 0% ge-1-0-0-1000M.virnqu2.ip.tele.dk [83.88.29.254]
0/ 100 = 0% |
5 66ms 0/ 100 = 0% 0/ 100 = 0% xe-1-0-0.virnxu5.dk.ip.tdc.net [83.88.4.161]
0/ 100 = 0% |
6 57ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-0.virnxu4.dk.ip.tdc.net [83.88.2.253]
0/ 100 = 0% |
7 54ms 0/ 100 = 0% 0/ 100 = 0% pos0-1-3-0.alb2nqh2.dk.ip.tdc.net [83.88.2.250]
0/ 100 = 0% |
8 45ms 0/ 100 = 0% 0/ 100 = 0% ge-5-1-0.alb2nxu7.dk.ip.tdc.net [83.88.31.158]
0/ 100 = 0% |
9 77ms 0/ 100 = 0% 0/ 100 = 0% kbn-b1.telia.net [195.215.109.2]
0/ 100 = 0% |
10 67ms 0/ 100 = 0% 0/ 100 = 0% kbn-bb1-pos1-0-0.telia.net [213.248.65.9]
0/ 100 = 0% |
11 145ms 0/ 100 = 0% 0/ 100 = 0% nyk-bb1-link.telia.net [80.91.249.21]
0/ 100 = 0% |
12 142ms 0/ 100 = 0% 0/ 100 = 0% ash-bb1-pos6-0-0-0.telia.net [213.248.80.68]
0/ 100 = 0% |
13 163ms 0/ 100 = 0% 0/ 100 = 0% atl-bb1-link.telia.net [80.91.252.214]
0/ 100 = 0% |
14 173ms 0/ 100 = 0% 0/ 100 = 0% mai-bb1-link.telia.net [80.91.251.29]
0/ 100 = 0% |
15 180ms 0/ 100 = 0% 0/ 100 = 0% mojohost-ic-124233-mai-b1.c.telia.net [213.248.104.166]
0/ 100 = 0% |
16 163ms 0/ 100 = 0% 0/ 100 = 0% sh04.mojohost.com [64.59.69.66]

Working here now, too. Thanks for the hard work, Brad et al.

I am cautiously optimistic that Cox has resolved their issue, finally. We have been working directly with their NOC and multiple users who were previously affected are not anymore.

Please let me know by email/phone ASAP if any further problems are experienced.

Brad

Final update: I have confirmation from Cox about their issue in Dallas and have high confidence this issue is permanently resolved. Thank you everyone for your patience and fortitude during this most unusual and frustrating problem.

Sincerely,

Brad Mitchell

That is just too funny. I told the last tech I dealt with Thursday night that it looked like the problem was either in Dallas or Tulsa. He said "well, it's definitely not Dallas."

:1orglaugh

I just reported a cox issue in AZ...

Spoke with Cox and it appears that this issue is still resolved and that this user experienced the problem prior to 3pm EST.

Brad

working fine for me in az now.

Loads fine for me, but I'm not in Vegas.

FYI, I'm currently having access problems from Vegas to Mojohost but it looks like a different kind of routing problem. It's being checked out right now, probably unrelated to the earlier issue.

Looks like Cox is fucking up again today. I hate calling them because they claim it is never their issue. GRRR

Down for me again

I am on the phone with carriers right now. Stay tuned, we have better direct contacts since Sunday. This just popped up all at once within the last 30 minutes.

Brad

See my post above. Brad @ MojoHost is on it. That's good enough for me.

Thanks for the info. :)

any positive feed back for mojohost?

sorry for double post .. :)

Really, if you read this thread and have to ask that question, I'm not sure what more could be said.