Sorry outage history

We’ve added a confirmation step when subscribers change their email address, helping ensure your status updates reach the right person. Subscribers receive a confirmation email at their new address. Their original address stays in use until they confirm, so they can keep receiving updates while the change is pending. Their notification preferences and Component selections carry over. Subscribers can resend the confirmation email or cancel the change from their subscription preferences. Once the change is complete, we’ll also notify their previous address.

We’ve updated unsubscribe links in notification emails to follow the usual sign-in requirements for private status pages. After signing in, subscribers are taken straight to their preferences.

We’ve made it easier to review which Components your subscribers want updates about. In the subscriber list, click a subscriber’s Component count to open a searchable view of their selections. This replaces the flat list previously shown on hover, keeping Components organised under their pages and groups. Search highlights matching names and shows how many Components match, helping you find a particular selection without scrolling through a long list.

We’ve improved how Sorry handles incoming requests, reducing waiting times during busy periods. This builds on the performance fix released following this morning’s incident.

Performance in the management UI at app.sorryapp.com is back to normal, so we're resolving this notice. Thanks for your patience, and sorry for the disruption.

We’ve fixed an issue that could prevent a status page from being deleted if a team member had previously collapsed or dismissed its getting-started checklist. Affected pages can now be deleted as expected.

You can now archive past notices manually, without waiting for your automatic archive settings to take effect. This gives you more control over your status-page history without deleting the original notices. Choose Archive Notice from a notice’s actions menu, either in the notice list or when editing it. Archived notices stay in their usual position in your dashboard, clearly marked, so they’re easy to find again. You can also choose Unarchive Notice to restore a notice to your status-page history - including notices that were archived automatically. Your existing automatic archiving continues to work as before - there’s nothing new to configure.

We’ve fixed an issue where subscribers with a deactivated email address could be excluded from status updates entirely, even when they had another notification channel enabled. Updates will now continue through their other eligible channels, while delivery to the deactivated email address remains suppressed. Existing channel and Component preferences continue to apply. No action is needed.

We’ve fixed a bug where the fallback text for some Slack notifications could include a subscriber-specific Access Link, even though the visible message used the public status page link. Both parts of the notification now use the same public link.

We’ve completed the final stage of our recent Ruby on Rails platform upgrade. Following a careful rollout and monitoring period, all parts of the upgrade are now active in production and performing normally. This work strengthens the foundations of Sorry and prepares the platform for further improvements. No action is required from customers.

Today we completed an upgrade of the Ruby on Rails framework that powers Sorry™. This is a behind-the-scenes change with no intended visible impact for customers. Before switching production traffic, we ran our automated test suite against both framework versions, completed manual QA in staging, and monitored the upgrade under live production traffic. Performance and error rates have remained normal. Completing this work provides a stronger foundation for future platform improvements, allowing us to adopt newer framework capabilities through smaller, safer upgrades.

We’ve made a handful of behind-the-scenes improvements to help public status pages load more quickly, with the biggest gains on pages with a long notice history. There’s nothing you need to do and no change to how your page looks or works — it should simply feel a little snappier.

We’ve made another small batch of improvements to how status page metrics and uptime are calculated. There’s nothing you need to do, but it gives us a sturdier foundation for future updates while helping status pages remain accurate and responsive.

We’ve rolled out another set of behind-the-scenes improvements to how status pages work out their current status and choose which recent notices to display. You shouldn’t notice any big changes just yet, but it gives us a tidier foundation for some improvements we’re working towards. We’ve also been keeping a close eye on performance throughout, and everything is looking nice and steady.

We’ve improved how public status pages are presented to search engines. Large pages with lots of components or a long notice history now use smaller, more focused sitemaps, making them faster and more reliable to process. We’ve also refined which content is included, prioritising the most useful public pages and adding the Status API guide. There’s nothing you need to do—these improvements will be applied automatically.

We’ve shipped a few behind-the-scenes changes to prepare status pages for some future improvements. Along the way, we’ve expanded our automated performance checks to cover larger, busier pages and more real-world scenarios. This should help us spot potential slowdowns earlier and keep status pages running smoothly as we continue to build. There’s nothing you need to do — it’s simply some useful groundwork for what’s coming next.

The management UI has remained stable, and this incident is now resolved. Thank you for your patience while we worked to restore normal service

We’ve made a small visual update to component lists on status pages. Clearer chevrons make it easier to see which components can be expanded, and component descriptions now have a tidier icon. There’s nothing you need to do, the changes will appear automatically.

We’ve given the Status API a bit of a tidy-up. Most importantly, it now works properly with private status pages, so you can securely use the API without making your page public. We’ve also refreshed the API documentation with clearer, copy-and-paste cURL examples and a few visual tweaks to make everything easier to follow. If you have a private status page, sign in and visit its API page to find your authentication details and updated examples. Existing API integrations will continue working as before.

We’ve simplified the way components load on status pages. It’s a behind-the-scenes improvement, so there’s nothing you need to do and no change to how your status page works.