Rewindex

CompaniesNetlifyIncidents

Netlify: Increased errors and latencies on the High-Performance Edge Network

MinorStatus: resolvedStarted Resolved (2.1 h)1 updatewww.netlifystatus.com (opens in new tab)
Part of an outage event

AWS outage, Aug 29, 2024 · 14 vendors, 14 incidents

Netlify’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 1 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepNetlify (this incident)posted +1 h 1 min
same windowAWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSSegment, Ably, Front1 to 4 hours later2 vendors, 1 blamed AWSConfluent, SemgrepNetlify (this incident)posted +1 h 1 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["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Segment, Ably, Front"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Confluent, Semgrep"]:::blames
  root --> h4
  me["Netlify (this incident)<br/>posted +1 h 1 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.

Timeline of updates

  1. resolved

    This incident has been resolved.

From Netlify’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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

Netlify profileRecent Netlify incidentsMarkdownJSON