My question is simple, is this you? Please let me know if you have a solution or if you're encountering the same thing now. Explanation: The problem appears that as soon as we add WordPress to our customer sites that 503 errors generate randomly on the site causing both the child application where the WordPress web app is located and the entire web application to be unavailable for a couple of minutes while the app pool recycles. I've laboriously removed our own code as the culprit of the unfortunate event. Support says that this is because of too many concurrent HTTP connections (a pretty good accomplishment since these are measured in milliseconds) and I know that WordPress can be a memory hog (although the memory usage monitors I've viewed in the admin page indicate a fairly low memory usage of about 35MB - although I'm somewhat skeptical). It doesn't appear to make a difference on how many restrictions I attempt to apply via the web.config and wp-config to manage the memory and connection limits of the blog, the 503 still comes all the same. While support has even doubled the allotted number of concurrent http connections for me I still seem unable to fix this. Is there anyone else out there who has experienced this? If so was there a way in which you were able to resolve this?