Service Health
Incident affecting Cloud Machine Learning
Translate API elevated latency / errors
Incident began at 2017-05-16 11:15 and ended at 2017-05-16 19:00 (all times are US/Pacific).
Date | Time | Description | |
---|---|---|---|
| 16 May 2017 | 21:56 PDT | The issue with Translation Service and other API availability has been resolved for all affected users as of 19:00 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence. This will be the final update on this incident. |
| 16 May 2017 | 18:07 PDT | Engineering is continuing to investigate the API service issues impacting Translation Service API availability, looking into potential causes and mitigation strategies. Certain other API's, such as Speech and Prediction may also be affected. Next update by 20:00 Pacific. |
| 16 May 2017 | 15:58 PDT | Engineering is continuing to investigate the API service issues impacting Translation Service API (and other API service) availability. Next update by 18:00 Pacific. |
| 16 May 2017 | 14:02 PDT | Engineering is continuing to investigate the API service issues impacting Translation Service API (and other API service) availability. The previous avenue of investigation has proven helpful but not conclusive. Next update by 16:00 Pacific. |
| 16 May 2017 | 12:58 PDT | Engineering is continuing to investigate the API service issues impacting Translation Service API (and other API service) availability. Some of the smaller scale mitigation testing is looking positive at this point, but further testing is necessary before we can confirm that a full solution is available. Next update by 14:00 Pacific. |
| 16 May 2017 | 11:49 PDT | Engineering is continuing to investigate the API service issues impacting Translation Service API (and other API service) availability. We are currently exploring mitigation and remediation options. Next update by 13:00 Pacific. |
| 16 May 2017 | 11:15 PDT | The API service is experiencing a 4% error rate, which has been mostly observed through the Translation Service APIs, which are experiencing elevated latency and errors. Our Engineering Team is working on it. If you have questions or are impacted, please open a case with the Support Team and we’ll work with you until this issue is resolved. An update will be provided by 11:45 AM US/Pacific. |
- All times are US/Pacific