Tamaranda.com is DOWN

We'll it's about a month to go since I posted. We tried Tamranda.com and know what? Check my sigs, we are down for more than an hour now without any notice again whatsoever.

Still never found a good host. A good host with reasonable prices, reasonable uptime and reasonable support. It's a shame moving from host to host. Now we are trying a dedicated server from surfspeedy.com, this will be the last try, I think. If this will also fail like the other, we have no choice but to build our very own servers.

yes right Tamaranda.com is DOWN
my god...what happend with Tamaranda.com ?!!

I think Tamranda.com is a dedicated server only, just my calculations.
Though they claim that their servers are in Florida.

We are now down for two hours. Oh, my valued users...we are very sorry about this. :deeply bows:

Recovery Alert

Your website is no longer on error
URL: http://xxxx.xxx
Time: 2006-07-21 15:51:40
Time on Error: 06 hours 00 minutes 53 seconds

About This Message: This message was generated by FreeWebMonitoring.com. Your website error has been resolved.


6 hour DOWN

Hello,

http://www.finetraders.org is now back to normal.

Operation restored at 2006-07-21 18:40:59.

Url was down as a resultat of:

Http error:Http_client.No_reply

Error was detected at 2006-07-21 12:01:12

Downtime total 6 hour(s) 39 min(s) 47 sec(s).

Check failures total: 15.


--
Best regards,
http://host-tracker.com/ support team

Er..are you referring to Tamranda or Tamaranda?

Er..are you referring to Tamranda or Tamaranda?

Typos.
It must be Tamranda.

We'll it's about a month to go since I posted. We tried Tamranda.com and know what? Check my sigs, we are down for more than an hour now without any notice again whatsoever.

Still never found a good host. A good host with reasonable prices, reasonable uptime and reasonable support. It's a shame moving from host to host. Now we are trying a dedicated server from surfspeedy.com, this will be the last try, I think. If this will also fail like the other, we have no choice but to build our very own servers.

Dayu,

We are sorry for the experience which you had with us.

It is very rare that one gets such a downtime with us. I can assure you that this wont happen again.

If you like, I can offer you another month of hosting for free & Im quite sure you'll get back to this thread only posting something positive about us.

Again, Im sorry for the inconvenience.

Dayu,

We are sorry for the experience which you had with us.

It is very rare that one gets such a downtime with us. I can assure you that this wont happen again.

If you like, I can offer you another month of hosting for free & Im quite sure you'll get back to this thread only posting something positive about us.

Again, Im sorry for the inconvenience.

May we please know what caused the rare downtime?

Also, thanks for the offer. We are glad to hear that from you as a sign of apology. And we are willing to offer that to our members as a sign of our apology too for them.

Either which, we have already signed for a new dedicated server and shall try our luck on them. We shall not force our members who have accounts in Tamranda to transfer. We shall let them give you a fair chance and experience your service for another month.

May we please know what caused the rare downtime?

Also, thanks for the offer. We are glad to hear that from you as a sign of apology. And we are willing to offer that to our members as a sign of our apology too for them.

Either which, we have already signed for a new dedicated server and shall try our luck on them. We shall not force our members who have accounts in Tamranda to transfer. We shall let them give you a fair chance and experience your service for another month.

This downtime was caused due to apache & a few other softwares getting corrupt, & reinstalling them all is basically which took the time. We have had such a long downtime after atleast 11-12 months.

I thank you for your co-operation & not moving your members.

You guys dont make daily backups?

You guys dont make daily backups?

What has this got to do with apache corruption? Red Hat E3 had a bad apache update during the night

You guys dont make daily backups?
We do weekly backups but as duport said, it has nothing to do with the problem

Can do all of the backups in the world, doesn't fix apache and it's configs much faster :P

yes...its up again.... hope it wont happend again

down again....:shame: :shame:

down again....:shame: :shame:

Our Customers have been notified about it.

Our main server is facing a distributed forged packet attack, so we have currently null routed the main IP of the server & are null routing the IPs which are causing the attack.

The server is up & one can confirm that by logining into there respective accounts using the other IP of the Server 207.150.164.71

Thx For your Info....

Our Customers have been notified about it.



We are not receiving any such information.
Or have you forgotten us as one of your costumers?
Click on my sig to know how many times you're letting us down.

Click on my sig to know how many times you're letting us down.

Im sorry for the problems this has cased you but please understand that this is not a server related issue. The server is unreachable on the Main IP because someone has initiated a distributed forged packet attack on our server. The server is still accessible via the Secondary IP.

We had no option other then null routing our main IP. We are working on banning the IPs which are sending the packets.

