Today's Issues

Monday Apr 17, 2017

[Resolved] Resolved: DCX Services | Database Server became Unresponsive | All Regions
09:30 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address. As of 09:37 CDT, engineers reported the issues were resolved.

During this time, customers were unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers were unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers were unable to view their customer service IP address for dedicated gear.
09:25 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address. As of 09:37 CDT, engineers reported the issues were resolved.

During this time, customers were unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers were unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers were unable to view their customer service IP address for dedicated gear.
09:04 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address.

During this time, customers will be unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers are unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers will not be able to view their customer service IP address for dedicated gear.

If you have any other questions or concerns, please contact a member of your support team.

Sincerely,

Rackspace

[Resolved] Resolved: DCX Services | Database Server became Unresponsive | All Regions
09:18 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address. As of 09:37 CDT, engineers reported the issues were resolved.

During this time, customers were unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers were unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers were unable to view their customer service IP address for dedicated gear.
09:03 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address.

During this time, customers will be unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers are unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers will not be able to view their customer service IP address for dedicated gear.

If you have any other questions or concerns, please contact a member of your support team.

Sincerely,

Rackspace

[Resolved] Resolved: DCX Services | Database Server became Unresponsive | All Regions
09:21 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address. As of 09:37 CDT, engineers reported the issues were resolved.

During this time, customers were unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers were unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers were unable to view their customer service IP address for dedicated gear.
09:02 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address.

During this time, customers will be unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers are unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers will not be able to view their customer service IP address for dedicated gear.

If you have any other questions or concerns, please contact a member of your support team.

Sincerely,

Rackspace

[Resolved] Resolved: DCX Services | Database Server became Unresponsive | All Regions
09:29 AM EDT
On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address. As of 09:37 CDT, engineers reported the issues were resolved.

During this time, customers were unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers were unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers were unable to view their customer service IP address for dedicated gear.
09:01 AM EDT

On 17 April 2017, at approximately 08:57 CDT, engineers identified that a database server became unresponsive in the IAD2 data center. The database server impacted MyRackspace Portal and Cloud Control Panel sections for DNS and for customer service IP address.

During this time, customers will be unable to make DNS updates through MyRackspace portal or the Cloud Control Panel. During this time, Rack Connect customers are unable to make changes or delete public IPs for their Cloud Servers and Cloud Accounts. Additionally, customers will not be able to view their customer service IP address for dedicated gear.

If you have any other questions or concerns, please contact a member of your support team.

Sincerely,

Rackspace


[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.