Localize incident

AWS is currently experiencing issues impacting Localize

Notice Resolved View vendor source →

Localize experienced a notice incident on February 28, 2017, lasting 3h 13m. The incident has been resolved; the full update timeline is below.

Started
Feb 28, 2017, 08:39 PM UTC
Resolved
Feb 28, 2017, 11:52 PM UTC
Duration
3h 13m
Detected by Pingoru
Feb 28, 2017, 08:39 PM UTC

Update timeline

  1. investigating Feb 28, 2017, 08:39 PM UTC

    We apologize for any issues you may experience with Localize. We are currently investigating issues involving slow performance, machine translations, emails, changes in phrase states. Services remain degraded due to a provider issue with AWS.

  2. monitoring Feb 28, 2017, 10:57 PM UTC

    Services are starting to recover as a result of Amazon Web Services stabilizing: https://status.aws.amazon.com. Emails are being sent out as expected. We expect other services to recover quickly. We apologize for the interruption to service and will continue to monitor our systems to ensure services remain stable.

  3. resolved Feb 28, 2017, 11:52 PM UTC

    Following the stabilization of AWS service, all Localize services have been fully restored and are stable. Thanks for your patience.