When you push code, a short list of questions follows. Which commit is serving traffic? Did the deploy go through? If it didn't, what went wrong? Every Render service has a new Deploys page built to answer exactly those.
Deploys is the page you land on when you open a service, and Events now sits under Monitoring, still showing every service event including deploys.
The page carries your last 30 deploys regardless of age, so a service last deployed three years ago still has a history worth reading. A Live badge marks the deploy serving traffic right now, which is not always the newest one. If a later deploy failed or is still building, the badge stays on the deploy actually serving traffic.
Click any deploy to open its details. A Notices panel collects the context for that one: "Exited with status 1 while building your code," a health check that never passed, whatever applies, in a single place.
Roll back and Render tells you up front that auto-deploy is going off. Manually deploy a specific commit and auto-deploy goes off as well. The Deploys page carries a banner afterward, and so does Events. The banner links straight into deploy settings when you want it back on.
Cron jobs get Builds and Runs as separate pages, which keeps build history and run history apart.
See it in action
Speed came from the layer underneath
Render service builds now run on nodes with faster CPU and disk, and median service build time fell from 38 seconds to 21 seconds over the summer, a 40% reduction in the median measured across all runtimes. The changelog entry has the week by week numbers and the per-runtime breakdown.
More on the path from code to production
Faster builds and the Deploys page are aimed at the same thing: making it simpler to get code to production, and simpler to see what happened when you did. There is more coming on that path. Read the docs on deploys to get started!