Safe FME incident

Unable to launch new instances or to access recently unpaused instances

Major Resolved View vendor source →

Safe FME experienced a major incident on May 10, 2019 affecting FME Flow Hosted Instances, lasting 8h 32m. The incident has been resolved; the full update timeline is below.

Started
May 10, 2019, 07:46 PM UTC
Resolved
May 11, 2019, 04:19 AM UTC
Duration
8h 32m
Detected by Pingoru
May 10, 2019, 07:46 PM UTC

Affected components

FME Flow Hosted Instances

Update timeline

  1. monitoring May 10, 2019, 07:46 PM UTC

    Due to a partial outage of AWS Route 53, we are unable to update the DNS records of FME Cloud instances. This results in paused instances being inaccessible after being restarted and prevents the launch of new instances. Running instances are not currently affected. We are monitoring the issue and will update the DNS records once the Route53 outage is resolved.

  2. resolved May 11, 2019, 04:19 AM UTC

    The AWS Route 53 outage was resolved and we have confirmed that all the FME Cloud instances that were affected are now accessible. If you are still experiencing difficulties accessing your instances, please contact our support team.