Safe FME incident

Partial outage on FME Cloud instances operations

Minor Resolved View vendor source →

Safe FME experienced a minor incident on March 14, 2017, lasting 9h 26m. The incident has been resolved; the full update timeline is below.

Started
Mar 14, 2017, 07:24 AM UTC
Resolved
Mar 14, 2017, 04:50 PM UTC
Duration
9h 26m
Detected by Pingoru
Mar 14, 2017, 07:24 AM UTC

Update timeline

  1. monitoring Mar 14, 2017, 07:24 AM UTC

    AWS is experiencing issues with DNS change requests in all regions. As a result, you might not be able to start or stop your instance. We are monitoring the situation and will update the status as soon the issue is resolved.

  2. monitoring Mar 14, 2017, 03:09 PM UTC

    We are still experiencing issues with the DNS services we use (AWS Route 53). Running instances that were launched more than 12 hours ago are unaffected. If you tried to launch, pause or start an instance within the last 12h, the action likely didn't complete. We are working to manually address requests that were made and that failed.

  3. resolved Mar 14, 2017, 04:50 PM UTC

    AWS recovered for the most part, instance starts and stops are working again. All affected instances are recovered and entered the correct state.