Historial de interrupciones de Starrez

1. August 31, 2026 at 11:11 PM UTCinvestigating

   Los clientes en Australia Sudeste están experimentando una interrupción del servicio - Los ingenieros están trabajando activamente para remediar el problema. -Siguiente actualización esperada dentro de 60 minutos, o como justificado por un cambio de eventos. Disculpas por cualquier inconveniente, StarRez Team

2. August 31, 2026 at 11:19 PM UTCidentified

   La cuestión ha sido identificada y los ingenieros de StarRez están trabajando activamente en una mitigación para la cuestión. Next update expected within 60 minutes, or as warranted by a change of events. Disculpas por cualquier inconveniente, StarRez Team

3. August 31, 2026 at 11:32 PM UTCidentified

   Se ha aplicado una solución, y estamos viendo que la estabilidad vuelva a la región. Los ingenieros de StarRez supervisarán de cerca para confirmar un retorno a una operación normal Next update as warranted by a change of events. Disculpas por cualquier inconveniente, StarRez Team

4. August 31, 2026 at 11:32 PM UTCmonitoring

   Se ha aplicado una solución, y estamos viendo que la estabilidad vuelva a la región. Los ingenieros de StarRez supervisarán de cerca para confirmar un retorno a una operación normal Next update as warranted by a change of events. Disculpas por cualquier inconveniente, StarRez Team

5. September 1, 2026 at 12:18 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 27, 2026 at 4:02 PM UTCinvestigating

   Los clientes de THD usando los datos del servidor SFTP-03.datacenter.adirondacksolutions.com están experimentando una interrupción del servicio. Los ingenieros están trabajando activamente para remediar la cuestión. La siguiente actualización debe presentarse dentro de 60 minutos, o según lo justificado por cambios en eventos.

2. August 27, 2026 at 5:05 PM UTCinvestigating

   Los ingenieros están trabajando activamente para remediar la cuestión. Next update expected within 60 minutes, or as warranted by a change of events.

3. August 27, 2026 at 5:52 PM UTCidentified

   La cuestión ha sido identificada y los ingenieros están remediando. La siguiente actualización debe presentarse dentro de 60 minutos, o según lo justificado por cambios en eventos.

4. August 27, 2026 at 6:39 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. August 27, 2026 at 8:06 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 13, 2026 at 2:17 PM UTCinvestigating

   We're currently seeing a partial outage with outbound email for some customers. This is due to a heat-related incident at one of our upstream infrastructure providers, and their team is actively working on it. Who's affected: Customers using THD-hosted email servers may notice emails being delayed or failing to send. Who's not affected: Customers using their own email infrastructure or AWS SES — your email is sending normally. Next update expected within 60 minutes, or as warranted by a change of events.

2. August 13, 2026 at 3:29 PM UTCinvestigating

   Our upstream provider is continuing to investigate the issue.

3. August 13, 2026 at 5:04 PM UTCidentified

   The issue impacting the upstream provider has been identified, and a solution is currently being implemented. Next update expected within 60 minutes, or as warranted by a change of events.

4. August 13, 2026 at 6:14 PM UTCidentified

   While our upstream provider continues working to remediate the underlying issue, our engineers are taking parallel action to restore email delivery. We are actively migrating affected customers to SES to reduce the impact of the disruption and restore email processing as quickly as possible. Next update expected within 60 minutes, or as warranted by a change of events.

5. August 13, 2026 at 7:43 PM UTCidentified

   While our upstream provider continues working to remediate the underlying issue, our engineers are taking parallel action to restore email delivery. We are continuing to actively migrate affected customers to SES to reduce the impact of the disruption and restore email processing as quickly as possible. Next update expected within 60 minutes, or as warranted by a change of events.

