Safe FME incident
Unable to launch new instances or to access recently unpaused instances
Resolved after 8 hours 32 minutes, affecting FME Flow Hosted Instances, on May 10, 2019.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than Safe FME
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services