At the risk of sounding harsh…..
I have been receiving complaints of users from cox.net not able to access the site without page time out errors or long delays sometimes up to 10 minutes. This is beyond my control. I have had no complaints from anyone not on cox.net sending any type of email or message relating to the problems that the users on Cox are having. We have users here from everywhere accessing the site and server without incident.
In the past I have had problems with Cox users accessing my service when my servers were co-located in Florida USA. Once again it was only Cox users and no one else had any problems. When the users contacted Cox in the past as well as this time Cox disavowed any problems and it was not their service, THIS IS NOT TRUE. I have completed a trace route routine from my network back through Cox to one of the users here having problems. The results are listed below:
1,73.151.216.1,8ms,c-5-0-ubr01.pottsville.pa.panjde.comcast.net,----
2,68.86.216.101,11ms,ge-6-1-ur01.pottsville.pa.panjde.comcast.net,----
3,68.86.208.241,8ms,ge-9-24-ur01.pinegrove.pa.panjde.comcast.net,----
4,68.86.208.237,8ms,ge-2-24-ur01.lebanon.pa.panjde.comcast.net,----
5,68.86.208.205,12ms,te-9-1-ur01.hershey.pa.panjde.comcast.net,----
6,68.86.208.201,8ms,te-9-1-ur02.lowerpaxton.pa.panjde.comcast.net,----
7,68.86.208.197,11ms,te-9-1-ur01.lowerpaxton.pa.panjde.comcast.net,----
8,68.86.208.193,9ms,te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net,----
9,68.86.208.34,14ms,po-80-ar01.ivyland.pa.panjde.comcast.net,----
10,68.86.208.29,18ms,po-90-ar01.401nbroadst.pa.panjde.comcast.net,----
11,68.86.208.30,15ms,po-80-ar01.wallingford.pa.panjde.comcast.net,----
12,68.86.208.2,21ms,po-80-ar01.audubon.nj.panjde.comcast.net,----
13,68.86.90.30,19ms,te-3-2-ar01.plainfield.nj.panjde.comcast.net,----
14,68.86.84.106,18ms,te-1-1-pr01.newyork.ny.ibone.comcast.net,----
15,68.86.88.90,20ms,nyrkbbrj01-ge020104.r2.ny.cox.net,----
16,68.1.0.49,23ms,None,----
17,68.9.7.2,24ms,None,----
18,68.9.8.38,27ms,None,----
19,----,Timeout,n/a,----
20,----,Timeout,n/a,----
21,----,Timeout,n/a,----
22,----,Timeout,n/a,----
23,----,Timeout,n/a,----
24,----,Timeout,n/a,----
25,----,Timeout,n/a,----
26,----,Timeout,n/a,----
27,----,Timeout,n/a,----
The selections in bold are failed connections. As you can see my backbone is direct to Cox cutting out the middle man. The connection is perfect right up to the point where the connection is handed from New York State in the United States to Cox in Canada. At this time it goes to crap and connections are “TIMED OUT” or lost completely.
Chart layout above:
Connection number, Connection IP Address, Time to connection in milliseconds, Resolved IP
Beagle World is running on a Sun Cobalt 1 Unit rack mountable headless blade server. All the patches and operating system are up to date with no errors on the system. The exact system breakdown is as follows:
Server Setup:
Sun Cobalt Raq4i 1U Blade Server Case
Sun Cobalt Raq550 Motherboard and Processor
512 Meg of Ram
80 Gigabyte Hard Drive.
Dedicated IP Address
Access restrictions (NONE)
Apache/1.3.33 (Unix)
Chili!Soft-ASP/3.6.2
mod_ssl/2.8.22
OpenSSL/0.9.7e
PHP/4.0.6
mod_auth_pam_external/0.1
FrontPage/4.0.4.3
mod_perl/1.29
Average user hits per day on a 1 month period: 1352
Maximum users in site at one time: 140
Network Equipment:
Cisco Data Catalyst 24 Port Switch
Independent Firewall (NONE)
Sites on Server:
Dedicated to abeagleworld.com
Server Photos:
Note: I had taken the server offline and pulled the server to take these photos. Offline time was 10 Minutes this evening starting at 8:02PM EST.
What I am trying to say here is there is nothing I can do about the problems the users are having while using the Cox service. I do wish for these users to continue to come to our community and be a part of this community. The only suggestion I can give you is give all this information to Cox and if they do not fix their problems get a new ISP.