Is Sorry Down?

This page shows the live Sorry status so you can confirm in seconds if Sorry is down.

Sorry current status

Updated

Sorry is operational

IsDown pulls data from the official status page every few minutes and collects user-reported Sorry issues.
Refresh the page to see the latest updates.

Get Sorry outage alerts in

Sorry user-reported issues in the last 24 hours

This chart displays the number of user-reported Sorry problems over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.

IsDown Logo Third-party monitoring

Stop Juggling Dozens of Status Pages – Monitor Them All in One Place

Monitoring 4000+ third-party services in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Create public or private status pages
Start Free Trial
14-day free trial · No credit card required
Trusted by thousands of teams

Sorry outage history

IsDown has tracked 62 incidents since started monitoring Sorry downtimes in January 2021. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

  • Apr 09 2025

    about 1 month ago · lasted 33 minutes

    As part of our continual work to keep the product secure, reliable, and performant, we will upgrade the version of Ruby, the underlying language of our application, on Wednesday, April 9th, at 09:00 UTC. We don't anticipate this...

  • Apr 07 2025

    about 1 month ago · lasted about 4 hours

    We're currently seeing a spike in response-times on the Pingdom API, causing a potential impact on how frequently we can synchronise the status of your checks. We don't anticipate this causing any real-world delay when triggering Pingdom...

  • Mar 20 2025

    about 2 months ago · lasted 20 days

    Following our upgrades from last month (https://status.sorryapp.com/history/2025/february/zlda84j6jtaoajgm-rescheduled-platform-wide-upgrades-to-ruby-on-rails), we plan to make further upgrades to the underlying tech stack on Thursday,...

  • Mar 06 2025

    2 months ago · lasted 14 days

    In addition to our Routine Database Maintenance on March 4th (https://status.sorryapp.com/notices/oohhlj9d8jmyodzl-routine-database-maintenance), our platform provider will perform routine maintenance on our cache servers a few days...

  • Mar 04 2025

    2 months ago · lasted 16 days

    Our platform provider will perform routine maintenance to our database cluster on March 4th during our agreed maintenance window of 09:00 - 13:00 UTC. We do not anticipate any substantial downtime, however the management UI and REST API...

  • Jan 2021 ...
    IsDown started monitoring Sorry status

    We've tracked and collected 62 incidents since started monitoring Sorry status

Sign up and check all outage history

Latest user comments about Sorry issues

No comments yet

Sorry outages in the last 30 days

Number of Incidents

0 issues

Last incident

31 days ago

IsDown Logo Seamless Integrations

Get Sorry outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.
Never miss an outage
Easy setup · No coding required
Works with your existing stack

Having problems with Sorry? What can you do?

  1. First, stay calm.

    • We know it's stressful when Sorry is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact of the Sorry outage

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did Sorry already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Sorry status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If Sorry is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Did Sorry recover?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
    • Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.

Want to be informed about Sorry status changes?

IsDown offers an easy way to monitor Sorry with maximum flexibility

Major Outages Notifications

IsDown monitors Sorry for major outages. A major outage is when Sorry experiences a critical issue that severely affects one or more services/regions. When Sorry marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors Sorry status page for minor outages. A minor outage is when Sorry experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in Sorry status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Early Outage Indicators

Sorry and other vendors don't always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.

Frequently Asked Questions

Is Sorry down today?

Sorry isn't down. You can check Sorry status and incident details on the top of the page. IsDown continuously monitors Sorry official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current Sorry status?

Sorry is currently operational. You can check Sorry status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a Sorry outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is Sorry slow today?

Currently there's no report of Sorry being slow. Check on the top of the page if there are any reported problems by other users.

How are Sorry outages detected?

IsDown monitors the Sorry official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last Sorry outage?

Sorry last outage was on April 09, 2025 with the title "Ruby version upgrade"

Sorry not working for you? How do I know if Sorry is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How can I check Sorry status and outages?

Why use IsDown to monitor Sorry instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor Sorry and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required