GS2 Outage History

GS2 is up right now

GS2 had 4 outages in the last 2 years totaling 13h 1m of downtime — averaging 0.2 incidents per month.

There were 4 GS2 outages since August 6, 2025 totaling 13h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.gs2.io

Major October 20, 2025

Increase in error rate

Detected by Pingoru
Oct 20, 2025, 05:45 PM UTC
Resolved
Oct 20, 2025, 09:43 PM UTC
Duration
3h 57m
Affected: AWS lambda-us-east-1
Timeline · 5 updates
  1. investigating Oct 20, 2025, 07:40 PM UTC

    We have observed an increase in error rates since 2025-10-20 16:30(UTC).

  2. investigating Oct 20, 2025, 07:40 PM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 20, 2025, 08:56 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Oct 20, 2025, 09:21 PM UTC

    The error rate has recovered to normal levels. However, the issue in AWS us-east-1 is still ongoing, and we will continue to monitor it.

  5. resolved Oct 20, 2025, 09:43 PM UTC

    The error rate has remained within normal ranges, and the issue is considered resolved. However, AWS continues to address the incident as documented in its outage report. It cannot be ruled out that the error rate may rise again during the ongoing resolution process, as seen this time. Please continue to monitor the outage report with particular caution until AWS issues a full recovery report.

Read the full incident report →

Critical October 20, 2025

DynamoDB Outage

Detected by Pingoru
Oct 20, 2025, 07:10 AM UTC
Resolved
Oct 20, 2025, 09:33 AM UTC
Duration
2h 22m
Affected: AWS dynamodb-us-east-1
Timeline · 6 updates
  1. identified Oct 20, 2025, 07:10 AM UTC

    Due to an AWS DynamoDB outage, ongoing service disruptions are occurring in the us-east-1 region of GS2.

  2. identified Oct 20, 2025, 07:27 AM UTC

    Errors have been confirmed across multiple components, not limited to DynamoDB.

  3. identified Oct 20, 2025, 07:29 AM UTC

    A case has been created in the AWS Health Dashboard. Please check the following for detailed recovery status. https://health.aws.amazon.com/health/status

  4. identified Oct 20, 2025, 07:58 AM UTC

    We have confirmed that the issue is still ongoing.

  5. monitoring Oct 20, 2025, 08:47 AM UTC

    We are pleased to announce that routing to us-east-1 began to be cut off around 2025-10-20 07:40 (UTC). By around 2025-10-20 08:07 (UTC), the switchover was complete, with all traffic now flowing to the secondary region (us-west-2), and the outage has been resolved. However, the outage in AWS us-east-1 continues. Once restored, us-east-1 will rejoin service delivery. We will notify you again when us-east-1 returns to service delivery.

  6. resolved Oct 20, 2025, 09:33 AM UTC

    2025-10-20 09:10 (UTC), us-east-1 rejoined the service delivery.

Read the full incident report →

Major September 22, 2025

WebSocket server error rate increases

Detected by Pingoru
Sep 22, 2025, 08:34 AM UTC
Resolved
Sep 22, 2025, 08:34 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 22, 2025, 08:34 AM UTC

    Due to a problem with the WebSocket server, connections could not be established or messages could not be received correctly after a connection was established, but this problem has now been resolved and is being monitored.

Read the full incident report →

Notice August 6, 2025

全体的なサービス停止

Detected by Pingoru
Aug 06, 2025, 01:35 AM UTC
Resolved
Aug 06, 2025, 08:16 AM UTC
Duration
6h 40m
Timeline · 3 updates
  1. investigating Aug 06, 2025, 01:35 AM UTC

    現在アクセス集中によりサービスが停止しています。

  2. identified Aug 06, 2025, 03:32 AM UTC

    一部のテナントのみが影響を受けている事象だと判明しました。調査は引き続き継続中です。

  3. resolved Aug 06, 2025, 08:16 AM UTC

    事象は解消しました。

Read the full incident report →