Sorry Outage History

We identified a deployment released at 14:15 UTC as the cause of the management UI loading slowly or failing to load. The deployment was rolled back at 15:01 UTC, and the UI has since recovered. We’re currently monitoring the service to ensure it remains stable. The cause of the deployment failure will be analysed as part of our internal post-incident review.

We've made performance improvements to how component metrics are loaded on your status pages. Pages with uptime metrics enabled will now load noticeably faster, particularly for status pages with larger component trees. These improvements apply across the board - your status page, notices, and the status API all benefit from the faster loading times. No action is needed on your part, the improvements are already live.

We've redesigned how you create notices from the dashboard to make it faster to post the right type of update. The "New Notice" button in the navigation bar now includes a dropdown menu that lets you jump straight into creating a specific notice type — **Incident**, **Maintenance**, **Historic**, or **General** — with the form pre-filled to the right settings. Previously, shortcuts for creating notices were tucked inside the timeline sections on the notices page. This new approach puts them all in one consistent place, always accessible regardless of which page you're on. The primary button still works exactly as before — click it to open the notice form and choose your type from there.

If you're using general notices to share updates with your users, those notices are now included in your Status API responses. General notices will appear alongside your existing planned and unplanned notices when listing notices via `/api/v1/notices`, and can be retrieved individually via `/api/v1/notices/:id`. You can also filter for them specifically using `?filter[type_eq]=general`. Since general notices don't have a lifecycle like incidents or maintenances, their API payload is a little leaner — fields like `state`, `began_at`, and `ended_at` are omitted. Full details are available on the API documentation tab of your status page.

We have significantly improved the performance of activity reports for accounts with large numbers of subscribers and components. Reports that previously took several seconds to load should now render much more quickly. No changes to how reports work — just faster results.

We've been alerted by our monitoring systems that the **Sorry™ Help Centre** is currently unavailable. If you need to get in touch with us, you can still contact our team using the in-app beacon or by emailing **[email protected]**. We're monitoring the situation closely and will share updates as soon as we receive more information from our service provider, Help Scout. Thank you for your patience.

Our monitoring, along with confirmation from Help Scout, shows that the issue has recovered and the Sorry™ Help Centre is now available again. We'll continue to monitor the service and, if everything remains stable, we'll resolve this incident shortly.

We have resolved an issue where adding a new team member could fail with a timeout error on accounts with a large number of status pages. Team members are now added instantly, with their page access being set up seamlessly in the background. No action is needed on your part.

The activity report for page collections was undercounting subscribers. Subscribers who had selected specific child components — but not every component under a page — weren't being included. These counts now accurately reflect all subscribers, regardless of how granular their component selections are.

We just released some under-the-hood changes to how we generate and store data for the new Activity Summary, in preparation for a bunch of new features landing in the near future.

SSL certificates for newly added custom domains sometimes failed and were not retried, leaving new customers with a certificate error during setup. We have made this provisioning more resilient, so it should no longer impact people as often.

We’re currently experiencing issues with our X/Twitter integration, which means notices are not being published there at this time. All other notification and message delivery channels are operating normally while we investigate the issue.

We've made a couple of small fixes to the Activity Summary shown at the top of your notice timeline: - Fixed an alignment issue where tile values appeared centered when there was no detailed breakdown to display. Values now consistently align to the left across all tiles. - Renamed the "Notices" tile to "Notices Created" to make it clear the count reflects notices created within the last 30 days.

We have patched an issue that was preventing some customers from completing the configuration flow when installing our Intercom Messenger App. This primarily affected accounts with multiple status pages. The app should now configure successfully for all accounts.

Your dashboard now features an Activity Summary — a quick snapshot of what has been happening on your status page over the last 30 days. At a glance, you will see: - **Notices published** — broken down by incidents and maintenance - **Notifications sent** — with a breakdown of your most-used channels - **Subscriber count** — including how many new subscribers joined recently The summary appears automatically on your Notice Timeline when there is recent activity, so you always have a pulse on how your status page is performing — without leaving your management console. This is just the beginning — we have plans to bring you even more insights into your status page activity. Stay tuned!

You can now permanently dismiss the onboarding setup tasks from your status page dashboard. If you have completed your setup, or simply prefer a cleaner workspace, click Dismiss to hide them for good. We have also improved how the hide/show toggle works. Previously, collapsing the setup tasks only lasted for your current browser session. Now your preference is saved to your account, so the panel stays how you left it even if you switch browsers or clear your cache.

We have added a 24-hour cooling-off period when deleting established status pages. Previously, deleting a status page was instant and irreversible. Now, when you delete a page that has built up subscribers and incident history, the deletion will be scheduled rather than happening immediately. Smaller or newly created pages will continue to be deleted straight away, so this will not slow you down during initial setup. This applies to standalone pages, collections, and individual pages within a collection.

We deployed some small changes to how we enable custom HSTS (Strict-Transport-Security) headers for particular status pages. This is a behind-the-scenes improvement and does not impact customers.

We have resolved an issue where magic link authentication responses were being cached by our CDN, which could cause links to fail after being accessed by email security bots. All magic links now work reliably on every click.

Customers were occasionally seeing errors when trying to delete incidents for which someone had previously removed the uptime impact. You may also have seen this error when deleting a page which contained an affected notice. This was a behind-the-scenes database constraint issue that has now been fixed.

We have a known bug that causes users to receive errors when trying to delete a notice that has an uptime impact they previously removed. We have just released the initial groundwork required to fix this bug, with the full fix to follow. This release changes how we track when and by whom an uptime impact was removed from a notice under the hood, without any visible changes to customers.

We have fixed an issue where importing from Atlassian Statuspage could fail with an unhelpful error message when there was a problem with your credentials. Now when you import from Atlassian Statuspage, you will see clear, actionable error messages if: - Your API Key does not have permission to access the specified Page ID - We are unable to connect to Atlassian Statuspage due to a temporary issue This makes it much easier to troubleshoot and resolve any issues when setting up imports from Atlassian Statuspage.