Today's Issues

Wednesday Mar 29, 2017

[Resolved] Global Billing | Payment and Sign-up Failures | ORD1
12:19 PM EDT
On 29 March 2017, between 07:20 and 10:00 CDT, engineers identified an issue impacting Payment Services and Sign-up Services in the all regions. The team engaged the vendor, who reported a widespread issue across all of their data centers. At 12:19 CDT, the vendor confirmed they fixed the issue and impact was resolved at 10:00 CDT.

During this time customers may have experienced failures when making payments or delays when attempting to initiate new services.
10:51 AM EDT
On 29 March 2017, at 07:20 CDT, Engineers identified an issue impacting Payment Service System in the ORD1 region. The team has engaged the vendor, who has reported a widespread issue across all of their data centers. During this time customers may experience failures when making payments or delays when attempting to initiate new services.

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