Cloud Load Balancers Issues

Friday Apr 21, 2017

Cloud Load Balancers | Inaccurate Node State in the API and Cloud Control Panel | DFW Region
07:01 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.

[Resolved] Resolved: LBASS | Admin API Unavailable | LON Region
07:08 AM EDT
Hello,

On 21 April 2017, between 10:20 UTC and 12:02 UTC, engineers became aware of an issue affecting the admin api in the LON region for Cloud Loadbalancers and are working to resolve the issue.

During this time, customers attempting to make updates in the LON region using the admin api may receive error messages.

Regards,

Rackspace
06:56 AM EDT
On 21 April 2017, between 10:20 and 12:05 UTC, engineers worked to resolve an issue affecting the admin api in the LON region for Cloud Loadbalancers.During this time, customers attempting to make updates in the LON region using the admin api may receive error messages.
06:55 AM EDT
On 21 April 2017, between 10:20 and 12:02 UTC, engineers worked to resolve an issue affecting the admin api in the LON region for Cloud Loadbalancers.During this time, customers attempting to make updates in the LON region using the admin api may receive error messages.
06:45 AM EDT
On 21 April 2017, at approximately 10:20 UTC, engineers became aware of an issue affecting the admin api in the LON region for Cloud Loadbalancers and are working to resolve the issue.During this time, customers attempting to make updates in the LON region using the admin api may receive error messages.

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