Deploying from GitLab may intermittently fail
DegradedThis incident has been resolved.
Render is up and running. Render hosts web services, databases and static sites.
Worked out from the incidents Render reported, so it is an estimate and not a measurement.
Last incident: “Deploying from GitLab may intermittently fail”, today.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Render’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Render reported was “Deploying from GitLab may intermittently fail”, today (2026-10-20 20:48 UTC). None of its incidents in the last 90 days were a full outage.
Render reports 57 components on its status page, including Render Dashboard, Web Services, Web Services, Web Services, Web Services. Each is checked again whenever this page refreshes.
Pause deploys that depend on it, queue or retry failed jobs once it recovers, and check whether a mirror or cache can cover the gap.
Normal during a build incident: 'Builds and Deploys' is a separate per-region component from 'Web Services', so it doesn't restart or stop running services.
Only services attached to a database in that region. Render tracks Postgres per region separately from web services — a database incident in Oregon doesn't touch a web service in Frankfurt unless it connects to that database.
If the status above is operational but Render still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.