Localize incident

Amazon S3 in some areas are currently down.

Notice Resolved View vendor source →

Localize experienced a notice incident on September 14, 2017, lasting 47m. The incident has been resolved; the full update timeline is below.

Started
Sep 14, 2017, 07:21 PM UTC
Resolved
Sep 14, 2017, 08:09 PM UTC
Duration
47m
Detected by Pingoru
Sep 14, 2017, 07:21 PM UTC

Update timeline

  1. identified Sep 14, 2017, 07:21 PM UTC

    Localizejs.com may not be available. Translations are still rendering for our customers.

  2. monitoring Sep 14, 2017, 08:07 PM UTC

    Amazon S3 is reporting increased error rates. We're monitoring the status of Amazon S3. Localizejs.com is currently up and translations are rendering for our customers.

  3. resolved Sep 14, 2017, 08:09 PM UTC

    Amazon appears to have resolved their S3 issues, which means you can access your Localize projects without delay.

  4. postmortem Aug 03, 2018, 05:32 PM UTC

    Update from AWS about their outage earlier today, September 14, 2017. Outage period: ![Image of Outage](https://global.localizecdn.com/uploads/1505423424308.png) Detailed log: ![Image of details](https://global.localizecdn.com/uploads/1505423634968.png) During this period Localize may have been unaccessible. This meant our customers were not able to access their Localize projects. However, existing translations continued to render on our customer's applications (unless they were also directly affected by the AWS S3 outage.) We apologize for any impact this may have caused for our customers.