6. August 13, 2026 at 9:09 PM UTCidentified

   Our upstream provider continues working to remediate the underlying issue, our engineers are taking parallel action to restore email delivery. We are actively migrating affected customers to SES to reduce the impact of the disruption and restore normal email processing as quickly as possible. While the primary impact of the upstream provider issue remains focused on email delivery, customers may also experience broader service degradation, including intermittent slowness or temporary disruptions. Our teams continue to actively monitor the environment and work to minimize customer impact.

7. August 13, 2026 at 10:34 PM UTCmonitoring

   Our upstream provider has restored services and we're now seeing the email backlog being processed. Engineers are currently reviewing to confirm email functionality is working as expected for impacted customers. Next update expected within 60 minutes, or as warranted by a change of events.

8. August 13, 2026 at 11:12 PM UTCmonitoring

   We are continuing to monitor for any further issues.

9. August 14, 2026 at 12:23 AM UTCresolved

   This incident has been resolved.

1. August 13, 2026 at 5:19 AM UTCinvestigating

   A subset of customers in Australia East are currently experiencing a service disruption -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

2. August 13, 2026 at 5:23 AM UTCidentified

   The issue has been identified, and sites are coming back online -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

3. August 13, 2026 at 5:52 AM UTCidentified

   Our upstream vendor logs have confirmed hardware failure as the cause of our issue however outages are ongoing as hardware recovers. We have escalated the situation with our vendor. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

4. August 13, 2026 at 6:10 AM UTCmonitoring

   We are seeing stability return to the region. Engineers will monitor closely to confirm a return to normal operation -Next update eas warranted by a change of events. Apologies for any inconvenience, StarRez Team

5. August 13, 2026 at 6:30 AM UTCresolved

   This incident has been resolved.

1. August 12, 2026 at 3:57 AM UTCinvestigating

   THD customers on the ND & Baltimore servers are experiencing a service disruption. Engineers are actively working to remediate the issue. The next update is due within 60 minutes, or as warranted by changes in events.

2. August 12, 2026 at 4:24 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. August 12, 2026 at 6:50 AM UTCresolved

   This incident has been resolved.

1. August 11, 2026 at 7:04 PM UTCinvestigating

   College Pads customers are experiencing a service disruption -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events.

2. August 11, 2026 at 7:20 PM UTCmonitoring

   The underlying issues have now been resolved with all customer workloads now back online. Engineers will continue to monitor the situation.

3. August 11, 2026 at 8:27 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. August 11, 2026 at 8:27 PM UTCresolved

   This incident has been resolved.

1. July 23, 2026 at 2:56 PM UTCinvestigating

   Los clientes de la región de EE.UU. Occidental están experimentando una interrupción del servicio - Los ingenieros están trabajando activamente para remediar el tema. - Next update expected within 60 minutes, or as warranted by a change of events. Disculpas por cualquier inconveniente, StarRez Team

2. July 23, 2026 at 3:52 PM UTCidentified

   Hemos identificado un problema con un proveedor de servicios que está impactando la disponibilidad para todos los clientes de la región de Estados Unidos. Hemos intensificado la cuestión con el proveedor para acelerar la rehabilitación y estamos monitoreando activamente la situación. Se compartirán más actualizaciones a medida que se disponga de más información.

3. July 23, 2026 at 4:50 PM UTCidentified

   El proveedor de servicios ha confirmado un problema de infraestructura de red dentro de la región de Estados Unidos Occidental. Estamos monitoreando activamente la situación. Se compartirán más actualizaciones a medida que se disponga de más información.

4. July 23, 2026 at 6:07 PM UTCidentified

   El proveedor de servicios ha confirmado un problema de infraestructura de red dentro de la región de Estados Unidos Occidental. Aún no se ha resuelto la cuestión de la corriente. Estamos siguiendo activamente los procedimientos de recuperación de desastres para restaurar la disponibilidad de los clientes afectados. Disculpas por cualquier inconveniente, StarRez Team

