WP Engine Reviews

I signed up for WPengine after speaking with a helpful sales guy (UK based). The server needed to include 2x installations of Wordpress, one for the website and another for the blog (it was actually a news site for SEO, but for the purposes of this review we will just call it a blog) www.(main)fistwpinstall.co.uk/(blog)secondWPinstall/ I was informed I could do this on the personal plan, no problem. Yey! On signing up, paying for a year on the personal plan with UK Data centre, I figure this is not possible by doing some research. I spoke to a colleague via the chat box to clarify, and they tell me I need to buy a Professional Plan unless I add an additional website (at an additional $14 a month) and add set up a forwarder on the DNS for the sub domain, not happy I use a second account (Which I purchased with the original order but was hoping to use it for another website, but this is a different story) So I install the blog and try to set this up via the DNS - Im struggling at this point so I speak to another Technical advisor via the Chatbox and he informs me, no, this can not be done! - As you can imagine, not happy at this point! I speak to the original chap on the phone again who advises I upgrade to the professional plan. A little unhappy, I ask to speak to his Boss. I don't understand why it is so difficult to add a second installation of WordPress on the server and why this is going to cost me an additional $700, so when you include UK data Centre this works out at $1500 total. I understand the benefits of using WPEngine; I get it! I just don't know how you can go from a plan that allows 1x WordPress install to a plan that accepts ten installs. I don't need ten installs; I only need 1 install and sub folder with wordpress installed for the website blog, how is this so difficult for WPengine to understand, surley most companies have this? why are you talking to me like I am the first person to ever ask this question. IN short, I have spoken with two people on the phone - employee 1x didn't have a clue what he was talking about. The other (his manager) didnt understand the point I was trying to raise, he was very abrupt and kind of told me to go away, they're not interested, "The product is not for me, and I need to find another server, WP Engine isn't suitable for you riff-raff" (he didn't say riff-raff, I made that up, but that was how I interpreted it. Secondly the support staff on the chat facility the first person did not have a clue, she took a long time to get back with replies, she must have been the 1st day on the job. She kept referring me back to blog posts for answers. She gave me the wrong advice and wasted a good few hours of my time. The 2nd chap I spoke to on the chat - in all fairness he was very knowledgeable, he shot from the hip, was very to the point and didn't skirt around any of the points I was raising. If any of the management at WPEngine are reading this I would ask that you, please look over this case, you very clearly have issues that need addressing. Some of your employees don't know the product they sell, and you have a big gap in your service offering. I am now going to go back to the drawing board and try to find another server - a full 3/4 hours of my life wasted!

First world class Managed WordPress Hosting.

This is a very popular hosting site for wordpress blogs and websites, I can't find anything suggesting that the host is not trustworthy. One comment says that wpengine is listed on the URIBL, but it seems not to be true sins I can't find them on the list.

I hope everyone here understands exactly what they're talking about. WP engine is a web host they do a first class job. The fact that one bad apple could hurt this entire company is unfortunate but please do not judge the entire host for one of their customers. I have given this link to show you guys that WP Engine was on top of this problem and fixed it right away I think if you read this you will be far more understanding as to why the domain has been affiliated with spam. http://wpengine.com/2012/07/dns-issues-earlier-that-caused-wpengine-com-to-go-offline-briefly-this-morning/?SSAID=389818 if anyone does not feel like clicking on the link that's understandable I have posted the information that you would get from clicking on that link

"DNS ISSUES EARLIER THAT CAUSED WPENGINE.COM TO GO OFFLINE BRIEFLY THIS MORNING
WRITTEN BY BEN METCALFE ON JULY 17, 2012
Ben Metcalfe, co-founder WP Engine writes…

Earlier this morning, our domain WPEngine.com stopped resolving for a short time. This resulted in our site, our my.wpengine customer control panel, our status.wpengine.com domain, and some customer sites to be unavailable for some visitors, depending on the status of their ISP’s DNS cache.

First and foremost we’d like to apologize to everyone who was effected — although the downtime was brief and was caused by an upstream provider outside of our control, DNS downtime is unacceptable!

I’d like to take the opportunity to explain what happened.

Some time yesterday it was reported that one of our client’s websites was hosting malware. We host tens-of-thousands of domains, and so occasionally such infections do occur, often when a new customer moves to us, taking their existing malware infection with them.

The person/entity reporting this sent emails to the [email protected] email addresses of all of our service providers, including ones that were not involved in the hosting of the infected site. They also sent the report to the [email protected] email address of our domain registrar. Unfortunately, and for reasons unknown, they did not send the report to our own [email protected] email address here at WP Engine.

One of our providers immediately forwarded the email to us and we had our independent security partner investigate and clean up the infected account within a few hours of the original report.

However, our domain registrar decided to take the entire wpengine.com domain offline — including all subdomains — in order to bring the infected site offline (the infected site was pointing their domain to a CNAME of a wpengine.com subdomain). Unfortunately they decided to do this many hours after the infected site had been cleaned up, and also without checking with us or successfully getting into contact with us.

As soon as we discovered our domain registrar was blocking DNS nameserver requests we made contact with them and had this block removed. Initially they actually blamed our DNS provider, which also sent us on a wild goose chase. Eventually they admitted they had done it.

As of right now, all sites should be back up online. We are investigating our next course of action, including whether there are any procedures we can improve on our side, and ultimately whether we need to change domain registrar. We will keep you posted,

Many thanks for your understanding,

Ben”

posted by Thomas Zickell

Partnered with Securi
http://sucuri.net/company/partners

Founded by Jason Cohen, author of the A Smart Bear blog.