Connectivity issues in Sydney

• General availability of applications published to Clouds hosted within the Sydney region

• Kony Cloud services within the Sydney region

[05:47 UTC] Connectivity issues in Sydney region reported by AWS for many core services such as EC2, ELB, EB, S3, Route53, & RDS.

[June 7, 06:44 UTC] Resolved. Applications and services have been restored.

RCA from AWS: A significant number of resources within one of the Sydney Availability Zones experienced a loss of power driving increased API error rates, higher latencies, and delays in propagation of instance state data in the affected Availability Zone. At 06:46 UTC, power was restored to the facility and instances and volumes started to recover. At 8:00 UTC, 80% of the affected instances and volumes had been recovered by automated systems. At 8:45 UTC, the increased error rates, latencies, and delayed propagation were fully resolved. A couple of unexpected issues prevented automated systems from recovering the remaining instances and volumes. The AWS team was able to fix these issues, and by 15:00 UTC, all but a small number of instances and volumes were recovered. Since 15:00 UTC AWS was working to recover the remaining instances and volumes. Most of these instances were hosted on hardware, which was adversely affected by the loss of power. At 18:50 UTC, AWS recommended to replace any remaining affected instances or volumes. The Kony team worked to restore remaining affected instances or volumes and by June 7, 06:44 UTC, the remaining affected instances or volumes were all restored and verified as behaving correctly.