Im sorry for the problems this has cased you but please understand that this is not a server related issue. The server is unreachable on the Main IP because someone has initiated a distributed forged packet attack on our server. The server is still accessible via the Secondary IP.

We had no option other then null routing our main IP. We are working on banning the IPs which are sending the packets.

One of our domain that is pointed to your very server ns1.Tamranda.com, ns2.Tamranda.com must be working then.
Click on that domain, http://i7s.net/english , does it work?
Any other excuses, the one that at least appears to be true?

One of our domain that is pointed to your very server ns1.Tamranda.com, ns2.Tamranda.com must be working then.
Click on that domain, http://i7s.net/english , does it work?
Any other excuses, the one that at least appears to be true?

None of the websites hosted on the server will work until the main IP on which HTTPD enteries are made works.

You can login into your WHM & cpanel here :: http://207.150.164.71/cpanel or http://207.150.164.71/whm which i think is enough to prove that the server is absolutely fine.

None of the websites hosted on the server will work until the main IP on which HTTPD enteries are made works.

You can login into your WHM & cpanel here :: http://207.150.164.71/cpanel or http://207.150.164.71/whm which i think is enough to prove that the server is absolutely fine.

And for what good is it if we can't access our pages and you keeping us down?

yes i already try and it work fine

Thx

yes i already try and it work fine

Thx

We are not paying for the pages of Tamranda just like the one in your sigs to become fine.
We are paying for our pages to be fine and become alive in the internet.
And we are paying for nothing if we are down, can't you understand?

Do you guys have a money back?

how bout you..?

Well I feel like I want my money back and a compensation for the damages that it keeps on inflicting on us.

We are not paying for the pages of Tamranda just like the one in your sigs to become fine.
We are paying for our pages to be fine and become alive in the internet.
And we are paying for nothing if we are down, can't you understand?

Please be Calm. We are doing nothing other then working on the issue.

Please keep in mind that the DOS attack has not originated because of our Fault & we have no control over such attacks. All that can be done it null routing the IPs causing it.

The server is working now & all the IPs involved in the attack have been null routed.

Once again, I apologize for the downtime.

Please be Calm. We are doing nothing other then working on the issue.


Calm? How can you be calm in more than 14 hrs downtime? Is this your fastest response to threats against your servers? Is that the level of your support?





Hello,

http://www.finetraders.org is now back to normal.

Operation restored at 2006-07-25 05:19:07.

Url was down as a resultat of:

Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)")

Error was detected at 2006-07-24 14:39:38

Downtime total 14 hour(s) 39 min(s) 29 sec(s).

Check failures total: 15.

--
Best regards,
http://host-tracker.com/ support team

The server is working now & all the IPs involved in the attack have been null routed.

Once again, I apologize for the downtime.

It took you more than 14 hrs to do that?

Calm? How can you be calm in more than 14 hrs downtime? Is this your fastest response to threats against your servers? Is that the level of your support?

I belive you have no idea what a Distributed Denial of Service attack is.

Our response started with 10 minutes after the attack started. 14 hours was the time taken to fully resolve the issue. Please keep in my that a third party ie the datacenter was also involved in the issue.

In my view, 14 hours was a short time to resolve such an issue. Just to let you know, in many cases it even takes weeks to fully resolve such issues & identify the sender of forged packets.

Even companies like google have faced such problem on even LARGER scale & it was not due to our fault that this attack originated.

I belive you have no idea what a Distributed Denial of Service attack is.

Our response started with 10 minutes after the attack started. 14 hours was the time taken to fully resolve the issue. Please keep in my that a third party ie the datacenter was also involved in the issue.

In my view, 14 hours was a short time to resolve such an issue. Just to let you know, in many cases it even takes weeks to fully resolve such issues & identify the sender of forged packets.

Even companies like google have faced such problem on even LARGER scale & it was not due to our fault that this attack originated.

Are you going to convince me with your beliefs just like when you said,
0 means Unlimited in cPanel. Im sorry but thats how cpanel works.
It cannot be changed to show */Unlimited instead of */0.

More than a year in business and you haven't anticipated things like that?

Short time response to corrupt apache: 6 hrs 39 mins DOWNTIME.
Short time response to DDoS attack: 14 hrs 39 mins DOWNTIME.

How's that for one week? Not to mention your everyday downtime glitches: 1min-60mins downtime, 2-5times a day.

And you're telling a costumer who paid you for 99.8% uptime to be calm?

r you angry dayu..?!

Short time response to corrupt apache: 6 hrs 39 mins DOWNTIME.