5. July 23, 2026 at 6:52 PM UTCmonitoring

   El proveedor de servicios ha implementado una solución correctiva para el problema de infraestructura de red dentro de la región de EE.UU. Occidental. La funcionalidad del sitio del cliente comenzará a ser restaurada ya que la solución está enrollada Estamos monitoreando activamente la situación. Se compartirán más actualizaciones a medida que se disponga de más información.

6. July 23, 2026 at 8:48 PM UTCresolved

   Este incidente ha sido resuelto.

7. July 31, 2026 at 1:22 PM UTCpostmortem

   **Overview** El 23 de julio de 2026, StarRez experimentó una interrupción del servicio que afectaba a clientes de StarRez Cloud en la región de los Estados Unidos. Las aplicaciones de StarRez Cloud no estaban disponibles para clientes afectados a partir de aproximadamente 14:44 UTC. Todos los sitios de clientes afectados fueron restaurados a plena operación para 19:24 UTC el 23 de julio de 2026. *Causa real* La perturbación fue causada por un outage de redes en toda la región desencadenado por un proveedor de servicios avanzado. El cambio causó que los entornos de los clientes afectados no estuvieran disponibles temporalmente durante varias horas, mientras que el proveedor de servicios avanzado trabajó para resolver los problemas de las redes. **Resolución** Los ingenieros de StarRez identificaron la cuestión con prontitud y tomaron medidas inmediatas para confirmar el alcance de la salida y plantear casos de apoyo de alta perseverancia con el proveedor de corriente. Después de confirmar la salida con el proveedor de corriente, nuestros ingenieros comenzaron a ejecutar un plan de recuperación de desastres para traer los sitios de clientes en línea en una región de nube vecina. Una vez que el proveedor de corriente resolvió los problemas de networking subyacentes, todos los sitios de clientes fueron restaurados a su región de nube configurada en el oeste de Estados Unidos y fueron confirmados totalmente operativos por 19:24 UTC, aproximadamente 4,5 horas después de la interrupción comenzó. **Siguientes pasos** StarRez seguirá monitoreando la salud de la infraestructura regional y se coordinará con los proveedores de corriente para minimizar el impacto de cualquier perturbación futura.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 26, 2026 at 5:53 AM UTCinvestigating

   Los clientes de la región centroamericana están teniendo una interrupción del servicio - Los ingenieros están trabajando activamente para remediar el problema. -Siguiente actualización esperada dentro de 60 minutos, o como justificado por un cambio de eventos. Disculpas por cualquier inconveniente, StarRez Team

2. June 26, 2026 at 6:01 AM UTCidentified

   El problema ha sido identificado y los ingenieros están remediando para traer sitios de vuelta en línea. - Los ingenieros están trabajando activamente para remediar el problema. -Siguiente actualización esperada dentro de 60 minutos, o como justificado por un cambio de eventos. Disculpas por cualquier inconveniente, StarRez Team

3. June 26, 2026 at 6:10 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. June 26, 2026 at 6:10 AM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. June 26, 2026 at 6:13 AM UTCresolved

   Este incidente ha sido resuelto.

6. June 30, 2026 at 1:51 AM UTCpostmortem

   **Overview** El 26 de junio de 2026, StarRez experimentó una perturbación del servicio que afectaba a clientes de StarRez Cloud en la región centroamericana. Las aplicaciones de StarRez Cloud no estaban disponibles para clientes afectados a partir de las 05:47 UTC aproximadamente. Todos los sitios de clientes afectados fueron restaurados para el funcionamiento completo por 06:06 UTC el 26 de junio de 2026. *Causa real* La perturbación fue causada por un cambio de configuración aplicado a la infraestructura de apoyo a StarRez Cloud en la región centroamericana. El cambio hizo que los entornos de los clientes afectados no estuvieran disponibles temporalmente mientras la infraestructura se estabilizara. **Resolución** Los ingenieros de StarRez identificaron rápidamente el problema y tomaron medidas inmediatas para restaurar la infraestructura afectada a un estado saludable. Todos los sitios de clientes de la región central de Estados Unidos fueron confirmados totalmente operativos por 06:06 UTC, aproximadamente 19 minutos después de la interrupción comenzó. **Siguientes pasos** StarRez está implementando más controles alrededor de la configuración a los recursos en la nube para evitar la repetición de esta clase de problema en el futuro.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 12, 2026 at 9:26 PM UTCinvestigating

   College Pads customers are experiencing a service disruption -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events.

