{
  "meta": {
    "version": "v1",
    "pricing": {
      "public": {
        "label": "Public",
        "description": "Read-only API access for lightweight status checks and public integrations."
      },
      "premium": {
        "label": "Premium",
        "description": "API keys with higher hourly quotas, plus Slack, Teams, Discord, webhook, and email outage alerts across your vendor stack."
      }
    },
    "generatedAt": "2026-11-17T10:10:23.514Z"
  },
  "data": {
    "id": "incident_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce",
    "slug": "aws-resolved-increased-connectivity-issues-in-us-east-1-n-virginia-2026-11-15",
    "title": "[RESOLVED] Increased Connectivity issues in US-EAST-1 (N. Virginia)",
    "summary": "Increased Connectivity issues in US-EAST-1",
    "status": "resolved",
    "stale": false,
    "severity": "major",
    "startedAt": "2026-11-15T12:38:02+00:00",
    "updatedAt": "2026-11-15T14:53:29+00:00",
    "resolvedAt": "2026-11-15T14:53:29+00:00",
    "provider": {
      "slug": "aws",
      "name": "AWS"
    },
    "affectedServices": [],
    "regions": [
      "us-east-1"
    ],
    "links": {
      "html": "/incidents/aws-resolved-increased-connectivity-issues-in-us-east-1-n-virginia-2026-11-15",
      "api": "/api/v1/incidents/aws-resolved-increased-connectivity-issues-in-us-east-1-n-virginia-2026-11-15",
      "providerHtml": "/providers/aws",
      "alerts": "https://outagedeck.com/account?stack=aws&utm_source=api&utm_medium=response&utm_campaign=api_alerts&utm_content=incident"
    },
    "impactSummary": "AWS reported [resolved] increased connectivity issues in us-east-1 affecting Multiple services in the N. Virginia region.",
    "source": {
      "id": "source_aws_status",
      "kind": "official_api",
      "name": "AWS Health Dashboard",
      "checkedAt": "2026-11-17T10:00:13.905+00:00",
      "stale": false,
      "officialUrl": "https://health.aws.amazon.com/health/status",
      "statusPageUrl": "https://health.aws.amazon.com/health/status"
    },
    "updates": [
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t123802000z",
        "status": "investigating",
        "body": "We are investigating reports of Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are also impacted at this time.",
        "createdAt": "2026-11-15T12:38:02+00:00"
      },
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t131545000z",
        "status": "monitoring",
        "body": "We continue to investigate Connectivity issues in the US-EAST-1 Region. IAM Identity center sign-in requests and AWS SignUp are impacted at this time. \n\nWe can confirm errors when attempted to authenticate when using identity center or when using services that rely on IAM Identity center. For Kiro users, logins from social sign in methods are not impacted at this time. There are no workarounds for impacted customers.",
        "createdAt": "2026-11-15T13:15:45+00:00"
      },
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t132211000z",
        "status": "monitoring",
        "body": "We are seeing early signs of recovery for authentication via IAM Identity Center and SignUp.",
        "createdAt": "2026-11-15T13:22:11+00:00"
      },
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t142347000z",
        "status": "monitoring",
        "body": "We can confirm recovery for most AWS Services. We have fully mitigated the issue authentication errors from IAM Identity Center that was impacting Kiro, Connect, and other services which rely on IAM Identity Center for authentication.\n\nWe continue to investigate an issue that is affecting a subset of Network Load Balancers in a single cell, in a single Availability Zone (use1-az1) in the US-EAST-1 Region. For customers who need immediate resolution, we recommend creating a new NLB with targets in multiple Availability Zones. We are actively working on multiple parallel paths to mitigate the issue. We will provide an update by 7:30 AM, or sooner if we have additional information to share.",
        "createdAt": "2026-11-15T14:23:47+00:00"
      },
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t143256000z",
        "status": "monitoring",
        "body": "We are seeing significant signs of recovery and are continuing to monitor for full recovery.",
        "createdAt": "2026-11-15T14:32:56+00:00"
      },
      {
        "id": "update_aws_aws_multiple_services_operational_issue_7eb95_9acd11d39ce_20261115t145329000z",
        "status": "resolved",
        "body": "Between 3:05 AM and 6:10 AM PST we experienced signup errors, authentication issues, and connectivity issues in the US-EAST-1 Region. Customers using IAM Identity Center for authentication into the AWS Console, or for authentication into other AWS Services such as Kiro, Connect, etc would have been affected during this time. \n\nEngineers were automatically engaged at 3:10 AM PST and immediately began investigating the root cause, while in parallel working to mitigate both impacts. At 5:20, we fully mitigated the issue affecting authentication, and most AWS Services observed full recovery at this time. \n\nA subset of customers using NLB in a single cell in use1-az1 continued to experience connectivity issues until we fully mitigated the underlying issue at 6:21 AM PST. We recommend customers retry any failed requests. The issue has been resolved and all AWS Services are operating normally.",
        "createdAt": "2026-11-15T14:53:29+00:00"
      }
    ],
    "access": {
      "plan": "public",
      "keyed": false
    }
  }
}