rewindex

CompaniesNetlifyIncidents

Netlify: Agent Runner failures

MajorStatus: resolvededitedStarted Resolved (1.1 h)3 updatesstspg.io (opens in new tab)
Summary

Netlify reported increased Agent Runner failures affecting Agent Runners, with major impact, starting at 2026-10-20 07:47 UTC. The incident was still open when archived, with 0 min elapsed at the last update; Netlify was investigating and had not stated a cause or fix.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Part of an outage event

Google Cloud europe-west2 outage, Oct 20, 2026 · 19 vendors, 19 incidents

Netlify’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h 39 min vs Google Cloud’s own post)

Swipe sideways to see the whole diagram.

same windowGoogle Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed Google CloudJFrogWithin an hour4 vendors, 4 blamed Google CloudAiven, Northflank, Elastic Cloud, dbt Labs1 to 4 hours later4 vendors, 4 blamed Google CloudMongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse CloudLater2 vendors, 1 blamed Google CloudGrafana Cloud, ConfluentNetlify (this incident)posted +1 h 39 min
same windowGoogle Cloud europe-west2posted 06:08 UTCPosted before Google Cloud did1 vendor, 1 blamed GoogleCloudJFrogWithin an hour4 vendors, 4 blamed GoogleCloudAiven, Northflank, Elastic Cloud,dbt Labs1 to 4 hours later4 vendors, 4 blamed GoogleCloudMongoDB Atlas, Sourcegraph,CockroachDB, ClickHouseCloudLater2 vendors, 1 blamed GoogleCloudGrafana Cloud, ConfluentNetlify (this incident)posted +1 h 39 min
Netlify is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Google Cloud europe-west2<br/>posted 06:08 UTC"]:::root
  before["Posted before Google Cloud did<br/>1 vendor, 1 blamed Google Cloud<br/>JFrog"]:::blames
  root --> before
  h1["Within an hour<br/>4 vendors, 4 blamed Google Cloud<br/>Aiven, Northflank, Elastic Cloud, dbt Labs"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed Google Cloud<br/>MongoDB Atlas, Sourcegraph, CockroachDB, ClickHouse Cloud"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 1 blamed Google Cloud<br/>Grafana Cloud, Confluent"]:::blames
  root --> later
  me["Netlify (this incident)<br/>posted +1 h 39 min"]:::me
  root -.->|"same window"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Agent Runners

Timeline of updates

  1. investigating

    We are investigating increased Agent Runner failures. We will share updates as we learn more.

  2. monitoring

    We are monitoring the incident.

  3. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Netlify profileRecent Netlify incidentsMarkdownJSON