Last checked
Sorry status
Hosted status pages for incident workflow.
Experiencing an issue?
¿Sorry no funciona?
Major outage
The current official status of Sorry cannot be verified. The latest stored provider observation indicated degraded performance. 0 reports were recorded for Sorry in the last 24 hours. Last official check: .
Source: official status pageHaving 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
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.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Sorry is experiencing an outage
Official provider statusOfficial incident active
Fixed: Some team members unable to reorder components — 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.
Official provider statusOfficial incident active
Your subscribers stay in the loop, even as your components evolve — 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.
Official provider statusOfficial incident active
Behind-the-scenes improvements to subscriber preferences — 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.
Official provider status
Sorry outage reports
0 outage reports in the last 24 hours.
Mapa de Interrupciones
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mapa de Interrupciones
Loading report locations…
Sorry status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemas
- Interrupción
- Mantenimiento
- Sin datos
Sorry components
Sorry incident history
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 |
|---|---|---|---|---|
| 1339h 17mOngoing | Yes | Unknown | ||
| 1h 28m | Yes | Unknown | ||
| 1h 5m | Yes | Maintenance | ||
| 1607h 3mOngoing | Yes | Unknown | ||
| 1652h 11mOngoing | Yes | Major | ||
| 1848h 58mOngoing | Yes | Unknown | ||
| 1940h 11mOngoing | Yes | Unknown | ||
| 1h 45m | Yes | Unknown |
Discusión de la Comunidad
Comparte tus pensamientos sobre Sorry
Aún no hay comentarios
¡Sé el primero en comentar!
Acerca de la supervisión de Sorry en Uptimus
Uptimus supervisa Sorry mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 25 componentes supervisados, 32 incidencias, 0 mantenimientos y 7 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Sorry. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Cómo supervisa Uptimus Sorry
Recibe alertas cuando Sorry o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 32 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Fixed: Some team members unable to reorder components».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 25 componentes de Sorry: Status Pages, Management UI, REST API, Inbound Mail. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
