Render: SLA evidence report
Render: SLA evidence report
We hold no probe record for Render: we read its status page, so the only incident record here is what Render declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Render declared
- 7
- On its own status page, in this window.
- Window
- 2026-09-22 to 2026-10-22
- UTC, 30 days.
Sep 23, 2026, 11:30 PM UTC to Sep 23, 2026, 11:30 PM UTC
Key Value service restarts, impact minor
Sep 25, 2026, 6:26 PM UTC to Sep 25, 2026, 6:38 PM UTC
Build and deploy failures in Oregon, impact major
Sep 27, 2026, 1:24 AM UTC to Sep 27, 2026, 3:01 AM UTC
Observing service instability from our upstream provider AWS in Oregon region, impact minor
Oct 3, 2026, 7:35 PM UTC to Oct 3, 2026, 8:21 PM UTC
Degraded Dashboard Performance; Degraded builds & deploys in Oregon, impact minor
Oct 14, 2026, 7:32 PM UTC to Oct 14, 2026, 10:18 PM UTC
Builds, deploys, and queued deploys are not starting in all regions, impact major
Oct 15, 2026, 8:58 PM UTC to Oct 15, 2026, 10:33 PM UTC
Dashboard not updating in real time; Some Workflows SDK requests timing out, impact minor
Oct 20, 2026, 8:48 PM UTC to Oct 21, 2026, 12:29 AM UTC
Deploying from GitLab may intermittently fail, impact minor
Methodology
These incidents come from Render's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Render owes, if any, is decided under its own SLA.