damn, if it weren't for bad luck...

[gr8expectations]

I must be about the most unlucky webmaster alive. Some of you have read how I was having hosting problems, ATCI was good, moved me to a new server. I have been having sporadic problems even since, pages not loading, not being able to FTP to my sites, this is a pain in the ass. Well today I think I have found the root of it all. Here is a pathping for one of my sites:

Tracing route to xxx.xxx [my IP addy]
over a maximum of 30 hops:
0 my IP addy
1 64.238.178.1
2 209.251.129.77
3 209.251.148.1
4 12.126.150.105
5 12.123.32.110
6 12.122.1.62
7 12.122.12.121
8 12.123.20.201
9 192.205.33.62
10 204.70.192.54
11 208.173.10.201
12 204.70.193.154
13 208.173.10.250
14 208.173.10.250
15 My site

Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 my IP addy
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 64.238.178.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 209.251.129.77
0/ 100 = 0% |
3 4ms 0/ 100 = 0% 0/ 100 = 0% 209.251.148.1
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% 12.126.150.105
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 12.123.32.110
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 12.122.1.62
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 12.122.12.121
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 12.123.20.201
0/ 100 = 0% |
9 32ms 0/ 100 = 0% 0/ 100 = 0% 192.205.33.62
0/ 100 = 0% |
10 32ms 0/ 100 = 0% 0/ 100 = 0% 204.70.192.54
0/ 100 = 0% |
11 29ms 0/ 100 = 0% 0/ 100 = 0% 208.173.10.201
0/ 100 = 0% |
12 28ms 0/ 100 = 0% 0/ 100 = 0% 204.70.193.154
0/ 100 = 0% |
13 34ms 0/ 100 = 0% 0/ 100 = 0% 208.173.10.250
0/ 100 = 0% |
14 35ms 0/ 100 = 0% 0/ 100 = 0% 208.173.10.250
0/ 100 = 0% |
15 28ms 0/ 100 = 0% 0/ 100 = 0% my site

Trace complete.

well the big problem is obviously with 4 IP addresses with 100% packet loss, all of which are AT&T Worlnet IPs.

So I guess the problem is not with my ISP, or else it wouldn't make the second jump, and not with my host, but with some hop in between. Just for curiosity I tried pinging the IPs, here is one result:

Pinging 12.123.20.201 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 12.123.20.201:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Oh yeah, I tried to call At&T about it, was routed to some indian that didn't understand a word of what I was saying, kept asking me if I was on dial up. Then referred me to online help which of course you must be a client to use. I used to work in a call center like that so I know how it goes, but really...How the hell am I supposed to get a hold of a technician at AT&T Worldnet and get something fixed? Fat chance in hell! But I am emailing anyway.

I might mention that this has been going on for more than a week, perhaps longer, you'd think they would have it fixed.

I guess my point is that no matter how much we learn, we can't control shit like the weather, the price of gas, or whether At&T Worldnet is operating. That and I am one unlucky SOB.

If anyone has a suggestion, please post, I am working with a friend to set up a band aid, where I can upload to his box, then it would upload to my server circumventing the bad hops. But this is a real pain in the ass. Anyone have another solution?

[King Porn]

Contact your ISP and ask them to investigate. Also note that not all routers will respond to ping requests by design. These routers may actually be working properly. AT&T may have their routers configured to not respond to simple ping requests. I've sent a trace route to one of your domains with no problems. None of those 21 hops were AT&T though. I've also sent a trace route from DNSStuff.com and there were no issues on those 7 hops.

[mynameisjim]

Dude, you just need a new host.

I know some people swear by ATCI but even the best companies let a few customers fall through the cracks. I think you're one of those customers.

Time to cut your losses and move on.

[SinSational]

Originally posted by mynameisjim
Dude, you just need a new host.

I know some people swear by ATCI but even the best companies let a few customers fall through the cracks. I think you're one of those customers.

Time to cut your losses and move on.

Although this issue is only happening to him, we are most certainly not letting him "fall through the cracks."

Anyway, for all that are interested.....


Here is the trace from the server back to his IP:

