Is Sorry down?

Last checked 4m ago
Current status
Sorry is up

No incidents right now.

Sorry is operational right now. Last checked 4m ago; the most recent incident resolved 13d ago.

Real-time Sorry status, recent outages, and incident history: pulled directly from Sorry's official status page at status.sorryapp.com every 5 minutes. Pingoru tracks 25 Sorry services and has captured 30 incidents in the last 90 days (99.77% uptime). Get email, Slack, Discord, or webhook alerts the moment Sorry reports a new incident, free for 3 monitors, no credit card.

Users who monitor Sorry also follow these Status Pages services: Akamai StatusPage Diligent ServiceTitan QuaverEd Boomi Unbounce Chowly Signicat FACEIT View all 8,000+ providers
Sorry uptime 99.77% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 38m
    Started Oct 20, 2026, 09:23 AM UTC · Resolved Oct 20, 2026, 10:01 AM UTC
    Management UI
    Timeline · 3 updates
    • investigating · Oct 20, 2026, 09:33 AM UTC

      Following this morning's [routine database maintenance](https://status.sorryapp.com/notices/6b1j81lztj0sz2wc-routine-database-maintenance), we are experiencing slower performance with the management UI at [app.sorryapp.com](https://app.sorryapp.com). We're looking into it now and will share an update as soon as we know more. We're sorry for any disruption.

    • investigating · Oct 20, 2026, 09:46 AM UTC

      We've seen performance in the management UI at app.sorryapp.com improve. We'll keep monitoring for a little while before we resolve this notice. Thanks for bearing with us.

    • resolved · Oct 20, 2026, 10:01 AM UTC

      Performance in the management UI at app.sorryapp.com is back to normal, so we're resolving this notice. Thanks for your patience, and sorry for the disruption.

    Latest: Performance in the management UI at app.sorryapp.com is back to normal, so we're resolving this notice. Thanks for your patience, and sorry for the disruption.

  2. Resolved 2h 23m
    Started Oct 02, 2026, 12:27 AM UTC · Resolved Oct 02, 2026, 02:50 AM UTC
    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…

  3. Resolved 2h 23m
    Started Oct 02, 2026, 12:27 AM UTC · Resolved Oct 02, 2026, 02:50 AM UTC
    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…

  4. Resolved 2h 23m
    Started Oct 02, 2026, 12:27 AM UTC · Resolved Oct 02, 2026, 02:50 AM UTC
    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…

  5. Resolved 2h 23m
    Started Oct 02, 2026, 12:27 AM UTC · Resolved Oct 02, 2026, 02:50 AM UTC
    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.

See the full Sorry outage history

25 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

Incident record

Since April 2026 · Sorryapp Public · 25 components checked every 5 minutes
61incidents recorded
61last 12 months
30last 90 days
5 daystypical duration, 12 months

The longest incident in the last year, General Notices now available on April 29, 2026, ran for 104 days. 11 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Management UI1

Latest incidents

Outage history

Past 90 days · 30 incidents View full outage history →