Rewindex

CompaniesRenderIncidents

Render: Some services in the Frankfurt region are experiencing elevated 502s

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.render.com (opens in new tab)
Part of an outage event

AWS outage, Jul 13, 2021 · 5 vendors, 5 incidents

Render’s incident blames AWS as the cause. (hop 1, posted +18 min vs the first vendor naming AWS)

“…furt region are experiencing elevated 502s Some services experienced 502s due relating to AWS connectivity issues. https://status.aws.amazon.com/#EU_block…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSConfluent, RenderRender (this incident)posted +18 min
AWSown incident not archivedWithin an hour2 vendors, 2 blamed AWSConfluent, RenderRender (this incident)posted +18 min
Render 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/>2 vendors, 2 blamed AWS<br/>Confluent, Render"]:::blames
  root --> h1
  me["Render (this incident)<br/>posted +18 min"]:::me
  h1 --- 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

    Some services experienced 502s due relating to AWS connectivity issues. https://status.aws.amazon.com/#EU_block

From Render’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 status.render.com (opens in new tab).

Render profileRecent Render incidentsMarkdownJSON