get a fucking clue+ before you go talking shit about your hosting company
 

You people are too fucking much. YOUR DSL/CABLE/DIALUP fucking suck and you go and report your hosting company as having a shitty link/network/business and yet the problem lies with you.

I have seen numerous complaints in regards to likewhoa being down, or extremely slow. I'm using about 5-10MBit/sec of non cogent bandwidth from likewhoa.

While i have experience some issues with connectivity and a little downtime i think it has been made a big deal of when it probably shouldnt.

While i admit it hasnt been the most stable, while i havent been a customer long, and judging from all the complements they've got in the past i really dont think they're as bad as people who are having connectivity issues @ their house are making them out to be.

Mind you, i have backup machines incase i lose a mirror machine for the streams but thats just commonsense so losing a server for hours really wouldnt affect me.. Failsafe is good!

My MRTG graph only shows two outages and once was my fault since snmpd stop running.

Just my 2cents

PS: dont take this is me defending likewhoa (which it might appear that i am) but when the problem is you and your reporting someone else as the problem and probably weakening a business because of your own stupidity then that isnt fair.

ok

:1orglaugh

:eek7

Okay guess my connection is just bad then. :1orglaugh

No, your connection is good, it's just the 3 networks i have machines on not working right because i got decent access time/routes to likewhoa ;)


2 878.ATM2-0.gw4.tor2.ALTER.NET (205.150.100.69) 0.881 ms 0.868 ms 0.836 ms
3 115.ATM2-0.XR1.TOR3.ALTER.NET (152.63.129.242) 1.058 ms 1.234 ms 1.309 ms
...
15 66.181.176.146 (66.181.176.146) 35.017 ms 35.081 ms 34.921 ms


2 metro-7.ix.ai.net (209.120.218.1) 2.151 ms 2.396 ms 2.198 ms
3 washdc7lce1-gige.wcg.net (64.200.94.229) 2.171 ms 2.345 ms 2.123 ms
...
10 66.181.176.146 (66.181.176.146) 9.596 ms 9.644 ms 9.641 ms

2 hadrian1.tor.velocet.net (216.138.223.1) 6.495 ms 6.365 ms 6.035 ms
3 hadrian10.ny.velocet.net (216.138.255.10) 18.720 ms 18.554 ms 18.472 ms
4 yipes2-velocet.ny.velocet.net (66.54.171.250) 19.528 ms 18.525 ms 20.364 ms
5 ge-3-1.core1.ny.likewhoa.net (66.7.129.227) 20.844 ms 19.675 ms 19.659 ms
6 66.181.176.146 (66.181.176.146) 19.418 ms 20.615 ms 20.126 ms

2 22 ms 13 ms 12 ms dstswr1-vlan2.rh.nyk2ny.cv.net [67.83.220.161]
3 7 ms 7 ms 7 ms ool-4353dc81.dyn.optonline.net [67.83.220.129]
4 12 ms 19 ms 14 ms r3-srp1-0.cr.hcvlny.cv.net [167.206.12.37]
5 23 ms 15 ms 21 ms r1-srp1-0.wan.hcvlny.cv.net [167.206.12.98]
6 10 ms 7 ms 8 ms r1-srp5-0.in.nycmny83.cv.net [167.206.12.117]
7 23 ms 18 ms 31 ms pos5-2.pr1.lga1.us.mfnx.net [167.206.8.154]
8 16 ms 22 ms 19 ms so-3-0-0.cr1.lga1.us.mfnx.net [208.185.0.237]
9 9 ms 7 ms 7 ms so-1-0-0.cr1.lga3.us.mfnx.net [64.125.30.18]
10 13 ms 21 ms 22 ms 64.124.11.173.likewhoa.com [64.124.11.173]
11 29 ms 23 ms 19 ms ge-3-8.core1.ny.likewhoa.net [66.181.190.1]
12 7 ms 7 ms 11 ms ns2.likewhoa.com [66.181.170.170]


:thumbsup

LikeChill man, we are just having LikeFun bitching about a hosting company.

You don't see me complainting, of course am with Verio.:1orglaugh

I guess it is my connection too. I have never had a problem with it but hey it is my connection not LWI or its fast, low latency, reliable upstream providers.


:1orglaugh

6 61 ms 47 ms 50 ms so-1-0-0.cph10.ip.tiscali.net [213.200.81.5]
7 50 ms 49 ms 57 ms so-2-0-0.cph20.ip.tiscali.net [213.200.81.33]
8 59 ms 49 ms 55 ms so-2-0-0.dus10.ip.tiscali.net [213.200.81.129]
9 99 ms 55 ms 98 ms so-6-0-0.fra40.ip.tiscali.net [213.200.81.29]
10 99 ms 49 ms 57 ms so-4-0-0.fra30.ip.tiscali.net [213.200.81.17]
11 181 ms 162 ms 155 ms so-7-1-0.nyc30.ip.tiscali.net [213.200.81.201]
12 148 ms 160 ms 155 ms so-5-2-0.nyc10.ip.tiscali.net [213.200.82.129]
13 157 ms 152 ms 162 ms ny-iix.above.net [198.32.160.22]
14 173 ms 160 ms 154 ms mfn.core2.ny.likewhoa.net [64.124.11.173]
15 184 ms 144 ms 162 ms ge-3-8.core1.ny.likewhoa.net [66.181.190.1]
16 179 ms 144 ms 154 ms ns2.likewhoa.com [66.181.170.170]


Tiscali is sexy :D

Nick must be a genius... he has downtime and the haters still can't win.

:thumbsup

FUCK CONNECTIONS SPEED, what about the 24 hours of strait down time days on end??:321GFY

i'll say only one thing

I BREATHE LIKEWHOA AIR AND I FEEL GREAT

My host hasnt been down for 1 minute in 59 days ;) And I pay 200 dollars per month for 1mbs.

:1orglaugh :1orglaugh :1orglaugh Nothing personal but business is business when our sites down we're loosing money, traffic its business! so if we're down you better belive people are gonna flame when they cant get answers and get a run around thats really a cookie cutter bs answers to why shit isnt being fixed.

I think the internet is down :1orglaugh

deniska--
Do you have free host software for pay site programs who use your hosting?

I thnk the sky is falling down again....

IMX,

Yes. We have a great solution for affiliate programs. Contact me on icq if you want more details.

i need your icq :)

IMX,

Sorry about that. I thought it was in my profile :).

ICQ# 51130723

notjoe - your the dumbfuck who needs to get a clue. I always do a traceroute and check traffic stats to make sure the problem is with the host and not my ISP.
Most people do this. What was your point anyways?

I believe his point was rather simple, you provided no information to backup your point. Additionally everyone else who posted seems to be getting great ping times / # of hops to Like Whoa, and more importantly its actually been up very stable without a problem since the fiasco last week.

As far as connectivity is concerned they seem in better shape as they added AboveNet/MFN last week. If your sites are loading slowly and your seeing less than 100ms ping time from your house, it's most likely your server's Apache configuration, a capped megabit plan or something to that extent, not their network. Judging from everyone else's post and seeing as how I do not have any sites hosted with them, but likewhoa.com loads mighty fast for me, I'd say they are back on track.

My suggestion is to contact their tech support and make sure your server is upto speed before blaming it on a seemingly non-existant network problem.

Ummm ... this is GFY, you know ...