Sorry 장애 기록

1. 2026년 9월 8일 AM 8:32 UTCinvestigating

   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.

1. 2026년 9월 4일 PM 1:49 UTCinvestigating

   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.

1. 2026년 9월 3일 AM 9:04 UTCinvestigating

   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.

1. 2026년 9월 2일 AM 10:48 UTCinvestigating

   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.

1. 2026년 8월 20일 AM 9:32 UTCinvestigating

   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.

1. 2026년 8월 18일 AM 11:48 UTCinvestigating

   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.

1. 2026년 8월 18일 AM 8:25 UTCinvestigating

   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.

1. 2026년 8월 12일 PM 1:28 UTCinvestigating

   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.

1. 2026년 8월 11일 PM 3:36 UTCinvestigating

   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.

1. 2026년 8월 11일 AM 9:21 UTCinvestigating

   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.

1. 2026년 8월 7일 PM 1:57 UTCinvestigating

   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.

1. 2026년 8월 3일 PM 4:03 UTCresolved

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

1. 2026년 7월 31일 AM 11:34 UTCinvestigating

   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.

1. 2026년 7월 22일 PM 6:47 UTCinvestigating

   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.

1. 2026년 7월 20일 AM 10:46 UTCinvestigating

   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.

1. 2026년 7월 14일 PM 2:21 UTCinvestigating

   우리는 재주문 부품이 될 때의 변경에서 제한된 페이지 액세스에서 일부 팀 구성원을 방지하는 버그를 해결했습니다. 새로운 순서를 적용하는 대신, 페이지는 과실을 표시하고 unchanged 분대를 떠났습니다. Component reordering now works as expect for all team member with permission to manage the page.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 14일 PM 1:05 UTCresolved

   우리의 모니터링은 지난 30 분 동안 안정 될 수있는 서비스를 보여주고, 도움말 센터는 완전히 사용할 수 있습니다. 우리는이 문제를 조사하고 해결 한 동안 당신의 인내력을 평가합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 3일 AM 10:36 UTCinvestigating

   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.

1. 2026년 7월 1일 PM 1:27 UTCinvestigating

   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.

1. 2026년 6월 23일 AM 8:41 UTCinvestigating

   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.