CONUS SITREP

Major System Outage

• Unable to start new Workspace Agent runs · Region not named — Critical · Investigating

All Systems Operational

No active incidents

There are currently no active events. Use Azure Service Health to view other issues that may be impacting your services.

[RESOLVED] Elevated API issues and Launch Failures (+2 more in the feed)

• Amazon Elastic Compute Cloud · Tokyo · Tokyo only — [RESOLVED] Elevated API issues and Launch Failures — Latest update 2026-11-11T21:11:29.000Z — 日本時間 2026 年 11 月 11 日 午後 11 時 46 分から 2026 年 11 月 12 日 午前 2 時 46 分 (太平洋標準時 午前 6 時 46 分から午前 9 時 46 分) にかけて、主に単一のアベイラビリティーゾーン (apne1-az1) において、API エラー率の上昇および起動失敗が発生しておりました。また、ECS および Fargate のタスク起動失敗、ELB のプロビジョニング遅延、NAT Gateway の作成および関連付け解除ワークフローの失敗、Managed Flink アプリケーションの状態遷移の遅延など、他サービスにも影響が発生しておりました。稼働中の EC2 インスタンスおよび既存のワークフローには影響はございませんでした。この時間帯において、影響を受けているアベイラビリティーゾーンでは EC2 および EBS のヘルスデータが欠損または遅延し、CloudWatch アラームが INSUFFICIENT_DATA 状態に移行し、DescribeInstanceStatus API が Insufficient Data を返しておりました。 根本原因を特定し、日本時間 2026 年 11 月 12 日 午前 0 時 47 分までに緩和策の実施を開始しました。日本時間 午前 2 時 46 分には API の広範な回復が見られ、新規 EC2 イン
• Multiple services · UAE · UAE only — Increased Error Rates — Latest update 2026-09-15T10:27:10.000Z — We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to he
• Multiple services · Bahrain · Bahrain only — Increased Error Rates — Latest update 2026-09-15T10:22:28.000Z — We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the disruption of a second Availability

Window requested: 10-28-2026 to 11-11-2026 UTC. A posting older than 7 days with no cancel time is not labeled active.

AOR zone · AES Ohio / DAY

No open posting in the AOR zone.

Elsewhere in PJM

• WarningPost Contingency Local Load Relief Warning

  A Post Contingency Local Load Relief Warning has been issued to maintain SHEFFIEL 138 KV *E02 at 127.0 KV in the AEP for Transmission Contingency Control. Additional Comments: Load -No Generation or Switching available View Posting

  Regions: AEP

  Posted Nov 9, 7:13 AM EST

  View posting 105611

• WarningPost Contingency Local Load Relief Warning

  A Post Contingency Local Load Relief Warning has been issued to maintain COMMONWC 138 KV *E03 at 127.0 KV in the AEP for Transmission Contingency Control. Additional Comments: Load -No Generation or Switching available View Posting

  Regions: AEP

  Posted Nov 9, 7:11 AM EST

  View posting 105610

• Estimated Kp, 1-minute product

  0.33

  Nov 11, 6:26 PM EST

• Planetary Kp, 3-hour product

  2.67

  Nov 11, 1:00 PM EST

No active alerts for Montgomery, Ohio.

Declarations since Oct 12, 7:30 PM EDT. Filter: Ohio.

No declarations in this window.