Today's Issues

Tuesday Apr 11, 2017

[Resolved] Cloud Databases | API Unavailable | DFW Region
11:16 PM EDT
On 11 April 2017, from 20:20 CDT to 23:30 CDT, engineers worked to resolve issues which affected the Cloud Databases API in the DFW region. During this time, customers in the affected region may have been unable to perform actions such as creating, resizing, or deleting databases, however, existing instances remain online.

Functionality has returned to the Cloud Database API; however, a scheduled disruptive maintenance will begin at 00:01 CDT to 06:00 CDT on 12 April 2017.
08:47 PM EDT
On 11 April 2017, at approximately 20:20 CDT, our engineers began working to resolve of issue affecting the Cloud Databases API in the DFW region and are working to resolve the problem.

During this time, customers in the affected region may be unable to perform actions such as creating, resizing, or deleting databases, however, existing instances remain online.

Currently, the maintenance scheduled for 12 April, at 00:01 CDT, will go forward as planned.

This notification will be updated as further information becomes available.

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