32 Sorry incidents · Mart 2026 — official updates, affected components, duration and resolution details.
Bazı takım üyelerini sipariş bileşenleri sırasında tasarruf değişikliklerinden sınırlı sayfa erişimine engelleyen bir otobüs çözdük. Yeni siparişi uygulamak yerine, sayfa bir hata gösterdi ve bileşenleri değişmeden bıraktı. Bitirme şimdi sayfayı yönetmek için izinli tüm takım üyeleri için beklendiği gibi çalışır.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
İzlememiz, son 30 dakika boyunca istikrarlı olmanın hizmeti gösterdi ve Yardım Merkezi tamamen mevcut. Sabrınızı takdir ederiz, bu konu araştırılmış ve çözülürken.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Maintenance is complete. No downtime occurred during the cache updates.
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.
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.
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.
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.
Between **21:50 and 23:35 UTC**, lasting approximately **1 hour and 45 minutes**, some emails sent through **Email by Sorry** were delayed. During this short window, some Sorry customers may have seen delays in emails being received by their subscribers. This included: - subscription confirmation emails - subscription magic links - incident notice notifications Customers using other email providers connected to Sorry, were not affected. The delays were caused by an issue with **Postmark**, the email delivery provider used by Email by Sorry. While the issue was outside of Sorry’s infrastructure, the impact was that some emails sent via Email by Sorry were delivered later than expected. Once Postmark resolved the issue, delayed messages were delivered and email delivery returned to normal. No customer action is required. We’re sorry that these emails arrived late. We know that delayed confirmation emails, magic links, and incident notifications are frustrating for both you and your subscribers, especially when people are expecting them to arrive right away. Further details are available on [Postmark's status page](https://status.postmarkapp.com/notices/cjagqohtofnqt9ts-email-sending-delays).
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.
The issue affecting our X/Twitter integration has now been resolved and notices are once again being published normally. Thank you for your patience while we worked on this. All notification and message delivery channels are now operating as expected.
Starting on May 12th, following the [release of our notice archiving feature](https://status.sorryapp.com/notices/ka9bfnq7spwssppy-automatic-notice-archiving) we saw a slow-down in the performance of uptime calculations - this was introduced by a change in the calculation that conditionally included archived notices based on who was viewing the status page. This was primarily impacting requests on the Status API, and likely wasn't noticeable to everyday users. We have now fixed the issue, so performance has returned to it's usual speed.
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.
The maintenance has now been completed. We’ve double-checked everything and can confirm that all services are working just as they should. Thanks for your patience!
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)
We no longer inject Google Analytics or Google Tag Manager into Error, Maintenance or 404 pages. This will help prevent white-noise from these bad requests from polluting your real visitor data.
We have just released some behind-the-scenes changes to the status page theme, cleaning up the code and making some minor performance improvements before adding new features in the coming weeks.
For the few customers using our experimental metrics rules to control who can see uptime on the status page, we have added a new preconfigured "Team" audience that lets you easily limit visibility to people on your team, without needing to build a custom rule that matches by email addresses or domains. This is also part of the foundation work we're building for our new notice archiving feature.
We've just released some improvements to the way that a notice's position in the timeline is calculated. (future, present, past) This has no outward impact on customers, but does gain us a slight performance improvement. The main motivation however is laying the groundwork for an upcoming feature that allows you to archive old notices. Watch this space.
The maintenance is now complete. Thanks for your patience.
We've added a new notice type to your status page. General Notices let you share updates that aren't incidents or maintenance — things like release notes, security advisories, domain changes, or end-of-life announcements. They're simpler than other notice types: no status to track, no timeline to manage. Write your message, optionally tag it to categorise it (e.g. "New Feature", "Security", "Bugfix"), and post. You can notify subscribers when posting a General Notice across all your configured channels. Create them from the dashboard using the dropdown on the "New Notice" button, or through the API.