Blazer Network Sucks
During the summer of 2005 I was told about a pretty good web host that was cheaper than what I currently used. It supported .NET and offered a lot of features at a good price. Support was fairly responsive, though not many features were automated (such as upgrading to .NET 2.0).
Things were pretty good for a time. Then Memorial Day weekend hit and Blazer Network went out in a blaze of glory.
It started with what can only be described as a catastrophic failure. My sites went down. The control panel went down. Blazer's website went down. Blazer's website went down? Amazing, their site never went down, even when their servers were down.
After three days of being down, I gave a call to their support line. Nothing, just a message saying all support representatives were busy. That remained constant for a few days.
Later that week my sites start working intermittently. Email still didn’t work.
About ten days after ‘the incident’ the voicemail changed to a message saying a few things. First, there was a failure (duh). Second, a new support team was in place. Third, there were a lot of problems left from the old support team (sabotage?). They still didn’t answer, but they let you leave messages. I did this everyday.
Over the next few days things still sucked. I tried to change my domain supplier, but my domain was locked and I couldn’t log in to edit it. More phone messages.
A little over 2 weeks after Blazer blew up the site seemed a bit more stable. The control panel was accessible, though it wasn’t 100% functioning. MSSQL management was one thing not available. I was still unable to unlock my domain. My domain was expiring June 24, time was running out. Incidentally, I could have renewed my domain if I wanted; they still were allowing new business.
About June 19 Blazer started answering their phone. Support was slow, but they informed me I was able to change my domain registration information by email, which I did. My domain transferred June 23, one day before it expired.
Technical issues were ironed out slowly now that they were answering the phone, but they weren’t offering refunds for downtime or explanations. MSSQL was working but not accessible to log in and edit data or get a copy of my stored procedures.
The July Fourth holiday weekend brought some strange doings. At home I couldn’t access my sites that hadn’t been moved to a new host. I could at work, but still couldn’t get in to the SQL server to get my data.
Finally on July 10 I could. At this point MSSQL still didn’t work, but thankfully it didn’t matter anymore.
Blazer Network completely lost their credibility as a web host. If you see this and have had a similar experience, let me know with a link and a comment.
Things were pretty good for a time. Then Memorial Day weekend hit and Blazer Network went out in a blaze of glory.
It started with what can only be described as a catastrophic failure. My sites went down. The control panel went down. Blazer's website went down. Blazer's website went down? Amazing, their site never went down, even when their servers were down.
After three days of being down, I gave a call to their support line. Nothing, just a message saying all support representatives were busy. That remained constant for a few days.
Later that week my sites start working intermittently. Email still didn’t work.
About ten days after ‘the incident’ the voicemail changed to a message saying a few things. First, there was a failure (duh). Second, a new support team was in place. Third, there were a lot of problems left from the old support team (sabotage?). They still didn’t answer, but they let you leave messages. I did this everyday.
Over the next few days things still sucked. I tried to change my domain supplier, but my domain was locked and I couldn’t log in to edit it. More phone messages.
A little over 2 weeks after Blazer blew up the site seemed a bit more stable. The control panel was accessible, though it wasn’t 100% functioning. MSSQL management was one thing not available. I was still unable to unlock my domain. My domain was expiring June 24, time was running out. Incidentally, I could have renewed my domain if I wanted; they still were allowing new business.
About June 19 Blazer started answering their phone. Support was slow, but they informed me I was able to change my domain registration information by email, which I did. My domain transferred June 23, one day before it expired.
Technical issues were ironed out slowly now that they were answering the phone, but they weren’t offering refunds for downtime or explanations. MSSQL was working but not accessible to log in and edit data or get a copy of my stored procedures.
The July Fourth holiday weekend brought some strange doings. At home I couldn’t access my sites that hadn’t been moved to a new host. I could at work, but still couldn’t get in to the SQL server to get my data.
Finally on July 10 I could. At this point MSSQL still didn’t work, but thankfully it didn’t matter anymore.
Blazer Network completely lost their credibility as a web host. If you see this and have had a similar experience, let me know with a link and a comment.
1 Comments:
Same thing happened to me. Screw those guys. The new owners say they aren't even going to release a statement about what happened. If it's that bad, you shouldn't even try to maintain the old company's name when you buy out someone. That's like saying, "hey, Enron is gone ... lets turn our energy company into Enron... that will get us lots of business!!!!"....
Doesn't work. Never do business with blazer again.
Post a Comment
Links to this post:
Create a Link
<< Home