Short time response to DDoS attack: 14 hrs 39 mins DOWNTIME.

How's that for one week? Not to mention your everyday downtime glitches: 1min-60mins downtime, 2-5times a day.

And you're telling a costumer who paid you for 99.8% uptime to be calm?

1. If you noticed in my previous replies, Apache was not the only thing which got corrupt. There were some other softwares aswell. Once installations were done, we also had to check EACH and EVERY software & account on the server to insure everything is fine & it does take time.

2. Regarding the DOS attack, yes you can consider that our respose time is 14 hours & I feel it was good if not fast. MIND you that the server was accesible on secondary IPs. Just to let you know, Datacenters are very strict regarding such issues & in many cases, they would null route the destination IP of DOS attack for 24 hours Straight.

One more thing, the server did become irresponsive 2-3 times a day, a couple of days before the real big DOS attack. This was because some small scale attacks were launched at that time but they were not distributed, hence our technical team nulled them with 30 minutes of occurence.

Im very sorry for all this but i would like to remind you again that we have NO control over such dDOS Attacks & it was not our fault that it originated.

i would like to remind you again that we have NO control over such dDOS Attacks & it was not our fault that it originated.

Never did I mentioned that you take control of any DDoS attack. I keep on asking your anticipation about such attacks and your time to respond. Or shall I start lecturing you about what are the softwares other techniques to prevent such attacks?

MIND you that the server was accesible on secondary IPs.

Let me remind you again that we are not paying for your pages to be accessible. We are paying for OUR pages to be accessible. Is that too hard to understand?

I keep on asking your anticipation about such attacks and your time to respond. Or shall I start lecturing you about what are the softwares other techniques to prevent such attacks?
We do anticipate such attacks & had proper firewall rules to block such attacks BUT the attack was so huge that the speed at which new connections were made was far more greater then the speed at which the server blocked those IPs itself. In such situations, even the best softwares can't do anything. I belive this would clear most things up :)


Let me remind you again that we are not paying for your pages to be accessible. We are paying for OUR pages to be accessible. Is that too hard to understand?
I never said that your sites were accessible since if it had been so, it wouldn't had been a downtime :). All im saying is that the server was accessible on the secondary IP which could have been used to access WHM, Cpanel, webmail & all such applications.

Never did I mentioned that you take control of any DDoS attack. I keep on asking your anticipation about such attacks and your time to respond. Or shall I start lecturing you about what are the softwares other techniques to prevent such attacks?


There is nothing you can do to anticipate a DDOS attack. No firewall is designed to handle DDOS attacks.

A serious DDOS attack will saturate your uplink making the entire network unavailable. We've have around 2 attacks each year, although we are normally able to get things up and running within 30 to 45 minutes.

Our worst DDOS attack had 100s of attacking ips and pushed network usage above 300mbps, which triggered a network cut-off from our tier-1 supplier InterNap (to save us from being billed). We had to go through router logs and ask our tier-1 to block major offending IPs, took about 1 hour in total before we had our network up and functional (but attack continued). Took another 2 hours to have every single IP blocked.

So depending on how major the attack tamranda faced, it could take a few hours to resolve. I am suspecting it took longer because a 3rd party handles it for them (a server provider) and server providers usually are much slower and prefer to take the quick option of null routing the destination IP and then taking their own sweet time to resolve the issue.

Of course, tamranda is responsible for the end hosting product to their customers. But typically such issues are not due to inaction by the shared host, but inaction or slow action by the server provider.

There is nothing you can do to anticipate a DDOS attack. No firewall is designed to handle DDOS attacks.

Actully, one of my Server admin has setup a rule on the server which Blocks an IP using APF which tries to open Too many connections to the server. It does work in small scale cases which are triggered by a few IPs but in a Distributed Attack as the one which we faced had 100s of IPs which caused it.

Moreover, the IPs kept changing in intervals of time which was the MAJOR reason for the downtime. Otherwise our server would have started working within 2 hours. Once Each set of IPs were banned, the attack originated from a new Set of IPs.

Our Datacenter also prefers to check the sniffer logs in detail before placing any null route for any IP which causes an addition of time.

Of course, I wouldn't consider that a DDOS though :)
A typical firewall would be out cold during a DDOS attack. We've had our CISCO routers that are capable of handling 1gbps go out cold during a DDOS attack due to the high PPS rate.

The only decent anti DDOS shield I've seen is manufactured by CISCO and costs around $100,000. it can truly handle massive attacks and block IPs. But installing a shield is useless unless your network could handle it.. normally it would saturate.. either the uplink or the routers due to the pps rate

