We currently have sevaral of our agents conferenced in with Rackspace Support and Customers trying to come to a resolution on this issue, but we have identified that the issue is related to Rackspace refusing connections from McAfee IPs based on arbitrary maximum congruent connection limitations on their network. Unfortunately McAfee cannot force Rackspace to alter their archetecture or accept connections, and we recommend customers of both McAfee SaaS and Rackspace contact Rackspace to discuss the issue further.
Thank you for contacting Cloud Sites support about this issue. As we discussed McAffee/MXLogic have made changes to their infrastructure recently and the new servers are creating many more connections than the normal limits, we have increased the allowed connections to try to accommodate them but they are trying to use more. We have been in discussion with them and it is now up to McAfee to make the necessary changes on their systems.
Rackspace Cloud Sites Support
I understand your frustration, but we have nothing to hide here.
Unfortunately the information Rackspace is providing is misleading. Any major environmental or archetectual changes that occur that will impact customers is communicated through Maintenance Communications and Service Alerts. No maintenance that would have impacted customers recently took place, and minor adjustments to the system are not communicated to any third parties, thus Rackspace would not have any way of determining if additional servers have been added, since all connections come from our two /21 blocks of IPs.
As stated earlier, we are currently working with Rackspace to determine what actually is the cause and to determine an appropriate resolution. I will see if our management team would be willing to post a service alert, but typically speaking service alerts are reserved for issues that our organization can control (e.g. a problem with the service, not a problem with an unrelated organization).