Vendor reports: degradedResolved · vendor status “resolved”Official status API

AWS Incident Reference: Ongoing service disruption in us-east-1 region

Reported by Kong Konnect · Developer Tools & CI/CD · source last read just now

Official source (opens in a new tab)
Vendor start
Oct 20, 2025, 07:11 UTC
Vendor's clock
Resolved
Oct 21, 2025, 14:13 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 7 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Kong Konnect reports degraded: "AWS Incident Reference: Ongoing service disruption in us-east-1 region".[E1, E2]
  • The vendor marked it resolved at 2025-10-21 14:13 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: Kong Konnect Cloud.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-10-21 14:13 UTC · summary s1, evidence 688d2b9f4d5ac375

Evidence (7)
  1. E1Kong Konnect reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "AWS Incident Reference: Ongoing service disruption in us-east-1 region". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-10-20 07:11 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Kong Konnect Cloud. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-10-21 14:13 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: Kong Konnect Cloud

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Kong Konnect is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 20, 2025, 07:11 UTCVendor-reported startVendor time
  2. Oct 21, 2025, 14:13 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.