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

Customers in AWS us-west-2 may experience elevated API latencies

Reported by Temporal Cloud · Developer Tools & CI/CD · source last read just now

Official source (opens in a new tab)
Vendor start
Aug 13, 2026, 11:47 UTC
Vendor's clock
Resolved
Aug 13, 2026, 12:27 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
40 min
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

  • Temporal Cloud reports degraded: "Customers in AWS us-west-2 may experience elevated API latencies".[E1, E2]
  • The vendor marked it resolved at 2026-08-13 12:27 UTC.[E3, E7]

Affected products and regions

  • Regions: us-west-2 (read from the title, so inferred).[E5]
  • Components: us-west-2.[E6]

What is unknown

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

Last update in these facts: 2026-08-13 12:27 UTC · summary s1, evidence db04e1bb4569ab3d

Evidence (7)
  1. E1Temporal Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Customers in AWS us-west-2 may experience elevated API latencies". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-13 11:47 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-west-2. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: us-west-2. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-13 12:27 UTC. (vendor) source (opens in a new tab)

Affected scope

us-west-2

Components: us-west-2

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

Potential relevance

Temporal Cloud 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. Aug 13, 2026, 11:47 UTCVendor-reported startVendor time
  2. Aug 13, 2026, 12:27 UTCVendor-reported resolutionVendor time

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