Page 2 of 2 FirstFirst 12
Results 26 to 45 of 45
  1. #26
    Join Date
    Jan 2004
    Location
    North Yorkshire, UK
    Posts
    4,164
    Code:
    H:\>tracert www.server4you.com
    
    Tracing route to www.server4you.com [69.64.44.43]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     1 ms  fe-1-0.dis3.dur.uk.razorblue.com [82.163.175.81]
    
      2     4 ms     3 ms     3 ms  fe-0-1.agg1.dur.uk.razorblue.com [82.163.169.99]
    
      3    28 ms    28 ms    27 ms  ge-1-0.cr2.man.uk.razorblue.com [213.130.145.4
    9]
      4    28 ms    27 ms    28 ms  213.130.145.126
      5    34 ms    35 ms    35 ms  213.130.138.65
      6    34 ms    35 ms    43 ms  ldn-b1-geth11-0-13.telia.net [213.248.75.65]
      7    35 ms    34 ms    34 ms  ldn-bb2-pos0-2-0.telia.net [213.248.64.93]
      8   103 ms   104 ms   102 ms  nyk-bb2-pos7-0-0.telia.net [213.248.65.210]
      9   102 ms   103 ms   102 ms  nyk-b1-link.telia.net [213.248.80.66]
     10   104 ms   103 ms   104 ms  so-9-1.car1.newyork1.level3.net [209.244.160.161
    ]
     11   107 ms   107 ms   108 ms  ae-1-52.bbr2.newyork1.level3.net [4.68.97.33]
     12   129 ms   128 ms   133 ms  so-3-0-0.mp1.stlouis1.level3.net [64.159.0.49]
     13   129 ms   129 ms   129 ms  ge-9-0.hsa1.stlouis1.level3.net [64.159.0.62]
     14   129 ms   128 ms   130 ms  server4you-gw.stl1.us.inetbone.net [63.208.32.16
    2]
     15     *        *        *     Request timed out.
     16     *        *        *     Request timed out.
    Doesn't look brilliant ...
      0 Not allowed!

  2. #27
    Join Date
    Mar 2003
    Posts
    1,584
    ditto

    "this should be in the providers downtime forum, not dedicated servers... mods?"

    kinda makes me think that the mods are slow to move non-paying or less paying advertisment companies.
      0 Not allowed!

  3. #28
      0 Not allowed!

  4. #29
    indeed :/ they werent down for long though
      0 Not allowed!

  5. #30
    And they are down AGAIN today.

    Ping to server4you.com

    Generated by www.DNSstuff.com at 19:56:44 GMT on 13 Dec 2005.


    Pinging server4you.com [69.64.44.43]:

    Ping #1: * [No response]
    Ping #2: * [No response]
    Ping #3: * [No response]
    Ping #4: * [No response]

    Done pinging server4you.com!

    (to do an IPv6 ping for a domain name, add a ':' before the domain name)
      0 Not allowed!

  6. #31
    This is becoming beyond a joke!
      0 Not allowed!

  7. #32
    It seems server4you has important problems. No answer for tickets, No answer for e-mails, no telephone for something else than sales. They told one of my VPS has been hacked on November 2005, since that date the service became worse and worse. They say things they cannot prove or they do not want to. I am still waiting answers.
      0 Not allowed!

  8. #33

    What i was told today

    Hi All

    i too host on server4you and have been happy up to now. i started an online chat with sales and asked what was going on, i was told that according to their EULA that i was responsible for backing up and restoring my sites. I know this but it wasnt what i asked, i wanted to know why all my sites were down. This person then responded "didnt i read my email" after saying what are you talking about, the person responded with a cut and paste of a suppose email that should have went out to subscribers. It says that they have had a major hardware failure and accounts and sites maybe lost and they are trying to rebuild and it might be a few days before things are back. apparently they are moving the people affected to a new "raid server" one would have thought it was already on one.

    The person i talked to was not very friendly and does anyone have any recomendations of other hosting companies.

    Thanks

    Kevin
      0 Not allowed!

  9. #34
    Well just to chime in here... I host mine and about 40 clients with server4you.... they have all been down for an entire week now.

    I find it inadequate that they think they can send and email to you...which in my case goes through the same servers that are...uh...no worky. And then treat you crappily when you ask what the ETA of repair is.

    I got the "you should have a back up we are not responsible" gambit from some b*** technician as well. I didn't ask when my stuff would be up...I could care less if the sites are there at this point...I have the backups ready...but it's hard to upload a site when the server is not available.

    I better start shopping around.... especially since I think it is going to be heck to get any hosting fees recouped from this.
      0 Not allowed!

  10. #35

    Great Support

    Dear Sir/Madam
    We regret deeply to inform you that one of our vps servers hosting several of our virtual private accounts suffered a catastrophic hard drive failure late friday, December 16. We are currently working to recover as much data as possible, but feel we must prepare those affected for the worst possibility: some accounts may be a complete loss for the next several days until we are able to rebuild those accounts on a new raid. We request your patience as we continue this laborious effort. We request that you please refrain from tying down tech support with inquiries, since it will be prohibitavly difficult to assess the status on a specific VE and will only divert our tech support staff's time away from the task of rebuilding. Thank you for your understanding as we continue the work necessary to rebuild these accounts.

    this is the actual replay from tech support from a ticket i was able to create today.
    Glad they care about their customers NOT!!!

    Kevin
      0 Not allowed!

  11. #36
    Ugly. You should probably look for a host who backs up their shared servers. I know that Verio does this. If a machine is backed up, even the worst recovery should only require a few hours.

    Seeing that S4Y doesn’t backup their machines, they should at least be able to direct you to a new server for you to use while they work to restore data from the old.

    Sorry to hear the stories of woe.
      0 Not allowed!

  12. #37
    Once again, the entire server4you network is down tonight. The fun just never ends with serever4you.com.

    Ping to server4you.com
    Generated by www.DNSstuff.com at 03:44:45 GMT on 29 Dec 2005.

    Pinging server4you.com [69.64.44.43]:

    Ping #1: * [No response]
    Ping #2: * [No response]
    Ping #3: * [No response]
    Ping #4: * [No response]

    Done pinging server4you.com!

    (to do an IPv6 ping for a domain name, add a ':' before the domain name)
      0 Not allowed!

  13. #38
    Join Date
    Sep 2003
    Location
    Washington, USA
    Posts
    3,262
    Quote Originally Posted by bdmcnitt
    Once again, the entire server4you network is down tonight. The fun just never ends with serever4you.com.

    Ping to server4you.com
    Generated by www.DNSstuff.com at 03:44:45 GMT on 29 Dec 2005.

    Pinging server4you.com [69.64.44.43]:

    Ping #1: * [No response]
    Ping #2: * [No response]
    Ping #3: * [No response]
    Ping #4: * [No response]

    Done pinging server4you.com!

    (to do an IPv6 ping for a domain name, add a ':' before the domain name)
    Website loads fine for me, I don't think server4you.com will reply to any ping requests.
      0 Not allowed!

  14. #39
    Join Date
    Jun 2004
    Posts
    2,853
    Loaded fine too.
      0 Not allowed!

  15. #40
    Join Date
    Dec 2005
    Location
    Lawrenceville GA
    Posts
    54

    Same verse same as the first

    New here but as I am experiencing the same issues with Server 4 You I thought I'd share my experience. I lease a Power dedicated for application serving. No http web services.
    I have been with S4Y for nearly 2 years. Up until recently all I had to say was top notch. I know people paying 3x as much for crappier service. Support tickets prompty responded too as well as a decent amount of technical excellence. In short they knew there stuff and were well well worth it.
    Then comes November. Not sure when but the server would experience latency spikes and complete losses of connectivity. The first support ticket explaind it as a DDoS attack at a switch that was taken care of. But it didnt stop there. First only one or two times a day same above described symptoms for 10 minutes. I decided to wait a few days as DDoS'ers unless it's coordinated have a low attention span. Two weeks later same thing. Except now the spikes occurr durring my servers prime time. I file another support ticket and get roughly the same answer shaken up a bit. All through the month of November this continues and I file a total of 5 support tickets. All with the same quip responses from some ignorant chick on the night shift. These have moved from segmented network outages to complete outages at the S4Y datacenter in St Louis. By December I am begining to grow tired of this. At the same time Im trying to be patient with a company thats given me a good solid year of service with not one real complaint on my part. At this time a call to Level 3 is in order for me to see what there response is to how they deal with DDoS as they are the primary upstream provider for S4Y. As expected I got the usual Tier 2 NOC escalation procedure that I have seen with Saavis, UUNet,MCI etc etc. This seems like then a problem they should be moving up the ladder and have blocked by Level 3.
    The outages continue. Durration is always about 10-20 minutes. Times are pretty much the same nightly. To me it sounds like a spammer running a cronjob at a preset time. However one thing comes up EVERYTIME on every outage

    server4you-gw.stl1.us.inetbone.net (63.208.32.162) 361.854 ms 361.072 ms

    Everytime theres a outage this sucker pops up as the broken link. I verified this by doing a traceroute from and to the server durring a event. I had traceroute set to go off when it lost connectivity to my Virginia server for more then 3 minutes.
    So great we have a culprit. I give this information in a support ticket and think ok this is cool cause theres a point of failure that can be examined. Pings inside the network durring a outage are fine meaning it's the switch getting bombed.

    Low and behold I get this chick again with some absolutely dismissive answer saying she's unplugged a machine to deal with the problem and everything in umpa loompa land should be happy. Apparently she didnt test her theory cause the network was down as she wrote the reply.

    I snapped. I have decided to post the ticket here. I have edited my language because it was unprofesional, rum induced and to be honest more for my benefit of venting before I dump this crappy provider who has fallen from a very high performance standard they had set with me previously. This is ticket #22 relating to this issue.

    Done: 2005-12-29 21:56:51
    Category: Technical Support
    Contact: RTS Problem
    Description: Another attack. See last night's ticket because it's about the same as this one
    Error Message: see above
    Author Message

    RTS 2005-12-29 21:59:35 Have you thought about just blocking the offending addresses with a limiting script on a firewal box. It's not hard to do. Or better yet put it to your upstream provider. Any serious NOC will block DDoS attacks.

    RTS 2005-12-29 22:02:58 Can you move me to a different switch to avoid this or something. I really can't put up with this any longer and have to think about moving the server. Your service has really deteriorated in the last 2 months to a point it's virtually unusable for high availability hosting.

    Anna R 2005-12-29 22:41:05 Dear customer, The question about movng you to a different switch will be sent to our network administrator. Right now I have disconnected one server from your switch to prevent following DoS-attacks. Please don´t hesitate to contact us for any further questions or problems. Our Support Team will be happy to assist you.

    RTS 2005-12-29 23:56:39 Well its been up and down since I posted the last message. Maybe you should stop disconnecting servers and FIND OUT THE XXXXXXXXXXXX PROBLEM. It's not difficult work. Google network security, DDoS iptables and Level 3's NOC escalation. This isnt rocket science and you people apear incompetent of late. Apparently if you google server4you most the links are about how the service has gone to the crapper last 2 months. You all are into me for a considerable amount of money if I have to move my server because of ths crap.

    RTS 2005-12-30 00:10:27 down and up. You peple need to seriously hire competent NOC staff. Any CNA or CNE wouldve had the trouble mopped up in under 12 man hours and a documented handling procedure in place.

    Anna R 2005-12-30 01:35:10 Dear Sir, Thank you much for your attention to the concerned request. Please be kindly informed that S4Y technical department does the best of it to help and support all incoming questions and inquiries, including ones, regarding recent DDoS attack. I would like to inform you that though S4Y offers unmanaged servers and the security of a server is up to the customer, we are willing and ready to support you in case of such problems, like DDoS. Unfortunately in the last 2 weeks the level of incoming DDoS attacks has increased and despite all our efforts to block them it may happen a specific server to suffer its consequesces. Considering this, please be kindly informed that technical department is working on this problem and together with our main network administrator, we are doing our best to resolve the DDoS problem in the shortest possible time. Really only our main administrator can solve the questions about global network policy and firewalls on switches. He is available during the business days working hours.

    RTS 2005-12-30 10:02:07 This DDoS attack isnt my problem you idiot. It's your network being attacked not my server. How come this problem cropped up in the last 2 months and before was a non-existent. Before when a complaint about a network issue was filed it was resolved within 24 hours. For the last 2 months however the quality of techinical support relating to YOUR network has dropped to a nearly non-existent. Please cmon. Your answer is unplugging server as stated above? Some answer. I think thats like what a fourth grader would do when faced with this situation. Someone technically saavy would sniff the network and either blacklist the offending networks at the switch.

    Quoting you I would like to inform you that though S4Y offers unmanaged servers and the security of a server is up to the customer, we are willing and ready to support you in case of such problems, like DDoS.

    Dont you ever, EVER try to pass your problems off to me you incompetent turd. My server is secure. Your network isn't you XXXXXXXXXXXX. Do you know what XXXXXXXXXXXX customer support is? It's when some XXXXXXXXXXXX vendor blames the problems on the customer. Not only is this problem unrelated to me other then the symptoms but it's network wide. How the XXXXXXXXXXXX is that my issue your helping me with you awful jackass. If my language seems terse it's because I have put up with Technicians like this Anna R with her short nonsensical answers and no real solutions. Do you need links to the nearly 200+ blog and forums I found thru google with YOUR customers with the exact same complaint as mine? Do you not realize that the next phase is your customer base will be eroding as now when you google server4you you get your page and a series of pages with complaints about your service going to the crapper? Youve lost dozens of customers from this issue. You have cost me hundreds if not thousands of dollars with this issue. Fire the retards and get yourself qualified NOC techs.

    RTS 2005-12-30 10:06:30 Quote from above Really only our main administrator can solve the questions about global network policy and firewalls on switches. He is available during the business days working hours. I think thats the guy who needs fired. Maybe he needs a pager or better yet a book on networking for dummies.

    So in a nutshell I'm looking at Server Central and trying to turn this from a problem to a opportunity by expanding the server quality I provide to my customers. However as far as Server4You goes they used to be decent for dedicated servers. I could see how they could be lacking in VPS or Webhosting. But dedicated white boxes they honestly used to be about as good as anyone out there for the best price. The only thing that comes to me is theyve picked up some new staff that really does not know there craft.
    Last edited by rts2271; 12-30-2005 at 12:56 PM.
      0 Not allowed!

  16. #41
    Join Date
    Nov 2005
    Location
    New York City
    Posts
    250
    I didn't read your whole essay there but i skimmed through it to see you have cursed them. That's not a good idea. No matter how much it's thier fault and they have ****ty support. As once you start cursing them, things won't get better.
      0 Not allowed!

  17. #42
    Join Date
    Jun 2004
    Posts
    2,853
    Quote Originally Posted by Hagane
    I didn't read your whole essay there but i skimmed through it to see you have cursed them. That's not a good idea. No matter how much it's thier fault and they have ****ty support. As once you start cursing them, things won't get better.

    I have edited my language because it was unprofesional, rum induced and to be honest more for my benefit of venting before I dump this crappy provider who has fallen from a very high performance standard they had set with me previously. This is ticket #22 relating to this issue.

    That's what he said.

    He knows it's not a good idea.
      0 Not allowed!

  18. #43
    Problems still are the same. Yesterday, more than 5 times offline / server down. I have requested refund.
      0 Not allowed!

  19. #44
    And again.

    Tracert to 69.64.32.146

    Generated by www.DNSstuff.com at 16:10:00 GMT on 19 Jun 2006.

    Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
    1 1 0 2 0.5 ms

    66.36.240.2 AS14361
    HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unknown: 819d1c36
    2 0 0 0 0.5 ms [+0ms]

    66.36.224.232 AS0
    IANA-RSVD-0 gec2.core1.dca2.hopone.net. 0 miles [+0] 254 US Unix: 17:10:01.761
    3 2 1 1 1.3 ms [+0ms]

    66.36.224.189 AS0
    IANA-RSVD-0 ge-4-2-125.car2.washington1.level3.net. 0 miles [+0] 253 US Unix: 16:10:02.251
    4 1 1 3 1.5 ms [+0ms]

    4.68.121.161 AS3356
    Level3 ae-2-56.bbr2.washington1.level3.net. 0 miles [+0] 251 US Unix: 16:10:02.302
    5 23 22 22 22 ms [+21ms]

    64.159.0.49 AS3356
    Level3 so-3-0-0.mp1.stlouis1.level3.net. 0 miles [+0] 247 US Unix: 16:10:02.355
    6 35 41 27 22 ms [+0ms]

    64.159.4.142 AS3356
    Level3 ge-7-2.hsa1.stlouis1.level3.net. 0 miles [+0] 248 US Unix: 16:10:02.437
    7 35 23 22 22 ms [+0ms]

    63.208.32.162 AS3356
    Level3 server4you-gw.stl1.us.inetbone.net. 0 miles [+0] 248 US [Router did not respond]
    8 * * * 99999 ms [+99999ms]

    [Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
    9 * * * 99999 ms [+0ms]

    [Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
    10 * * * 99999 ms [+0ms]

    [Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
    11 * * * 99999 ms [+0ms]

    [Unknown] [Unknown - Firewall did not respond]
    [4 hops with no response:
    assuming we hit a firewall
    that blocks pings] 0 miles [+0]
    12
    13
    14
    15

    Analysis:
    Number of hops: 11
    Last hop responding to ICMP: 7, UDP: 7, TCP: 7.
    There appears to be a firewall right after 63.208.32.162 (hop 7) that blocks ICMP, unwanted UDP, and unwanted TCP packets.

    Legend:
    T1/T2/T3 are the round-trip times in milliseconds (1/1000ths of a second).
    T1 uses a proper ICMP-based tracert (Microsoft style). T2 uses a UDP-based traceroute (Unix-style). T3 uses a TCP-based traceroute (port 80).
    Since many ISPs now block ICMP and/or packets to unknown ports, T3 (not used by many traceroute programs) typically shows the best results.
    Best times may be theoretical (if it takes 80ms to hop 10, and 50ms to hop 11, we say the best time for hop 10 is 50ms).
    If no reverse DNS entry is given for an IP, we display 'unknown.example.com' if the domain name is known.
      0 Not allowed!

  20. #45
    Join Date
    Oct 2004
    Location
    San Francisco, CA
    Posts
    2,455
    New outages are best for a new thread

    Thread closed.
      0 Not allowed!

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •