Hey this is a worry for me.

I just paid for a year on PowWeb, (for a client) and now I can't access my site, nor can I access PowWeb itself. Have they gone broke? Is there some US regulatory body I check this type of thing out with?

TIA

Cindy xxx

If you are referring to

"www.powweb.com"

I am not sure?

But they are up and running for me.

Are you sure it's not your cache working? Both myself and my client can't access PowWeb at all, whether it's the ops.powweb.com bit, or the main site. Also, all amails are bouncing back. You can see why we're concerned.

Can you think of any other reason why this could be happenning? We're in Australia, but other USA websites (like this one!) are accessible.

Cin xxx

I can access Powweb right now just fine. Most likely it's a connection problem for you. Try running a tracert from your computer to your site or Powweb's.

George -- thanx for your reply

Tracert runs from Start|Run tracert http://www.powweb.com doesn't it? I tried, but all I get is a blank DOS screen.

So I tried Rackspace's Tracerout and got:
traceroute to www.powweb.com (64.63.125.210), 30 hops max, 38 byte packets
PLUS a whole bunch of ???.???.???.??? numbers and stuff.

Then I tried the client's site http://www.newlandfoodco.com and I got:
traceroute to newlandfoodco.com (64.63.125.22), 30 hops max, 38 byte packets
PLUS a whole bunch of ???.???.???.??? numbers and stuff.

So then I tried my ISP and got almost the same, except it froze. I hit the Esc key and it stops at hop number 12, where all the others wne tot hop number 14.

I'm a bit out of my depth here -- just a simply graphic designer, really. All this web stuff is a bit much for me!

Do you think I should call my ISP and complain?

Cin xxx

Originally posted by cindyjames


Do you think I should call my ISP and complain?

Cin xxx

Hell yes, and be quick before you loose the customer.

then ask them to see if the site comes up on there system

Mike

Hi cindyjames:
First off the problem most likely is temporary with your ISP, so I would just wait, at least for 8-12 hours before considering calling em'. Usually these things just resolve themselves. I remember one time I couldn't access my site for over 6 hours. I knew the problem was with my ISP, so I sat still.

Secondly, since the problem seems to be a connection problem between you and your web host, your tracert should reflect that. In other words, you should run the tracert NOT from say Rackspace, but from your computer to your site.

To run a tracert, you could go to MS DOS Prompt, and just type:

tracert yoursite.com

Press enter after that.

You guys are just GREAT!!!!

Thans so much for all your help. I've decided to ring my ISP, and of course, like most Aussies, they're out to lunch until the new year. So I guess we'll just have to wait.

Thanx again . . . and don't get too drunk on new year's!

Cin xxxx

Sorry if this is a hassle -- but could one of you try http://www.newlandfoodco.com and see if it's ok as well? That way I can at least deflect the blame onto the ISP

Thanx again

Cin xxx

Originally posted by cindyjames
Sorry if this is a hassle -- but could one of you try http://www.newlandfoodco.com and see if it's ok as well? That way I can at least deflect the blame onto the ISP

Thanx again

Cin xxx

Works like a charm for me :)

Sprintlink > InterNap > YOU
-no problem (from S. Cali)