I cant get thru to my server there, or to netfree or the @web site so i assume they are under attack again. :(

Why is this happening...they run along great for a while then bammo they go down...

anyone else having troubles getting thru?

I don't think it surprises anyone anymore.
Just look at the other threads about Atwebhost and Netfree.

Have you tried to call them?

Makes you wonder where the onsite support is at :(

No i havent called them...a call from Oz to them is to expensive...and probably not worth the damn effort. :mad:

I just wish they would move their support site to a remote location.

Ive had no contact with them since the takeover. At least before James or asher would be online to let us know what was going on...now you get nothing...and the forums have gone too...

I would move if i could

Well snowman,

I called them for you .. :)

They said that they had a problem with their router which need to be reboot. It should come back up in a few minutes.

Why thanks :)

However i dont think that is the only problem down there...

Tracing route to atwebhost.com [69.10.11.23]
over a maximum of 30 hops:

1 * * * Request timed out.
2 105 ms 823 ms 101 ms vl109.sw02.mel.iprimus.net.au[192.168.96.26]
3 100 ms 100 ms 100 ms 203.134.50.22
4 271 ms 275 ms 273 ms POS4-1.cr1.sjc.primustel.com [209.227.129.241]
5 328 ms 322 ms 319 ms ATM6-0-101.cr1.ord.primustel.com [209.227.128.62]
6 343 ms 342 ms 339 ms ATM6-0-102.cr2.jfk.primustel.com [209.227.128.74]
7 339 ms 341 ms 550 ms G2-0-20.cr1.jfk.primustel.com [209.227.131.3]
8 351 ms 345 ms 489 ms ATM6-0-103.cr1.phi.primustel.com [209.227.128.6]
9 357 ms 1581 ms 1816 ms ATM6-0-101.cr1.dca.primustel.com [209.227.128.14]
10 2684 ms 3175 ms 3092 ms G2-0.pr1.dca.primustel.com [209.227.134.8]
11 351 ms 352 ms 346 ms mae-east-atm1.wcg.net [198.32.187.38]
12 469 ms 404 ms 389 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
13 386 ms 383 ms 380 ms drvlga1wcx1-oc48.wcg.net [64.200.127.29]
14 553 ms 768 ms 390 ms miamfl2wcx3-oc48.wcg.net [64.200.240.17]
15 1835 ms 395 ms 385 ms miamfl6lce1-pos5-0.wcg.net [64.200.119.90]
16 371 ms 369 ms 370 ms miamfl2wcx3-yipes-gige.wcg.net [64.200.118.214]
17 373 ms 373 ms 372 ms 66.227.93.254
18 500 ms 382 ms 781 ms 66.7.158.52
19 * 421 ms 415 ms 216.82.72.66
20 * * * Request timed out.
21 * * * Request timed out.
22 * 822 ms * 69.10.11.23
23 * * * Request timed out.
24 1086 ms 1307 ms * 69.10.11.23
25 * 574 ms 816 ms 69.10.11.23

Trace complete.

its up now ..

I was with them for about 4 months and I'd say it was for the majority up/down fairly often. I left last month but I can tell you that this is no suprise to me (the problem you describe)

I was with them for about 4 months and I'd say it was for the majority up/down fairly often. I left last month but I can tell you that this is no suprise to me (the problem you describe)

Same story here!

Originally posted by drhonk
Well snowman,

I called them for you .. :)

They said that they had a problem with their router which need to be reboot. It should come back up in a few minutes.

I honestly cannot count how many times atwebhost has blamed their problems on their routers. :rolleyes:

Anyone know what this downtime is being caused by? Can't wait until the 12th this sucks...

what happens on the 12th?

Bye bye @web and hello nocster (http://www.nocster.com/presale.shtml).

As you can see, I've :: Lost Hope::.

Is there an issue again at the moment???

my server pings ok but my nameservers dont, ive done the ususall suspect things like restart bind and httpd but still nothing

I started my server with atwebhost in the beginning of november. For the first month, uptime was near 100%. But, in the beginning of December, they had a problem with a router, causing my server to be down for 30 HOURS. I was wise and jumped ship as soon as that happened. I figured that if it took them 30 hours to replace a router, there was going to be more problems in store.

I think the bottom line is......

Nobody has anything good to say about @webhost!!

I suddenly lost apache, bind and mysql this morning, we got it all up again but now the main nameserver IP for the account on the server doenst want to work.

I put in a support ticket 4 hours ago and just to make sure i got sent an email to support at the same time...i got no reply...and hour ago i spoke to someone there who said he was on the other side of the building and that he would get a tech to look at the issue, however nothing sbeen doen and i just called back and got a message box...

not happy