[root@ ~]# traceroute 64.238.xxx.xx
traceroute to 64.238.xxx.xx (64.238.xxx.xx), 30 hops max, 38 byte packets
1 hosted.by.cirn.net (69.5.82.67) 0.401 ms 0.298 ms 0.286 ms
2 xe-3-3.e3.iad1.cirn.net (209.222.130.30) 0.811 ms 0.319 ms
3 readnews.por2.ar1.iad1.us.nlayer.net (69.31.31.114) 0.805 ms 7.853 ms 0.892 ms
4 134.po2.ar1.iad1.us.nlayer.net (69.31.31.113) 0.847 ms 0.900 ms
5 g3-5.core01.iad01.atlas.cogentco.com (69.31.30.6) 0.574 ms g3-4.core01.iad01.atlas.cogentco.com (69.31.30.2) 0.440 ms g3-5.core01.iad01.atlas.cogentco.com (69.31.30.6) 0.411 ms
6 t8-2.mpd01.dca02.atlas.cogentco.com (154.54.2.49) 0.695 ms 0.666 ms *
7 v3491.mpd01.dca01.atlas.cogentco.com (66.28.4.85) 1.653 ms 1.793 ms 1.575 ms
Icmp checksum is wrong
8 g11-0-0.core01.dca01.atlas.cogentco.com (154.54.5.53) 14.307 msIcmp checksum is wrong
13.146 msIcmp checksum is wrong
13.120 ms
9 *Icmp checksum is wrong
p15-0.core02.dca01.atlas.cogentco.com (66.28.4.22) 13.378 msIcmp checksum is wrong
13.361 ms
10 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.161) 13.522 ms 13.362 ms 13.316 ms
11 v3502.na01.b002053-0.atl01.atlas.cogentco.com (66.28.67.46) 13.713 ms 14.171 ms *
12 city-of-gainesville.demarc.cogentco.com (38.99.218.198) 29.732 ms 29.557 ms 30.168 ms
13 c7206-1-to-c8510-1.gru.net (209.251.128.9) 30.437 ms 30.760 ms 31.129 ms
14 ssg1-co1-gw.gru.net (209.251.129.75) 30.541 ms 30.764 ms 30.655 ms
15 64-238-xxx-xx.sfp.apt.gru.net (64.238.xxx.xx) 30.317 ms 30.853 ms 32.872 ms


The packet loss starts at cogent.

Traces to your IP from various networks across the US all start showing packet loss.....when hitting cogent.

Without getting too technical, it appears that you are on gru.net, which is a small time ISP, that is connected to the city of gainesville, which is single homed to a cogent connection.

I would contact your ISP again and ask them to look at their cogent connection.

As King Porn mentioned, tracing to your domain from various locations/networks is fine.

[Hammer]

Originally posted by mynameisjim
Dude, you just need a new host.

I know some people swear by ATCI but even the best companies let a few customers fall through the cracks. I think you're one of those customers.

Time to cut your losses and move on.

That's a very unfair post because this has nothing to do with his hosting company.

[mynameisjim]

Let me say I have no experience with ATCI but I did mention that in the post and also said that I have heard some people who swear by ATCI hosting.

It just seems that for whatever reason, this guy has had many problems. Whether it's him, the host, or a combination of the two there comes a time when you have to cut your loses and try something new. It's not always a reflection of the company, it's just a matter of doing what's best for your own interests in a particular situation.

My post was NOT an attack on ATCI Hosting as they seem to be a good company that stands behind their product. My post WAS aimed at this particular person's situation and what I would do if I were him.

I apologize if it seemed like an attack on a specific company because that was not the intention.

[gr8expectations]

Just updating here, no new gossip, except that Chris and Scott @ ATCI have been real stand up in this situation. The support with my ISP has been shit, and I am glad I am moving from florida to oregon in a few weeks, guess that will tell if it is a problem with host, ISP or PC.

I can say that since this has started, ATCI has been proactive in solving my problems.

Just a big thank you to Chris and Scott!

Thankxxx guys
Gr8

[mynameisjim]

Good to hear things are getting taken care of.

Where are you moving to in Oregon? I vacationed up in Bend for a few weeks. Awesome mountain biking there but I did break my leg on the last day...d'oh!

Portland is pretty nice as well. Cool city.