Simon Data incident

AWS Outage

Major Resolved View vendor source →

Simon Data experienced a major incident on June 13, 2023 affecting Simon Web App and Simon Event Trigger Flows and 1 more component, lasting 5h 57m. The incident has been resolved; the full update timeline is below.

Started
Jun 13, 2023, 07:37 PM UTC
Resolved
Jun 14, 2023, 01:35 AM UTC
Duration
5h 57m
Detected by Pingoru
Jun 13, 2023, 07:37 PM UTC

Affected components

Simon Web AppSimon Event Trigger FlowsSimon Data PipesSimon Data Syncs

Update timeline

  1. identified Jun 13, 2023, 07:37 PM UTC

    Our upstream provider, Amazon Web Services (AWS), is currently experiencing an issue which is affecting our services. We are currently looking into this issue in partnership with AWS and will provide updates.

  2. identified Jun 13, 2023, 08:36 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jun 13, 2023, 08:37 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Jun 13, 2023, 08:56 PM UTC

    AWS has started to see signs of recovery which has positively affected Simon components affected. We are continuing to work on this issue in partnership with AWS support.

  5. identified Jun 13, 2023, 09:25 PM UTC

    The AWS outage has been resolved and Simon recovery is on it's way. We are continuing to monitor our systems as components become operational. We will provide more updates as we make progress on recovery efforts.

  6. identified Jun 13, 2023, 09:51 PM UTC

    The AWS outage has been resolved and Simon recovery is on it's way. We are continuing to monitor our systems as components become operational. We will provide more updates as we make progress on recovery efforts.

  7. identified Jun 13, 2023, 09:55 PM UTC

    The AWS outage has been resolved and Simon recovery is on it's way. We are continuing to monitor our systems as components become operational. We will provide more updates as we make progress on recovery efforts.

  8. monitoring Jun 14, 2023, 01:02 AM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Jun 14, 2023, 01:35 AM UTC

    This incident has been resolved.