There were 7 Sorry outages since March 28, 2026 totaling 60h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
If you are using page collections and importing incident templates from Atlassian StatusPage, we have got good news! Previously, imported templates would always appear as shared templates across your entire collection. Now, when you import into a specific page within your collection, those templates are automatically organized under that page—exactly where you would expect them to be. This means less manual reorganization after imports, and your templates stay neatly grouped with the pages they belong to. Happy importing! 🎉
We have fixed a bug where subscriber counts displayed on the pages index were incorrect for pages within collections. The counts were underreporting the true number of subscribers. Subscriber counts now accurately reflect all subscribers for each page in your collections, including those subscribed to specific components and those subscribed to all components.
From 17:54 UTC on April 22, our monitoring began detecting degraded performance on the Management UI, with response times increasing above normal levels. Customers may have noticed the Management UI feeling slow or unresponsive between 17:54 UTC on April 22 and 12:33 UTC on April 23. A period of elevated automated traffic placed additional load on our servers, which combined with an existing issue in how we handle slow requests led to a gradual build-up that caused the performance degradation our monitoring detected. **Timeline** - **17:54 UTC, April 22** — Monitoring detects degraded performance and increasing response times - **08:02 UTC, April 23** — Team alerted, investigation begins - **09:37 UTC, April 23** — Servers restarted, normal performance restored - **12:33 UTC, April 23** — Fix applied **What We've Done** - Updated our server configuration to prevent this from recurring - Improved our alerting to ensure our team are notified more promptly of similar degradation - Performance improvements to our most resource-intensive pages are underway We appreciate your patience, and we're sorry for any disruption this may have caused. If you have any questions, please don't hesitate to reach out to our team.
Everything continues to look happy and stable for the past hour, with no further performance issues flagged since that slight wobble between 00:55 and 01:05 UTC. All the data we're seeing suggests that the issue was a general network slowdown, somewhere outside of our infrastructure, between our edge servers and our main platform. We're happy to consider this incident as resolved.
Pingoru polls Sorry's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required