Skip to main content
AWS

CONNECT (ap-northeast-1): Increased Error Rates

Partial outage Lasted 38m · started · AWS's page

Level
confirmed
Worst impact
Partial outage
Components
CONNECT
Regions
ap-northeast-1
Down Index
56of 100

What to do

  • Check whether you use AWS CONNECT in ap-northeast-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 38m it lasted.

    Anything that failed between 2026-08-21 02:02 UTC and 2026-08-21 02:40 UTC may need a replay.
  • Subscribe to AWS's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=aws works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from AWS 2

  1. investigating

    AP-NORTHEAST-1リージョンにおいて、エラー率が上昇しており、リアルタイムメトリクスに影響が出ています。お客様はリアルタイムメトリクスデータの欠落または遅延を経験する可能性があります。| We are experiencing increased error rates affecting real-time metrics in the AP-NORTHEAST-1 Region. Customers may experience missing or delayed real-time metric data.

    provider

  2. investigating

    日本時間 8:58 AM から 10:34 AM の間、AP-NORTHEAST-1 リージョンにおける Amazon Connect のリアルタイムメトリクスに影響する遅延が増加し、データが欠落する、またはデータが最新の状態に更新されない事象が発生しました。この間、お客様は分析レポート内で一部のデータが反映されない状況を経験した可能性があり、また、コンタクトフロー内でリアルタイムメトリクス (例: 人員の確認ブロック) にアクセスする際に問題が発生した可能性があります。根本原因は、メトリクスイベント配信を担うサブシステムの問題であると特定しました。日本時間 10:13 AM に緩和策の適用を開始し、 10:34 AM までに影響を解消しました。本事象は解決済みであり、サービスは正常に稼働しています。| Between 4:58 PM and 6:34 PM PDT, we experienced increased delays affecting real-time metrics for Amazon Connect in the AP-NORTHEAST-1 Region, resulting in missing or stale data. During this time, customers may have experienced missing data within analytics reports, and may have observed issues if accessing realtime metrics within contact Flows, such as checking agent staffing. We identified the root cause to be an issue with the subsystem responsible for metric event delivery. We started applying the mitigations at 6:13 PM and mitigated the issue by 6:34 PM. The issue has been resolved and the service is operating normally.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-247a9cbc2d

Is AWS still down?

No, this incident was resolved 2026-08-21 02:40 UTC. For AWS's live state, see https://down.guide/aws.

How long did it last?

38m, from 2026-08-21 02:02 UTC to 2026-08-21 02:40 UTC, by the times AWS posted.

What was affected?

AWS named CONNECT in ap-northeast-1.

What caused it?

AWS hasn't published a root cause. If it does, it shows here.

Where does this come from?

AWS's official status page, https://health.aws.amazon.com/health/status, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.