Outages and root causes.

Two years of public outages, and what each company said caused them. Every entry links to the company's own write-up; nothing here is our speculation.

Status pages re-read 19 min ago

Incidents listed

By month, last two years · Render

Peak 6 · July 2026

Incidents listed: 21; Last two years
Official write-ups: 1; Linked from the incident
Major outages: 4; As graded by each company
Services: 1; With at least one entry

Notable outages, summarised

Read from each company's published analysis and summarised in our own words. Follow the link for the full account.

Render
Mar 26, 2024
All workloads restarted platform-wide
Every customer and system workload on Render was restarted at once across all regions; simple services recovered in about 20 minutes, but databases and services with disks took up to nearly four hours.
Root cause, as stated by Render
A faulty code change, which a bug in feature-flag handling had kept from being exercised in non-production environments, caused a restart of all workloads.
Read the official analysis (opens in a new tab)Report an error (opens a correction request in a new tab)

From the status pages

With a published RCA Partial and major outages Both

Render · Builds, deploys, and queued deploys are not starting in all regions
Partial outage · Oct 14, 2026 · 2 h 45 min
Read the RCA (opens in a new tab)
Render · Build and deploy failures in Oregon
Partial outage · Sep 25, 2026 · 12 min
Incident report (opens in a new tab)
Render · Degraded builds/deploys
Partial outage · Sep 2, 2026 · 21 min
Incident report (opens in a new tab)
Render · Service instability in Singapore
Partial outage · Aug 31, 2026 · 2 h 22 min
Incident report (opens in a new tab)
Render · Deployment Issues
Partial outage · Aug 20, 2026 · 3 h 53 min
Incident report (opens in a new tab)
Render · Service Disruption in Oregon
Major outage · Jul 24, 2026 · 2 h 14 min
Incident report (opens in a new tab)
Render · GitHub git clone 403 errors
Major outage · Jul 19, 2026 · 5 h 36 min
Incident report (opens in a new tab)
Render · GitHub outage affecting new service creation and service deploys
Major outage · Jul 16, 2026 · 1 h 33 min
Incident report (opens in a new tab)
Render · Some users enrolled in 2FA are experiencing login issues
Partial outage · Jul 15, 2026 · 1 h 6 min
Incident report (opens in a new tab)
Render · Render Dashboard Unavailable
Major outage · Jul 15, 2026 · 32 min
Incident report (opens in a new tab)
Render · Some services and datastores in Singapore experiencing brief disruptions
Partial outage · Jul 9, 2026 · 26 min
Incident report (opens in a new tab)
Render · Issues with GitHub connections
Partial outage · Jun 5, 2026 · 53 min
Incident report (opens in a new tab)
Render · Emails, including notifications, are delayed
Partial outage · Jun 4, 2026 · 1 h 12 min
Incident report (opens in a new tab)
Render · Unable to load metrics for some services in Oregon
Partial outage · Jun 1, 2026 · 20 min
Incident report (opens in a new tab)
Render · Upstream provider outage causing delays provisioning custom domains
Partial outage · May 22, 2026 · 44 min
Incident report (opens in a new tab)
Render · Logs unavailable for some services in all regions
Partial outage · May 12, 2026
Incident report (opens in a new tab)
Render · Certificate issuance paused for Let's Encrypt
Partial outage · May 8, 2026 · 44 min
Incident report (opens in a new tab)
Render · HA Postgres Unavailability
Partial outage · May 7, 2026 · 54 min
Incident report (opens in a new tab)
Render · Some web services and databases in Oregon are unresponsive
Partial outage · Apr 16, 2026 · 14 min
Incident report (opens in a new tab)
Render · Image pull failures in Oregon
Partial outage · Apr 13, 2026 · 24 min
Incident report (opens in a new tab)
Render · Disruption affecting the provisioning of new instances in Singapore and partially in Oregon
Partial outage · Apr 8, 2026 · 12 h 14 min
Incident report (opens in a new tab)

Who publishes root causes

Write-ups posted on status pages, last two years

Public information only

Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.

Sources

Official status pages: incident titles, severity, times and the link to each published root-cause analysis, exactly as each company posted them
Company engineering blogs and incident reports: the basis for the notable-outage summaries, each linked from its card

How fresh it is

Incidents and RCA links: re-read from every status page about once an hour; last run 19 min ago
Notable-outage summaries: written by hand and last checked against their sources on Nov 10, 2026

Titles, severity and times are as published on each company's status page. "Published RCA" means the company posted a postmortem on that incident's official page; we link to it and do not reproduce it. Many companies publish root causes on a blog instead, or not at all, so the absence of a link is not evidence that no analysis exists. Severity grading differs between companies and is not comparable across them. This is not a complete record of every outage.