What's new
Everything that's shipped, newest first. Looking for what's coming next instead? See the roadmap.
September 10, 2026
Stronger password requirements
Passwords now require a minimum of 8 characters, enforced both when you sign up and whenever you set a new one.
Status page incidents show who resolved them
Every update on one of your organization's own status page incidents now shows who posted it, and the incidents list shows who actually resolved each one, not just when.
Reports now include uptime monitor downtime, not just heartbeats
The Downtime incidents figure on both the Reports page and the scheduled report email was only ever counting missed heartbeats. It now includes downtime detected by uptime monitors too, so the number actually matches what it's labeled.
PII scrubbing, shown with a real example
The PII scrubbing page now shows an actual redacted issue, not just a description of the rules: an email address and an api_key field both caught and replaced before storage, sitting right next to an unrelated field that's correctly left untouched.
Report a caught exception, with full context, in every language
Code that catches its own error to keep running (a third-party API call, an SFTP upload, a webhook post) never used to reach ForgeOps at all, since nothing ever crashed. Every SDK now exposes a direct capture call for exactly that, right at the catch/rescue/except site, with a context hash that shows up as inspectable JSON on the issue. See it for your own language on the new Handled exceptions page.