We do anticipate such attacks & had proper firewall rules to block such attacks BUT the attack was so huge that the speed at which new connections were made was far more greater then the speed at which the server blocked those IPs itself. In such situations, even the best softwares can't do anything. I belive this would clear most things up :)

Yes, now it's very clear how poor your facilities and performance are.
With all the anticipation and proper firewalls, and with every small DDoS attacks everyday that you claims causes your server to have 1min-60mins downtime glitches, 2-5 times a day, still it will take more than 14hrs of downtime for you to solve rather huge DDoS attacks. Man, you can be sure I won't recommend any such lame performance.



I never said that your sites were accessible since if it had been so, it wouldn't had been a downtime :). All im saying is that the server was accessible on the secondary IP which could have been used to access WHM, Cpanel, webmail & all such applications.

Oh, now it is safe for me to conclude that you have never considered the stance of your costumer at all. Now I am pretty sure you are one of those who after buying some gadgets and learned how to tweak a little, greatly proclaims with himself, hey...I have a business. Well if you're offering that hostings for free, it ain't posing any problems, you are great. But when you talk about paid hosting, it must be different, you have to put all your efforts and considerations to the costumer who is paying you for your job.

Don't you realize that there is no sense in bragging to your costumer that your servers are accessible when their pages to which they are paying for are non-accessible which means they are paying for nothing other than braggs from their host. Let me tell you that costumers, especially those who don't know the jargons and everything about servers, are not really interested about the hosts excuses for their downtime. They are paying for their uptime and if you can't provide them, fine.. will be looking for someone who can.

What's worst is that you are bragging that to a costumer whom after you have caused to suffer more than 6hrs of downtime (because of your corrupted softwares), the next few days you made to suffer more than 14hrs more of downtime (for your poor facilities and performance against DDoS attacks). Remember, the same costumer who is already getting pissed off by your 1min-60min downtime glitches that happens 2-5 times everyday.

It's fair, I have given you enough chance to explain and express yourself.
Now it's clear that you've started your business without thinking any of these.

We'll still accept your one month free offer, though you can be sure we will not last in your server for another month more. Maybe two weeks are enough for us to evacuate to our newly bought dedicated server. After that, you can be sure we won't be back in your lame servers again, nor can you expect any recommendations for your lame performance and unwitty business practices.

You should really take this to email. As the mods have stated in other areas, this is not a support forum or a place to resolve your disputes. Provide the review and move on.

You should really take this to email. As the mods have stated in other areas, this is not a support forum or a place to resolve your disputes. Provide the review and move on.

This wasn't supposed to be talking about disputes nor reviews at all.
It was just how things turned out because of not smart responses from the host. If you can see my previous posts, I have not intended things to turn out this way.

Yes, now it's very clear how poor your facilities and performance are.
With all the anticipation and proper firewalls, and with every small DDoS attacks everyday that you claims causes your server to have 1min-60mins downtime glitches, 2-5 times a day, still it will take more than 14hrs of downtime for you to solve rather huge DDoS attacks. Man, you can be sure I won't recommend any such lame performance.
I dont know whats your problem but you are arn't getting what I mean. As JodoHost specified above, there is no proper firewall to handel such dDos Attacks & I never said that we get dDos Attacks daily, all i said was that we got a small DOS attack a couple of days before the Big dDOS.

Yes, it took us 14 Hours as I had said above, im rather happy that it took 14 Hours since it much more a complicated issue then you can imagine.


Don't you realize that there is no sense in bragging to your costumer that your servers are accessible when their pages to which they are paying for are non-accessible which means they are paying for nothing other than braggs from their host. Let me tell you that costumers, especially those who don't know the jargons and everything about servers, are not really interested about the hosts excuses for their downtime. They are paying for their uptime and if you can't provide them, fine.. will be looking for someone who can.
I do realize that & I apolozie but we could have done nothing to avoid the DOS attack.


What's worst is that you are bragging that to a costumer whom after you have caused to suffer more than 6hrs of downtime (because of your corrupted softwares), the next few days you made to suffer more than 14hrs more of downtime (for your poor facilities and performance against DDoS attacks). Remember, the same costumer who is already getting pissed off by your 1min-60min downtime glitches that happens 2-5 times everyday.
Im not bragging you. Im only trying to tell you that we had always tried to get this DOS issues sorted out as soon as possible, but the conditions were so complex that it took 14 hours. We care for our customers & thats why we took the time to inform everyone about the Secondary IP, even if it is of little help to the customer. Some clients might have needed urgent access to there files & thats the reason why we gave them links to Secondary IPs.

Please PM me the logs where you see 2-5 downtimes every day.