Last checked
Sorry status
Hosted status pages for incident workflow.
Experiencing an issue?
Czy Sorry nie działa?
Degraded performance
The official status page for Sorry reports degraded performance. An unresolved official incident is listed: “Fixed: Status page deletion”. 0 reports were recorded for Sorry in the last 24 hours. Last official check: .
Having issues with Sorry?
Share your experience to help others stay informed.
Sorry service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Sorry activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Small green bars: normal status (illustrative). Taller bars: report activity. Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Sorry is experiencing issues
Official provider statusOfficial incident active
Fixed: Status page deletion — We’ve fixed an issue that could prevent a status page from being deleted if a team member had previously collapsed or dismissed its getting-started checklist. Affected pages can now be deleted as expected.
Official provider statusOfficial incident active
More control over notice archiving — You can now archive past notices manually, without waiting for your automatic archive settings to take effect. This gives you more control over your status-page history without deleting the original notices. Choose Archive Notice from a notice’s actions menu, either in the notice list or when editing it. Archived notices stay in their usual position in your dashboard, clearly marked, so they’re easy to find again. You can also choose Unarchive Notice to restore a notice to your status-page history - including notices that were archived automatically. Your existing automatic archiving continues to work as before - there’s nothing new to configure.
Official provider statusOfficial incident active
Fixed: Notification delivery across enabled channels — We’ve fixed an issue where subscribers with a deactivated email address could be excluded from status updates entirely, even when they had another notification channel enabled. Updates will now continue through their other eligible channels, while delivery to the deactivated email address remains suppressed. Existing channel and Component preferences continue to apply. No action is needed.
Official provider statusOfficial maintenance active
Fixed: Maintenance message missing from the Status API — 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.
Official provider status
