Last checked
Hosted status pages for incident workflow.
Experiencing an issue?
Sorry宕机了吗？
Degraded performance
Share your experience to help others stay informed.
Official status checked
Sorry is experiencing issues
Official provider statusOfficial incident active
Safer email address changes for subscribers — We’ve added a confirmation step when subscribers change their email address, helping ensure your status updates reach the right person. Subscribers receive a confirmation email at their new address. Their original address stays in use until they confirm, so they can keep receiving updates while the change is pending. Their notification preferences and Component selections carry over. Subscribers can resend the confirmation email or cancel the change from their subscription preferences. Once the change is complete, we’ll also notify their previous address.
Official provider statusOfficial incident active
Fixed: Unsubscribe links on private status pages — We’ve updated unsubscribe links in notification emails to follow the usual sign-in requirements for private status pages. After signing in, subscribers are taken straight to their preferences.
Official provider statusOfficial incident active
A clearer view of subscriber Component selections — We’ve made it easier to review which Components your subscribers want updates about. In the subscriber list, click a subscriber’s Component count to open a searchable view of their selections. This replaces the flat list previously shown on hover, keeping Components organised under their pages and groups. Search highlights matching names and shows how many Components match, helping you find a particular selection without scrolling through a long list.
Official provider statusOfficial maintenance active
Faster responses when listing notices through the API — Following our investigation into [this morning’s performance incident](https://status.sorryapp.com/notices/17iuudcmiar0ffb1-degraded-performance-with-the-management-ui), we’ve fixed an issue that could cause slow responses when listing incidents and maintenance notices through the Management API, particularly for pages with large notice histories. The fix is now live, and we’re seeing significantly faster responses to these API requests.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 42h 43mOngoing | Yes | Unknown | ||
| 113h 34mOngoing | Yes | Unknown | ||
| 157h 33mOngoing | Yes | Unknown | ||
| 180h 23mOngoing | Yes | Unknown | ||
| 39m | Yes | Minor | ||
| 1195h 58mOngoing | Yes | Unknown | ||
| 1286h 41mOngoing | Yes | Unknown | ||
| 1315h 26mOngoing | Yes | Unknown |
Uptimus 通过官方状态源监控 Sorry，并将事件、维护和组件健康状况统一为一致的服务状态。
此页面目前包含 25 个受监控组件、51 个事件、9 个维护窗口和 19 天已知历史。
Uptimus 是独立监控服务，与 Sorry 无关联。健康状态并不保证每位用户、设备或地区都未受影响。
当 Sorry 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。 可用历史包含 51 个事件，为提醒提供当前状态之外的背景。 最近收录的事件是“Safer email address changes for subscribers”。
接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Sorry 的 25 个组件: Status Pages, Management UI, REST API, Inbound Mail。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
Planned work published by the official provider.
Following our investigation into [this morning’s performance incident](https://status.sorryapp.com/notices/17iuudcmiar0ffb1-degraded-performance-with-the-management-ui), we’ve fixed an issue that could cause slow responses when listing incidents and maintenance notices through the Management API, particularly for pages with large notice histories. The fix is now live, and we’re seeing significantly faster responses to these API requests.
Started 2026年10月20日 UTC 14:53 · Ongoing
The maintenance is now complete. Thanks for your patience.
Started 2026年10月20日 UTC 09:00 · Ongoing
The maintenance is now complete. Thanks for your patience.
Started 2026年9月26日 UTC 04:00 · Ongoing
The maintenance has now been completed. We’ve double-checked everything and can confirm that all services are working just as they should. Thanks for your patience!
Started 2026年9月24日 UTC 09:00 · Ongoing
The maintenance is now complete. Thanks for your patience.
Started 2026年9月12日 UTC 14:00 · Ongoing
We’ve resolved a bug that caused the Status API’s state_text field to return null while a status page was under maintenance, even when a custom maintenance message had been configured. The API now returns the configured maintenance message as expected, consistent with operational and degraded states. No changes are needed to existing integrations.
Started 2026年9月1日 UTC 09:47 · Ongoing
We’ve updated some of the underlying technology that powers public status pages, keeping it aligned with current security and maintenance standards. It’s a behind-the-scenes improvement, so there’s nothing you need to do and no change to how your status page looks or works.
Started 2026年8月12日 UTC 09:23 · Ongoing
The maintenance is now complete. Thanks for your patience.
Started 2026年8月11日 UTC 09:00 · Resolved 2026年8月11日 UTC 09:13
Downdetector 公共页面主要基于用户报告。Uptimus 还会在来源提供时结合官方事件、维护窗口和组件状态。
| 比较标准 | Uptimus | Downdetector |
|---|---|---|
| Sorry 的社区中断报告 | 已包含 | 已包含 |
| 区分个别报告和大范围中断的自适应基线 | 已包含 | 已包含 |
| 24 小时报表活动和区域中断视图 | 已包含 | 已包含 |
| 在一个工作区管理网站、状态提供商、Steam 游戏及 Android 应用和游戏 | 已包含 | 独立产品 |
| 从同一工作区发送邮件、推送和 Webhook 告警 | 已包含 | 独立产品 |
| Sorry 的官方事件更新和状态时间线 | 已包含 | 以用户报告为主 |
| 分别展示组件健康与维护窗口 | 已包含 | 公共页面功能有限 |
The official status page for Sorry reports degraded performance. An unresolved official incident is listed: “Safer email address changes for subscribers”. 0 reports were recorded for Sorry in the last 24 hours. Last official check: .
发现其他流行服务及其当前状态
评价此服务
暂无评价
分享您对 Sorry 的看法
成为第一个评论的人！