2. June 12, 2026 at 10:01 PM UTCmonitoring

   The underlying issues have now been resolved with all customer workloads now back online. Engineers will continue to monitor the situation.

3. June 13, 2026 at 12:14 AM UTCresolved

   This incident has been resolved.

1. June 11, 2026 at 2:45 AM UTCinvestigating

   Customers in all regions are currently experiencing a service disruption for AI features within the StarRez product. The features impacted are: - Write with AI - Rez 360 Intelligence - Summaries - Parcels AI scanning ( - Program Agent Beta - Rez 360 Intelligence : Ask Ai beta All other functionality within the StarRez product is not impacted at this time. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

2. June 11, 2026 at 2:59 AM UTCidentified

   The issue has been acknowledged and identified with our upstream vendor who is actively working to restore services. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

3. June 11, 2026 at 4:07 AM UTCidentified

   We are seeing small improvements in completion rates however errors are still occurring, and we expect timeouts and prolonged response delays whilst this incident is ongoing. Our upstream vendor is continuing they're efforts to mitigate and resolve this situation. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

4. June 11, 2026 at 4:48 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. June 11, 2026 at 6:03 AM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 3:56 PM UTCinvestigating

   We are aware of a service disruption currently. We are investigating the cause and will provide additional updates as possible, or within the next 60 minutes.

2. May 11, 2026 at 4:55 PM UTCidentified

   We’ve identified an issue with an upstream service provider that is impacting availability for a number of clients. We have escalated the issue with the provider to expedite remediation and are actively monitoring the situation. Further updates will be shared as more information becomes available.

3. May 11, 2026 at 6:05 PM UTCidentified

   The upstream service provider has confirmed an issue and are in the process of resolving this for our West Central US region. Further updates will be shared as more information becomes available.

4. May 11, 2026 at 10:15 PM UTCidentified

   The upstream provider is continuing their investigation into this incident. Further updates will be shared as more information becomes available.

5. May 11, 2026 at 10:23 PM UTCidentified

   The service disruption is still ongoing within this region. StarRez Engineers are actively in the process of executing our Disaster Recovery plan for impacted customers. Customers are starting to come online as this process completes. - Updates within the next hour or as warranted. Apologies for the inconvenience StarRez

6. May 11, 2026 at 11:37 PM UTCidentified

   The service disruption is still ongoing within this region. StarRez Engineers are actively in the process of executing our Disaster Recovery plan for impacted customers. The upstream provider is continuing their investigation into this incident. Further updates will be shared as more information becomes available. - Updates within the next hour or as warranted. Apologies for the inconvenience StarRez

7. May 12, 2026 at 12:58 AM UTCidentified

   The service disruption is still ongoing within this region. StarRez Engineers are actively in the process of executing our Disaster Recovery plan for impacted customers. The upstream provider has identified the root cause and are working on a fix for the issue. - Updates within the next hour or as warranted. Apologies for the inconvenience StarRez

8. May 12, 2026 at 1:46 AM UTCmonitoring

   The upstream provider has completed the fix and we are seeing recovery across all impacted sites. StarRez Engineers are continuing to monitor the situation. - Updates within the next hour or as warranted. Apologies for the inconvenience StarRez

9. May 12, 2026 at 3:03 AM UTCresolved

   The issue with the upstream service provider has been resolved. All sites are restored to full function. Sites that had to undergo Disaster Recovery steps will have these finalized and restored to normal during the relevant maintenance windows for those sites. Apologies for the inconvenience StarRez

10. June 19, 2026 at 12:56 AM UTCpostmortem

    ## StarRez Root Cause Analysis ### Overview On 11 May 2026, StarRez experienced a service disruption affecting StarRez Cloud customers in the West Central US region. StarRez Cloud applications were unavailable for affected customers beginning at approximately 15:56 UTC. All affected customer sites were restored to full operation by 03:03 UTC on 12 May 2026. ### Root Cause The disruption was caused by hardware failures at our upstream service provider's West Central US datacenter. The failures caused the database services underpinning StarRez Cloud applications in that region to become unavailable, taking a number of customer sites offline. ### Resolution Once confirmed as an upstream infrastructure failure, StarRez engineers initiated disaster recovery for the affected region, restoring affected customer environments in an alternate region. Affected sites were progressively restored beginning at approximately 22:23 UTC, with all sites confirmed fully operational by 03:03 UTC on 12 May 2026. Customers recovered via disaster recovery were moved back to the West Central US region during their scheduled maintenance windows later the same day. ### Next Steps StarRez will continue monitoring regional infrastructure health and coordinate with upstream providers to minimize the impact of any future disruptions.

1. May 8, 2026 at 8:37 AM UTCinvestigating

   Customers in the East US region are currently experiencing intermittent service disruption. -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

2. May 8, 2026 at 9:12 AM UTCidentified

   The issue has been identified, and engineers are currently working to resolve this issue. Customers will continue experiencing intermittent outages whilst the work continues. Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

3. May 8, 2026 at 9:59 AM UTCmonitoring

   The underlying issue has been mitigated, and customer sites are now coming back online and remaining stable. -Next update expected within 60 minutes, or as warranted by a change of events.

4. May 8, 2026 at 10:14 AM UTCmonitoring

   All sites are now back online and stable. We will continue to monitor before resolving. -Next update as warranted by a change of events.

5. May 8, 2026 at 11:41 AM UTCresolved

   This incident has been resolved.

1. May 1, 2026 at 2:29 PM UTCinvestigating

   We are aware of a service disruption currently. We are investigating the cause and will provide additional updates as possible, or within the next 60 minutes.

2. May 1, 2026 at 2:50 PM UTCidentified

   The team has identified the issue and has implemented a mitigation, with affected sites returning to service. We will continue to provide updates as we have them, or within the next 60 minutes.

3. May 1, 2026 at 3:47 PM UTCmonitoring

   The team has applied a mitigation, and all affected sites are in full service. We are continuing to monitor. Next update as soon as we have it, or within the next 60 minutes.

4. May 1, 2026 at 4:42 PM UTCresolved

   This incident has been resolved.

1. April 28, 2026 at 11:54 AM UTCmonitoring

   There was a temporary disruption affecting access to the THD VPN tunnel. Services have since been fully restored, and we are continuing to monitor the situation closely.

2. April 28, 2026 at 12:58 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 10:20 AM UTCinvestigating

   THD customers on the Newport server might experience a service disruption. Engineers are actively working to remediate the issue. The next update is due within 60 minutes, or as warranted by changes in events.

2. March 10, 2026 at 11:32 AM UTCmonitoring

   Service has recovered since applying the mitigation. We are continuing to monitor the situation. Next update in 60 minutes or sooner if we have more information.

3. March 10, 2026 at 12:59 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. March 10, 2026 at 2:02 PM UTCresolved

   This incident has been resolved.

1. March 4, 2026 at 11:12 PM UTCinvestigating

   We are investigating service degradation for Cloud Payments in the US Region. Engineers are working on mitigating the issue. Next Update in 60 minutes or sooner if we have more information.

2. March 4, 2026 at 11:22 PM UTCidentified

   Engineers have applied a mitigation to address the issue and are continuing to review the situation. Next update in 60 minutes or sooner if we have more information.

3. March 4, 2026 at 11:42 PM UTCmonitoring

   Service has recovered since applying the mitigation. We are continuing to monitor the situation. Next update in 60 minutes or sooner if we have more information.

4. March 5, 2026 at 1:36 AM UTCresolved

   This incident has been resolved

1. March 4, 2026 at 3:59 PM UTCinvestigating

   We are currently investigating an issue affecting Single Sign-On (SSO) authentication. Users may experience difficulties logging in via SSO. - Engineers are actively working to remediate the issue.  - Next update expected within 60 minutes, or as warranted by a change of events.

2. March 4, 2026 at 4:02 PM UTCinvestigating

   We are continuing to investigate this issue.

3. March 4, 2026 at 4:13 PM UTCmonitoring

   Engineers have remediated the issue. We will continue to monitor and will close this incident out once stability has been confirmed.

4. March 4, 2026 at 6:34 PM UTCresolved

   This incident has been resolved.

5. March 31, 2026 at 1:15 AM UTCpostmortem

   **Overview** On 5 March 2026, following the enablement of Cloudflare for all customers, THD experienced a service disruption that resulted in an authentication loop during Single Sign-On \(SSO\). **Root Cause** The SSO Service Provider configuration did not correctly handle session validation when operating behind the Cloudflare proxy, resulting in authentication sessions being invalidated and causing a login loop. **Resolution** The issue was initially mitigated by reverting the Cloudflare change, restoring normal SSO functionality. Configuration updates were then made to the SSO Service Provider to ensure compatibility with proxied traffic, after which Cloudflare was incrementally re-enabled.

1. January 22, 2026 at 11:25 PM UTCinvestigating

   We are aware of an ongoing Microsoft 365 outage that is affecting email delivery to Outlook mailboxes. This is a downstream issue within Microsoft 365 and is separate from StarRez Cloud. As a result, some customers may experience delays or failures in receiving MFA-related emails. We are monitoring the situation closely and will provide updates as more information becomes available. Further details are available via Microsoft’s status page: https://status.cloud.microsoft/ Apologies for any inconvenience caused, StarRez Team

2. January 22, 2026 at 11:26 PM UTCmonitoring

   We are aware of an ongoing Microsoft 365 outage that is affecting email delivery to Outlook mailboxes. This is a downstream issue within Microsoft 365 and is separate from StarRez Cloud. As a result, some customers may experience delays or failures in receiving MFA-related emails. We are monitoring the situation closely and will provide updates as more information becomes available. Further details are available via Microsoft’s status page: https://status.cloud.microsoft/ Apologies for any inconvenience caused, StarRez Team

3. January 23, 2026 at 6:00 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. January 23, 2026 at 8:22 AM UTCresolved

   This incident has been resolved.

1. December 5, 2025 at 9:18 AM UTCinvestigating

   We are investigating an issue affecting all regions. Next Update in 60 minutes or sooner if we have more information.

2. December 5, 2025 at 9:42 AM UTCidentified

   We are aware of an issue affecting access to StarRez Cloud as a result of a global outage of an upstream provider. We are assessing the impact and escalating with the provider as required

3. December 5, 2025 at 10:30 AM UTCmonitoring

   The upstream provider has resolved the issue, with all customer workloads back online. Engineers will continue to monitor and will close this incident out once stability has been confirmed.

4. December 5, 2025 at 11:34 AM UTCresolved

   This incident has been resolved

1. November 25, 2025 at 5:24 AM UTCinvestigating

   A subset of customers in the WestUS2 region are currently having a service disruption -Engineers are actively working to remediate the issue. -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

2. November 25, 2025 at 5:31 AM UTCidentified

   The issue has been identified. Services are now coming back online -Next update expected within 60 minutes, or as warranted by a change of events. Apologies for any inconvenience, StarRez Team

3. November 25, 2025 at 5:37 AM UTCmonitoring

   The underlying issues have now been resolved with all customer workloads now back online. Engineers will continue to monitor and will close this incident out once stability has been confirmed. Apologies for any inconvenience, StarRez Team

4. November 25, 2025 at 10:03 AM UTCresolved

   This incident has been resolved.