8base incident

8base System Unavailable - AWS Outage is impacting our availability

Major Resolved View vendor source →

8base experienced a major incident on June 13, 2023 affecting 8base Platform API and 8base Console Organizations and 1 more component, lasting 2h 26m. The incident has been resolved; the full update timeline is below.

Started
Jun 13, 2023, 08:29 PM UTC
Resolved
Jun 13, 2023, 10:55 PM UTC
Duration
2h 26m
Detected by Pingoru
Jun 13, 2023, 08:29 PM UTC

Affected components

8base Platform API8base Console Organizations8base AppBuilder

Update timeline

  1. monitoring Jun 13, 2023, 07:10 PM UTC

    AWS Operational issue

  2. monitoring Jun 13, 2023, 07:11 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Jun 13, 2023, 07:28 PM UTC

    https://health.aws.amazon.com/health/status

  4. monitoring Jun 13, 2023, 07:31 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Jun 13, 2023, 07:31 PM UTC

    We are monitoring AWS progress toward resolving their issue. Details of the outage can be tracked here: https://health.aws.amazon.com/health/status

  6. monitoring Jun 13, 2023, 07:55 PM UTC

    We continue to monitor the situation and are awaiting AWS updates - the latest report from AWS reads: AWS is continuing to experience increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. We have identified the root cause as an issue with AWS Lambda, and are actively working toward resolution

  7. monitoring Jun 13, 2023, 08:29 PM UTC

    All, the latest update from AWS: AWS is continuing to work to resolve the error rates invoking Lambda functions. We're also observing elevated errors obtaining temporary credentials from the AWS Security Token Service, and are working in parallel to resolve these errors.

  8. monitoring Jun 13, 2023, 09:09 PM UTC

    Many AWS services are now fully recovered and marked Resolved on this event. We are continuing to work to fully recover all services.

  9. resolved Jun 13, 2023, 10:55 PM UTC

    This incident has been resolved.