Status updated
Sorry™, known as Sorry App, is a UK-based status page and incident communication service. It helps businesses create hosted, branded status pages where they can inform customers about outages, maintenance and service disruptions. Sorry offers subscriber notifications by email, SMS and webhooks, private status pages for internal teams, component monitoring integrations, and an API. Software companies and online services use Sorry to communicate transparently during incidents, reducing support tickets and building customer trust.
I have a problem with Sorry
Select the type of problem you're facing to help us and other users.
Recent User Report Trends for Sorry
Aggregated reports in the last 48 hours.
No user reports about Sorry in the last 48 hours.
View live report trends
Add your report to help, or tap to skip
Report a problem to see the chart, or skip
What is Sorry's current status?
All systems are operational
No active incidents reported.
Incident history: past 7 days
times in UTCToday
Yesterday
Oct 30, 2026
Oct 29, 2026
Oct 28, 2026
Oct 27, 2026
Oct 26, 2026
User Reports for Sorry
Recent issues reported by users from around the world.
No user reports for Sorry in the last 30 days.
Experiencing an issue? Add your report:
Stop refreshing this page
We'll email you the moment Sorry goes down — and again when it's back.
Performance Insights
Get a premium status page for your own site — $0, forever
- 1Add your site
- 2Verify you own it
- 3Keep it free
- · Any domain you own. Free while the page stays live.
Any domain you own. Free while your verified page stays live, no credit card.
About Sorry & Technical Insights
What this service does and the technologies behind it.
Read the tech stack as text▾
Overview: A privacy-conscious Jamstack SaaS that dogfoods its own transparency product, pairing a static Netlify marketing site with lean subscription and support tooling.
What stands out
- Using Sorry on sorryapp.com is a deliberate dogfooding signal: the vendor's own uptime is its demo.
- Fathom instead of Google Analytics suggests a privacy stance that complements the trust-and-transparency pitch.
- PostHog-style growth tooling is absent; ProfitWell plus Fathom indicates a lean, subscription-metrics-driven team.
- Help Scout rather than an enterprise helpdesk fits a small UK B2B team selling to business services buyers.
Technologies sorryapp.com uses
- Gatsby — Static-first React framework delivering fast, cheap-to-host marketing pages for a content-driven SaaS.
- Tailwind CSS — Utility CSS for rapid, consistent marketing-site styling without a bespoke design system.
- Help Scout — Support inbox for a B2B SaaS selling trust tooling; suggests human-handled onboarding and incident escalations.
- React — Component base for the Gatsby-rendered front end and likely the in-app dashboard.
- Netlify — Hosting and CI for the Gatsby build, keeping deploy velocity high for a small product team.
- Profitwell — Subscription analytics on Stripe billing to track MRR, churn and retention for a self-serve SaaS model.
- Webpack — Module bundler powering the Gatsby build pipeline and asset optimisation.
- Sorry — The product itself: this site is the company's own status-page platform, dogfooded to prove reliability.
- Fathom — Privacy-first analytics replaces GA, matching a transparency-focused brand that dislikes third-party data leaks.
- PWA — Installable web app conventions show a product-led, app-like onboarding rather than pure desktop software.
- Open Graph — Rich link previews so shared status pages and marketing links look credible on social.
- Google Tag Manager — Tag container for marketing pixels and campaign measurement across the funnel.
- HSTS — Forces HTTPS, essential for a vendor whose entire value proposition is trust.
How these technologies work together
- Gatsby requires Netlify — Gatsby's build output is deployed to Netlify; the marketing site cannot ship without this pairing.
- Gatsby runs on React — Gatsby compiles React components into static HTML, defining how every page is authored here.
- Help Scout integrates with Sorry — Inbound support conversations escalate into published incidents, so customer queries become public transparency.
- Gatsby requires Webpack — Webpack underpins Gatsby's bundling and code-splitting; the static output depends on it.
- Fathom works alongside Profitwell — Fathom measures anonymous site traffic while ProfitWell tracks paying subscribers, together covering the funnel.
- Gatsby works alongside Tailwind CSS — Tailwind classes are compiled through Gatsby's build, giving fast iteration on landing pages.
- Netlify works alongside Sorry — Netlify serves the marketing site while Sorry publishes status destinations, sharing the same uptime story.
- Open Graph works alongside Sorry — Open Graph metadata makes published status pages and incident links render credibly when shared externally.
- Fathom overlaps with Google Tag Manager — Both collect site measurement; Fathom covers privacy-first stats while GTM loads campaign pixels.
- PWA works alongside React — PWA conventions layer install and offline behaviour onto the React front end.
- Profitwell works alongside Sorry — Subscription analytics on a reliability product: churn spikes when status pages themselves fail.
Trust & Safety Checks
Public registration, DNS and certificate records UptimeCard checked independently for the domain sorryapp.com.
Domain name active since 2010
sorryapp.com has been a registered domain since December 2010 — 15 years at the same web address.
Domain lock enabled
The registry blocks unauthorised transfers, so the domain cannot be hijacked.
Registered through 2029
The owner has kept this domain secured until December 2029.
DNS managed by AWS Route 53
8 nameservers answer for this domain, so it stays reachable even if one goes offline.
Records last verified September 2026.
How to fix Sorry not working
Sorry is a status page service. Companies use it to publish incidents and planned maintenance to their customers, and to send updates by email and other channels. Find your symptom below. Most problems come from a sign-in, a component or incident setting, a subscriber list, or the platform itself. If your own status page is unavailable, keep customers informed through your other channels until it is back.
Jump to what you are seeing
Website Down
The Sorry website or your status page does not load for your customers.
- Open the page in a private window and on another network.
- Check status.sorryapp.com for an active incident.
- If your own status page is down, post updates through your other channels until it returns.
Login Failed
Sign-in to the Sorry dashboard is refused.
- If the message says the password is wrong, reset it and check spam.
- Check you are using the account your team set up.
- Try a private window to rule out an old session.
Dashboard Error
The dashboard shows an error, or an incident update does not save.
- Reload in a private window, and save a copy of the update text first.
- Check the component and the status you selected are valid.
- Check status.sorryapp.com, and report the page name and the time to your administrator.
API Down
Calls to the Sorry API fail or time out, so updates cannot be posted by code.
- Check the status code. An access error usually means the key is wrong, and a server error means a service-side problem.
- Confirm the key has not been revoked and is for the right page.
- Post the update through the dashboard by hand, and check status.sorryapp.com.
Notifications Failed
Subscribers do not receive status updates by email or other channels.
- Check the subscriber's address is correct, and that they have confirmed their subscription.
- Check spam for the notification emails, and check the sending domain is set up.
- Check status.sorryapp.com, and send one test notification to yourself.
Status Page Down
The status page itself is not available to customers.
- Check whether the page loads in a private window on another network.
- Check status.sorryapp.com for an incident on the platform.
- Post the same update on your social or email channels until the page is back, and report the time to support.
Still not working?
Contact your organisation's Sorry administrator first, since they manage the page and its subscribers. For a platform-wide problem, contact Sorry support through the help option in the dashboard or on the Sorry website. Have your page name, the incident or component, the exact error text, and the time with your time zone. Never send subscribers' email addresses or passwords in a support message. Live incident updates are on status.sorryapp.com.
Most status-page problems come from a sign-in, a notification setting or a page that has not updated, and they usually clear once that is checked. The status page shows live incidents, so you can see whether the problem is on Sorry's side.
Frequently asked questions about Sorry
Is Sorry down right now?
No. Based on the latest status data on this page, Sorry (sorryapp.com) is up and running normally. The most recent incident, "Management UI performance issues", was resolved (last update Aug 3, 2026).
What should I do if Sorry is not working for me?
First rule out your side: reload the page, try another browser or device, clear the cache and cookies for sorryapp.com, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.
What was the most recent Sorry incident?
The most recent incident on record is "Management UI performance issues", last updated on Aug 3, 2026. It has been resolved.
How many people reported problems with Sorry recently?
No user reports about Sorry were submitted in the last 48 hours.
How do I report a problem with Sorry?
Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.
Where is the official Sorry status page?
The official status page for Sorry is status.sorryapp.com.
Related Services & Domains
Other websites and services in the same category as sorryapp.com.
Related Keywords
Common themes, topics and technologies associated with sorryapp.com.
