Prismatic incident

Degraded services in US-EAST-2 Regions

Major Resolved View vendor source →

Prismatic experienced a major incident on October 7, 2024 affecting Integration Runner and OAuth 2.0 Refresh, lasting 29m. The incident has been resolved; the full update timeline is below.

Started
Oct 07, 2024, 07:39 PM UTC
Resolved
Oct 07, 2024, 08:08 PM UTC
Duration
29m
Detected by Pingoru
Oct 07, 2024, 07:39 PM UTC

Affected components

Integration RunnerOAuth 2.0 Refresh

Update timeline

  1. investigating Oct 07, 2024, 07:39 PM UTC

    The Prismatic team started seeing increased error rates in multiple services starting at 13:27 Mountain. The errors appear to originate in the underlying AWS services. We have reached out to our contacts at AWS for more information and to bring increased awareness to this issue. We will continue to monitor the situation and work towards resolution.

  2. investigating Oct 07, 2024, 07:40 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 07, 2024, 07:44 PM UTC

    We continue to monitor the situation.

  4. identified Oct 07, 2024, 07:50 PM UTC

    AWS has confirmed an issue with S3 and related services in their us-east-2 region. They are working towards resolution. We will continue to monitor the situation and provide updates as they are available.

  5. monitoring Oct 07, 2024, 07:59 PM UTC

    It appears that the relevant issues have been identified and addressed by the AWS teams. We will continue to monitor for new additional problems and provide updates until we are confident that operation has been completely restored.

  6. resolved Oct 07, 2024, 08:08 PM UTC

    It appears the issue has been completely resolved and AWS is working to understand the root issue(s). We will open a new issue on this status page if any further problems emerge.