Today's Issues

Thursday Apr 20, 2017

[Resolved] Resolved: MyRackspace and Encore | Managed Virtualization Section Unavailable | All Regions
03:06 PM EDT
On 20 April 2017, from 10:45 to 12:41 CDT, engineers identified impact to the Managed Virtualization sections of the MyRackspace Portal and Encore in all regions and worked to resolve the issue as quickly as possible. During this time, Customers may have experienced issues when attempting to access the Managed Virtualization section of the MyRackspace Portal.

If you have any other questions or concerns, please contact a member of your support team.
11:22 AM EDT
On 20 April 2017, starting at 10:45 CDT, engineers identified issues impacting the Managed Virtualization sections of the MyRackspace Portal and Encore in all regions. Engineers are engaged and actively working to resolve the issue. During this time, Customers may experience issues when attempting to access the Managed Virtualization section of the MyRackspace Portal.

[Resolved] RackConnect v3 | RackConnect v3 Unavailable | DFW Region
07:35 AM EDT
On 20 April 2017, starting at 05:30 CDT, engineers identified that a scheduled maintenance is currently impacting RackConnect v3 in the DFW Region. As of 06:53 CDT, engineers confimed that the affected RackConnect v3 instances were back online and the any remaining issues were resolved. During this time, RackConnect v3 environments may have been unavailable for a subset of customers in the DFW Region.
05:08 AM EDT
On 20 April 2017, starting at 05:30 CDT, engineers began work to resolve issues impacting RackConnect v3 in the DFW Region. During this time, RackConnect v3 environments may be unavailable for a subset of customers in the DFW Region.

[Resolved] Cloud Servers | ServiceNet Disruption | DFW Region
07:36 AM EDT
On 20 April 2017, starting at 05:00 CDT, engineers identified ServiceNet issues during a scheduled non-impacting maintenance. Engineers determined that an internal error caused a ServiceNet outage for a subset of customers in the DFW Region. Engineers resolved customer impact at 05:10 CDT. During this time, customers and may have experienced connectivity issues between their Cloud Servers, RackConnect v2, and other cloud products.
04:51 AM EDT
On 20 April 2017, starting at 05:00 CDT, engineers identified ServiceNet issues during a scheduled non-impacting maintenance. Engineers determined that an internal error caused a ServiceNet outage for a subset of customers in the DFW Region. Engineers resolved customer impact at 05:10 CDT. During this time, customers and may have experienced connectivity issues between their Cloud Servers, RackConnect v2, and other cloud products.

[Resolved] Cloud Load Balancers | Inaccurate Node State in the API and Cloud Control Panel | DFW Region
06:53 AM EDT
On 6 March 2017, the Cloud Load Balancer team was made aware that a portion of customers are experiencing inaccurate node state being reflected in the API and the Cloud Control Panel for the DFW region. Some customers have reported that the status returned by the API for a given node in a load balancer instance is inconsistent with the running state of the node and traffic flow. This issue affects the CLB API and control panel node statuses only – it has not been observed to impact client traffic flow to nodes. Customers can recreate monitoring health checks on impacted nodes to restore the impacted status views in the API and control panel. At this time, Cloud Load Balancer engineers continue to investigate the issue. If you have any questions or need assistance, please contact a member of your support team.
06:04 AM EDT
On 6 March 2017, the Cloud Load Balancer team was made aware that a portion of customers are experiencing inaccurate node state being reflected in the API and the Cloud Control Panel for the DFW region. Some customers have reported that the status returned by the API for a given node in a load balancer instance is inconsistent with the running state of the node and traffic flow. This issue affects the CLB API and control panel node statuses only – it has not been observed to impact client traffic flow to nodes. Customers can recreate monitoring health checks on impacted nodes to restore the impacted status views in the API and control panel. At this time, Cloud Load Balancer engineers continue to investigate the issue. If you have any questions or need assistance, please contact a member of your support team.
11:56 AM EDT
On 6 March 2017, the Cloud Load Balancer team was made aware that a portion of customers are experiencing inaccurate node state being reflected in the API and the Cloud Control Panel for the DFW region. Some customers have reported that the status returned by the API for a given node in a load balancer instance is inconsistent with the running state of the node and traffic flow. At this time, Cloud Load Balancer engineers are actively working to investigate and resolve the issue. If you have any other questions or concerns, please contact a member of your support team.