rewindex

RewindexOutage eventsSep 27, 2026

AWS outage, Sep 27, 2026

4 linked vendors posted 4 incidents between and . 4 vendors named AWS in 4 incidents (2 of them blamed it). Vendors reported an AWS outage; AWS’s own incident for this date is not in the archive. 2 other vendors had incidents in the same window; nothing links them to AWS (listed below).

Observed, not verified. A line means a vendor’s incident named another vendor, or a known dependency (declared by the vendor and named as a cause before). It is not a proven cause. Incidents that only share the time window are listed apart.

Times are in UTC; lags are from when the first vendor named AWS.

    3. first vendor named AWS
Named AWSNamed another vendor or depends on oneEach column is 30 minutes

How it spread

Vendors that named AWS, grouped by when they posted, and vendors that blamed one of the vendors AWS took down. Solid lines: the vendor named the other. Dashed: a known dependency, not named in the incident.

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour4 vendors, 2 blamed AWSTemporal Cloud, Figma, Render, Front
AWSown incident not archivedWithin an hour4 vendors, 2 blamed AWSTemporal Cloud, Figma,Render, Front
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 2 blamed AWS<br/>Temporal Cloud, Figma, Render, Front"]:::blames
  root --> h1

Vendors that named AWS

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

4 vendors

  • +0 min

    Names AWS

    Minor incident

    Temporal CloudIncreased latency in region us-west-2

    …Increased latency in region us-west-2 The issue is resolved and service is operating normally. Between 00:32 and 01:03 UTC, some namespaces in AWS us-west-2 saw increased API latency and errors. This…

  • +3 min

    Blames AWS

    Critical incident

    FigmaService disruption

    …gating an issue where Figma Services are degraded or unavailable because of failures with AWS and other dependencies.…

  • +23 min

    Blames AWS

    Minor incident

    RenderObserving service instability from our upstream provider AWS in Oregon region

    …Observing service instability from our upstream provider AWS in Oregon region This incident has been resolved. All services, except for the free web services tier, have recovered. We continue to monit…

  • +48 min

    Names AWS

    Minor incident

    Front[us-west-2] Elevated API error rates may cause delays

    …[us-west-2] Elevated API error rates may cause delays The upstream issues causing delays in our system have been resolved. Our team is currently investigating elevated API error rates that may cause d…

Also happening at the same time (not linked)

2 incidents from 2 vendors started in this window without naming AWS or a linked vendor, and with no known dependency on them. Listed for context only; they are not counted as part of the event (an ordinary week has about 1 incidents in these hours).

Show all 2

Detected automatically from 6 status pages opening incidents in the peak hour (normally at most 9). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.