Today's Issues

Friday Apr 14, 2017

[Resolved] CDB Ops | API Unavailable During Maintenance | DFW2
03:40 AM EDT
On 14 April 2017, from 00:00 to 04:00 CDT, engineers worked through a planned maintenance on Cloud Databases in the DFW2 data center. During the time of the maintenance, the Cloud Databases API was unavailable to make any changes to hosted databases. The maintenance has now concluded and API access has been restored. If you have any further questions, please reach out to a member of your support team.
12:15 AM EDT
On 14 April 2017, between 00:00 and 04:00 CDT, engineers are working to complete a planned maintenance in the DFW region. During this time, the Cloud Database API may be unavailable to make changes to your hosted databases. If you have any further questions, please reach out to a member of your support team.

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