Sorry Outage History
Sorry is up right nowPingoru has recorded 62 incidents for Sorry: 62 in the last 12 months and 32 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 588 (1%) |
Incidents, newest first
Major May 7, 2026 HSTS Configuration Changes 9h 22m
Started May 07, 2026, 12:00 AM UTC· resolved May 07, 2026, 09:23 AM UTC
- investigating Feb 09, 2026, 10:24 AM UTC
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.
Major May 6, 2026 Fixed Magic Link Authentication Issue 9h 9m
Started May 06, 2026, 12:01 AM UTC· resolved May 06, 2026, 09:11 AM UTC
- investigating Feb 05, 2026, 04:05 PM UTC
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.
Major April 29, 2026 General Notices now available 103d 22h
Started Apr 29, 2026, 11:14 AM UTC· resolved Aug 11, 2026, 09:30 AM UTC
- investigating Apr 29, 2026, 11:14 AM UTC
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.
Major April 29, 2026 Fixed Intermittent Error Deleting Incidents 11h 10m
Started Apr 29, 2026, 12:08 AM UTC· resolved Apr 29, 2026, 11:18 AM UTC
- investigating Feb 05, 2026, 02:33 PM UTC
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.
Major April 28, 2026 Groundwork for a fix when removing notices with deleted impact times 3h 28m
Started Apr 28, 2026, 10:29 AM UTC· resolved Apr 28, 2026, 01:58 PM UTC
- investigating Feb 05, 2026, 11:03 AM UTC
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.
Major April 27, 2026 Improved Error Messages for Atlassian Statuspage Import 8h 8m
Started Apr 27, 2026, 12:07 AM UTC· resolved Apr 27, 2026, 08:16 AM UTC
- investigating Feb 03, 2026, 01:56 PM UTC
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.
Major April 24, 2026 Better Template Organization When Importing from Atlassian 2h 23m
Started Apr 24, 2026, 04:06 PM UTC· resolved Apr 24, 2026, 06:30 PM UTC
- investigating Feb 03, 2026, 12:32 PM UTC
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! 🎉
Major April 24, 2026 Fixed Incorrect Subscriber Counts for Pages in Collections 15h 55m
Started Apr 24, 2026, 12:11 AM UTC· resolved Apr 24, 2026, 04:06 PM UTC
- investigating Feb 03, 2026, 10:29 AM UTC
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.
Major April 22, 2026 Management UI Performance Degradation 18h 39m
Started Apr 22, 2026, 05:54 PM UTC· resolved Apr 23, 2026, 12:33 PM UTC
- resolved Apr 24, 2026, 06:26 PM UTC
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.
Major April 16, 2026 Faster activity reports 89d 4h
Started Apr 16, 2026, 09:53 AM UTC· resolved Jul 14, 2026, 02:25 PM UTC
- investigating Apr 16, 2026, 09:53 AM UTC
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.
Major March 28, 2026 Slow Performance on Management UI 45m
Started Mar 28, 2026, 01:35 AM UTC· resolved Mar 28, 2026, 02:21 AM UTC
- resolved Mar 28, 2026, 02:21 AM UTC
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.
Major January 30, 2026 Service Degradation on January 30, 2026 3h 46m
Started Jan 30, 2026, 12:46 PM UTC· resolved Jan 30, 2026, 04:32 PM UTC
- resolved Feb 04, 2026, 02:07 PM UTC
### What Happened On January 30, we deployed a network configuration change designed to block aggressive web crawlers from China that were placing unnecessary load on our infrastructure. Unfortunately, this change contained a bug that caused some requests to our service to be handled incorrectly. During the affected period, some customers may have experienced: - **Status notice updates not being saved** when submitted - **General performance degradation** across the platform ### Timeline - **12:48 PM UTC:** Configuration deployed to production - **3:30 PM UTC:** Issue discovered by our engineering team - **4:32 PM UTC:** Configuration rolled back, normal service resumed ### Why This Happened The bug slipped through our standard quality assurance process because it affected network infrastructure that wasn't covered by our existing automated testing. While our performance monitoring detected the degradation, the threshold wasn't set to trigger an immediate alert. ### What We've Done We've taken the following steps to prevent similar issues: 1. **Improved monitoring thresholds** to alert our team immediately when performance degrades 2. **Expanded automated testing** to include network-level infrastructure changes that were previously outside our QA scope 3. **Conducted a full review** of the change to understand what went wrong ### Impact Assessment We're grateful that no customers reported issues during this incident, suggesting the actual impact was minimal. Importantly, **no data was lost** - any failed form submissions would have been immediately apparent to users, who could simply retry. ### Moving Forward We've fixed the issue and improved our safeguards to prevent this from happening again. If you have any questions about this incident, feel free to reach out.