Is Sorry down?
Last checked 9m ago20 active incidents: Behind-the-scenes improvements to subscriber preferences, Your subscribers stay in the loop, even as your components… · +18 more
Sorry is reporting a partial outage right now (last checked 9m ago). Some components are affected; others remain operational.
Real-time Sorry status, recent outages, and incident history — pulled directly from Sorry's official status page at https://status.sorryapp.com every 5 minutes. Pingoru tracks 25 Sorry services and has captured 45 incidents in the last 90 days (98.62% uptime). Get email, Slack, Discord, or webhook alerts the moment Sorry reports a new incident — free for 5 monitors, no credit card.
AkamaiActive incidents 19
-
Timeline · 1 update
- investigating · Jul 01, 2026, 01:27 PM UTC
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.
Latest: 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 com…
-
-
Timeline · 1 update
- investigating · Jul 03, 2026, 10:36 AM UTC
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.
Latest: 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 co…
-
-
Timeline · 1 update
- investigating · Jul 14, 2026, 02:21 PM UTC
We resolved a bug that prevented some team members with restricted page access from saving changes when reordering components. Instead of applying the new order, the page displayed an error and left the components unchanged. Component reordering now works as expected for all team members with permission to manage the page.
Latest: We resolved a bug that prevented some team members with restricted page access from saving changes when reordering components. Instead of applying the new order, the page displayed…
-
-
Timeline · 1 update
- investigating · Jul 20, 2026, 10:46 AM UTC
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.
Latest: 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.
-
-
Timeline · 1 update
- investigating · Jul 22, 2026, 06:47 PM UTC
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.
Latest: 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. W…
-
+14 more ongoing incidents — sign up free to track them all.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- investigating · Jun 23, 2026, 08:41 AM UTC
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.
Latest: 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 component…
-
-
Timeline · 1 update
- investigating · Jun 19, 2026, 01:28 PM UTC
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.
Latest: 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 th…
-
-
Timeline · 1 update
- investigating · Jun 02, 2026, 10:41 AM UTC
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.
Latest: 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…
-
-
Timeline · 1 update
- investigating · May 20, 2026, 04:09 PM UTC
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.
Latest: 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…
-
-
Timeline · 1 update
- investigating · May 20, 2026, 09:50 AM UTC
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.
Latest: 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 r…
-
See the full Sorry outage history
36 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Sorry outage history →Or sign up free to get alerts when Sorry breaks · 10 free monitors · No credit card
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Started Sep 14, 2026, 07:38 AM UTC · ● 16h 1m
- Improved status page sitemaps OngoingStarted Sep 14, 2026, 07:38 AM UTC · ● 16h 1m