Sorry Outage History
Sorry is up right nowPingoru has recorded 62 incidents for Sorry: 62 in the last 12 months and 33 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 8 | 350 of 720 (49%) |
| May 2026 | 10 | 601 of 744 (81%) |
| June 2026 | 4 | 82 of 720 (11%) |
| July 2026 | 7 | 74 of 744 (10%) |
| August 2026 | 7 | 47 of 744 (6%) |
| September 2026 | 4 | 34 of 720 (5%) |
| October 2026 | 20 | 3 of 519 (1%) |
Incidents, newest first
Major October 20, 2026 Degraded performance with the management UI 38m
Started Oct 20, 2026, 09:23 AM UTC· resolved Oct 20, 2026, 10:01 AM UTC
- investigating Oct 20, 2026, 09:33 AM UTC
Following this morning's [routine database maintenance](https://status.sorryapp.com/notices/6b1j81lztj0sz2wc-routine-database-maintenance), we are experiencing slower performance with the management UI at [app.sorryapp.com](https://app.sorryapp.com). We're looking into it now and will share an update as soon as we know more. We're sorry for any disruption.
- investigating Oct 20, 2026, 09:46 AM UTC
We've seen performance in the management UI at app.sorryapp.com improve. We'll keep monitoring for a little while before we resolve this notice. Thanks for bearing with us.
- resolved Oct 20, 2026, 10:01 AM UTC
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.
Major October 2, 2026 Behind-the-scenes improvements to subscriber preferences 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 01, 2026, 01:27 PM UTC
We’ve made some background changes to the way that subscribers are linked to components - this simplifies the amount of housekeeping we have to do when you make changes to your component tree, and also improves performance when building by-component breakdowns in the activity summary. There are no outward changes for customers, just an improvement to the underlying technology.
Major October 2, 2026 Your subscribers stay in the loop, even as your components evolve 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 03, 2026, 10:36 AM UTC
We've made an improvement that keeps subscriber notifications accurate whenever you add or move components on your status page. As you reorganise things over time, these changes could previously leave a subscriber's notification preferences slightly out of step with your new structure. Now we automatically keep everyone aligned with your latest layout, so they keep hearing about exactly the things they care about, and nothing they don't. **What this means for you and your subscribers** - **Add a Subcomponent:** anyone already following the parent automatically starts receiving updates about the newly added subcomponent. - **Move a Component:** subscribers keep receiving updates for whatever they initially chose to follow, wherever it now sits in your component structure. And if you delete a component, there's nothing to worry about — subscribers stay on your list and simply stop hearing about the part you removed. **Do I need to do anything?** No. This works automatically across your status pages, including changes made through the dashboard, the API, and when importing from another provider. Your subscribers' existing choices are always respected.
Major October 2, 2026 Fixed: Some team members unable to reorder components 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 14, 2026, 02:21 PM UTC
We resolved a bug that prevented some team members with restricted page access from saving changes when reordering components. Instead of applying the new order, the page displayed an error and left the components unchanged. Component reordering now works as expected for all team members with permission to manage the page.
Major October 2, 2026 Simpler status page component loading 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 20, 2026, 10:46 AM UTC
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.
Major October 2, 2026 Status API improvements for private pages 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 22, 2026, 06:47 PM UTC
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.
Major October 2, 2026 A small visual refresh for status page components 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Jul 31, 2026, 11:34 AM UTC
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.
Major October 2, 2026 A little groundwork for future improvements 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 07, 2026, 01:57 PM UTC
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.
Major October 2, 2026 Improved status page sitemaps 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 11, 2026, 09:21 AM UTC
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.
Major October 2, 2026 A little more status page groundwork 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 11, 2026, 03:36 PM UTC
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.
Major October 2, 2026 Keeping status pages secure and up to date 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 12, 2026, 09:23 AM UTC
We’ve updated some of the underlying technology that powers public status pages, keeping it aligned with current security and maintenance standards. It’s a behind-the-scenes improvement, so there’s nothing you need to do and no change to how your status page looks or works.
Major October 2, 2026 A few more behind-the-scenes improvements 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 12, 2026, 01:28 PM UTC
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.
Major October 2, 2026 A little speed boost for public status pages 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 18, 2026, 08:25 AM UTC
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.
Major October 2, 2026 Upgraded our Ruby on Rails platform 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 18, 2026, 11:48 AM UTC
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.
Major October 2, 2026 Finalised our Ruby on Rails platform upgrade 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Aug 20, 2026, 09:32 AM UTC
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.
Major October 2, 2026 Fixed: Maintenance message missing from the Status API 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Sep 01, 2026, 09:47 AM UTC
We’ve resolved a bug that caused the Status API’s state_text field to return null while a status page was under maintenance, even when a custom maintenance message had been configured. The API now returns the configured maintenance message as expected, consistent with operational and degraded states. No changes are needed to existing integrations.
Major October 2, 2026 Fixed: Slack notification fallback links 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Sep 02, 2026, 10:48 AM UTC
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.
Major October 2, 2026 Fixed: Notification delivery across enabled channels 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Sep 03, 2026, 09:04 AM UTC
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.
Major October 2, 2026 More control over notice archiving 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Sep 04, 2026, 01:49 PM UTC
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.
Major October 2, 2026 Fixed: Status page deletion 2h 23m
Started Oct 02, 2026, 12:27 AM UTC· resolved Oct 02, 2026, 02:50 AM UTC
- investigating Sep 08, 2026, 08:32 AM UTC
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.
Major September 14, 2026 Redesigned Component Management 7h 38m
Started Sep 14, 2026, 12:00 AM UTC· resolved Sep 14, 2026, 07:38 AM UTC
- investigating Jun 23, 2026, 08:41 AM UTC
We've rebuilt the component management experience from the ground up — it's faster, simpler, and designed to scale with you. **Find what you need** — Managing hundreds of components is now quick and effortless. A real-time search filter lets you find any component instantly, and if you use collections, each page now has its own dedicated view so you can work in a focused, uncluttered workspace. **Organise with confidence** — Reordering and moving are now separate, intentional actions. Drag to reorder within a level, or move a component to a new parent using a clear target picker that shows exactly where it will land. If you're deleting a component with sub-components, you'll be asked to confirm by typing its name, so nothing is removed by accident. **Edit with clarity** — Adding and editing components is simpler, with clean focused forms and at-a-glance visibility into which components display metrics like uptime and mean time to resolve. We hope you enjoy the new experience — as always, reach out if you have any feedback.
Major September 8, 2026 Fixed: Subscriber component preference displaying incorrectly 8h 27m
Started Sep 08, 2026, 12:09 AM UTC· resolved Sep 08, 2026, 08:36 AM UTC
- investigating Jun 19, 2026, 01:28 PM UTC
We resolved a bug where some subscribers set to receive notifications for "All components" were incorrectly shown as subscribed to "Only certain components" when editing them in the Management UI. This was a display issue only - no notifications were affected, and all subscribers continued to receive the correct alerts throughout.
Major September 3, 2026 Fixes and improvements to the Manage Preferences email 9h 3m
Started Sep 03, 2026, 12:03 AM UTC· resolved Sep 03, 2026, 09:06 AM UTC
- investigating Jun 02, 2026, 10:41 AM UTC
We just released a fix to the email which is sent to subscribers when they want to manage their subscription preferences. Before the fix, the email heading didn't correctly include the status page name, instead showing a placeholder. We also took this opportunity to rework the email copy to better align with the language of the subscriber journey. The email now uses the phrase "Manage Subscription" rather than "Sign-in" to better match the experience on the status page itself.
Major September 1, 2026 Subscriber Email Verification 9h 6m
Started Sep 01, 2026, 12:02 AM UTC· resolved Sep 01, 2026, 09:08 AM UTC
- investigating May 20, 2026, 09:50 AM UTC
New subscribers to your status page now go through a double opt-in process — verifying their email address before they receive any notifications. When someone subscribes, they'll receive a confirmation email with a link to verify their address. Once they click it, they're verified and will start receiving your status updates. Subscribers who don't confirm within 30 days are automatically removed. **Why this matters:** - **Spam compliance** — double opt-in is a best practice for mass notification senders, ensuring you only contact people who genuinely want to hear from you - **Better deliverability** — fewer bounces and invalid addresses protect your sender reputation - **Cleaner subscriber lists** — spam signups and typos are filtered out before they ever receive a notification You'll see unverified subscribers in your subscriber list marked as such, so you always have full visibility into who's confirmed and who's still pending. Subscribers added through the API, CSV import, or your management dashboard are verified automatically — confirmation is only required when someone subscribes directly on your status page. This is enabled for all accounts and requires no configuration on your part.
Major August 20, 2026 Automatic Notice Archiving 9h 18m
Started Aug 20, 2026, 12:16 AM UTC· resolved Aug 20, 2026, 09:35 AM UTC
- investigating May 15, 2026, 11:24 AM UTC
Old notices on your status page are now automatically archived after a configurable time period. Once archived, notices become visible only to your team — keeping your status page clean and focused on what matters most. **What's new:** - Notices older than your chosen threshold are automatically archived - Archived notices are only visible to your team. Anyone else viewing your status page won't see them. - Your team retains full access on the status page when logged in, and in the management dashboard - A 3-year default has been applied to all existing pages [Learn more in our help center](https://help.sorryapp.com/article/185-notice-archiving)