Histórico de interrupções do Starrez

1. 31 Eost 2026 da 23:11 UTCinvestigating

   Clientes na Austrália Sudeste estão passando por uma interrupção de serviço Os engenheiros estão a trabalhar activamente para resolver o problema. n Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

2. 31 Eost 2026 da 23:19 UTCidentified

   A questão foi identificada e os Engenheiros StarRez estão trabalhando ativamente em uma mitigação para a questão. Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

3. 31 Eost 2026 da 23:32 UTCidentified

   Foi implementada uma solução e estamos a ver a estabilidade regressar à região. Engenheiros StarRez irão monitorar de perto para confirmar um retorno à operação normal A próxima atualização como justificada por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

4. 31 Eost 2026 da 23:32 UTCmonitoring

   Foi implementada uma solução e estamos a ver a estabilidade regressar à região. Engenheiros StarRez irão monitorar de perto para confirmar um retorno à operação normal A próxima atualização como justificada por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

5. 1 Gwengolo 2026 da 00:18 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Eost 2026 da 16:02 UTCinvestigating

   Clientes THD usando o servidor SFTP data-03.datacenter.adirondacksolutions.com estão experimentando uma interrupção de serviço. Os engenheiros estão trabalhando ativamente para corrigir o problema. A próxima atualização é devida dentro de 60 minutos, ou como justificado por mudanças nos eventos.

2. 27 Eost 2026 da 17:05 UTCinvestigating

   Os engenheiros estão trabalhando ativamente para corrigir o problema. Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos.

3. 27 Eost 2026 da 17:52 UTCidentified

   A questão foi identificada e os engenheiros estão remediando. A próxima atualização é devida dentro de 60 minutos, ou como justificado por mudanças nos eventos.

4. 27 Eost 2026 da 18:39 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

5. 27 Eost 2026 da 20:06 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Eost 2026 da 14:17 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. 13 Eost 2026 da 15:29 UTCinvestigating

   Our upstream provider is continuing to investigate the issue.

3. 13 Eost 2026 da 17:04 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. 13 Eost 2026 da 18:14 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. 13 Eost 2026 da 19:43 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. 13 Eost 2026 da 21:09 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. 13 Eost 2026 da 22:34 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. 13 Eost 2026 da 23:12 UTCmonitoring

   We are continuing to monitor for any further issues.

9. 14 Eost 2026 da 00:23 UTCresolved

   This incident has been resolved.

1. 13 Eost 2026 da 05:19 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. 13 Eost 2026 da 05:23 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. 13 Eost 2026 da 05:52 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. 13 Eost 2026 da 06:10 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. 13 Eost 2026 da 06:30 UTCresolved

   This incident has been resolved.

1. 12 Eost 2026 da 03:57 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. 12 Eost 2026 da 04:24 UTCmonitoring

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

3. 12 Eost 2026 da 06:50 UTCresolved

   This incident has been resolved.

1. 11 Eost 2026 da 19:04 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. 11 Eost 2026 da 19:20 UTCmonitoring

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

3. 11 Eost 2026 da 20:27 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11 Eost 2026 da 20:27 UTCresolved

   This incident has been resolved.

1. 23 Gouere 2026 da 14:56 UTCinvestigating

   Clientes na região oeste dos EUA estão passando por uma interrupção de serviço - Os engenheiros estão a trabalhar para resolver o problema. - Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

2. 23 Gouere 2026 da 15:52 UTCidentified

   Identificamos um problema com um provedor de serviços a montante que está impactando a disponibilidade de todos os clientes da região dos EUA ocidentais. Aumentamos o problema com o provedor para acelerar a reparação e estamos monitorando ativamente a situação. Outras atualizações serão compartilhadas à medida que mais informações estiverem disponíveis.

3. 23 Gouere 2026 da 16:50 UTCidentified

   O prestador de serviços a montante confirmou uma questão de infra-estrutura de rede na região dos EUA ocidentais. Estamos a acompanhar activamente a situação. Outras atualizações serão compartilhadas à medida que mais informações estiverem disponíveis.

4. 23 Gouere 2026 da 18:07 UTCidentified

   O prestador de serviços a montante confirmou uma questão de infra-estrutura de rede na região dos EUA ocidentais. A questão a montante ainda não foi resolvida. Estamos ativamente seguindo procedimentos de recuperação de desastres para restaurar a disponibilidade para clientes afetados. Peço desculpa por qualquer inconveniente, Equipa StarRez

5. 23 Gouere 2026 da 18:52 UTCmonitoring

   O fornecedor de serviços a montante implementou uma correção de remediação para a questão da infraestrutura de rede na região dos EUA ocidentais. A funcionalidade do site do cliente começará a ser restaurada como a correção é removida Estamos a acompanhar activamente a situação. Outras atualizações serão compartilhadas à medida que mais informações estiverem disponíveis.

6. 23 Gouere 2026 da 20:48 UTCresolved

   Este incidente foi resolvido.

7. 31 Gouere 2026 da 13:22 UTCpostmortem

   ** Visão geral Em 23 de julho de 2026, a StarRez sofreu uma perturbação de serviço afetando clientes da StarRez Cloud na região oeste dos EUA. As aplicações StarRez Cloud não estavam disponíveis para clientes afetados a partir de aproximadamente 14:44 UTC. Todos os sites de clientes afetados foram restaurados para a operação completa em 19:24 UTC em 23 de julho de 2026. **Root Cause** A perturbação foi causada por uma falha de rede em toda a região desencadeada por um prestador de serviços a montante. A mudança fez com que ambientes de clientes afetados ficassem temporariamente indisponíveis por várias horas, enquanto o provedor de serviços a montante trabalhava para resolver os problemas de rede. **Resolução** Os engenheiros da StarRez identificaram a questão prontamente e tomaram medidas imediatas para confirmar o alcance da falha e levantar casos de suporte de alta gravidade com o provedor a montante. Depois de confirmar a falha com o provedor de upstream, nossos engenheiros começaram a executar um plano de recuperação de desastres para trazer sites de clientes de volta on-line em uma região de nuvem vizinha. Uma vez que o provedor a montante resolveu os problemas de rede subjacentes, todos os sites de clientes foram restaurados para sua região de nuvem configurada nos EUA Ocidental e foram confirmados plenamente operacional até 19:24 UTC, aproximadamente 4,5 horas após o início da interrupção. **Próximos Passos A StarRez continuará a monitorizar a saúde das infra-estruturas regionais e a coordenar-se com os fornecedores a montante para minimizar o impacto de quaisquer perturbações futuras.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Mezheven 2026 da 05:53 UTCinvestigating

   Clientes da região centro-americana estão atualmente tendo uma interrupção de serviço Os engenheiros estão a trabalhar activamente para resolver o problema. n Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

2. 26 Mezheven 2026 da 06:01 UTCidentified

   A questão foi identificada e os engenheiros estão remediando para trazer sites de volta online. Os engenheiros estão a trabalhar activamente para resolver o problema. n Próxima atualização prevista dentro de 60 minutos, ou como justificado por uma mudança de eventos. Peço desculpa por qualquer inconveniente, Equipa StarRez

3. 26 Mezheven 2026 da 06:10 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 26 Mezheven 2026 da 06:10 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

5. 26 Mezheven 2026 da 06:13 UTCresolved

   Este incidente foi resolvido.

6. 30 Mezheven 2026 da 01:51 UTCpostmortem

   ** Visão geral Em 26 de junho de 2026, a StarRez sofreu uma interrupção de serviço que afetou os clientes da StarRez Cloud na região centro-americana. As aplicações StarRez Cloud estavam indisponíveis para clientes afetados a partir de aproximadamente 05:47 UTC. Todos os sites de clientes afetados foram restaurados à plena operação até 06:06 UTC em 26 de junho de 2026. **Root Cause** A interrupção foi causada por uma mudança de configuração aplicada à infraestrutura que apoia a StarRez Cloud na região dos EUA Central. A mudança fez com que ambientes de clientes afetados ficassem temporariamente indisponíveis enquanto a infraestrutura estabilizava. **Resolução** Os engenheiros da StarRez identificaram a questão prontamente e tomaram medidas imediatas para restaurar a infraestrutura afetada a um estado saudável. Todos os sites de clientes na região centro-americana foram confirmados totalmente operacional até 06:06 UTC, aproximadamente 19 minutos após o início da interrupção. **Próximos Passos O StarRez está implementando mais guardrails em torno da configuração para recursos de nuvem para evitar a recorrência desta classe de problemas no futuro.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Mezheven 2026 da 21:26 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. 12 Mezheven 2026 da 22:01 UTCmonitoring

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

3. 13 Mezheven 2026 da 00:14 UTCresolved

   This incident has been resolved.

1. 11 Mezheven 2026 da 02:45 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. 11 Mezheven 2026 da 02:59 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. 11 Mezheven 2026 da 04:07 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. 11 Mezheven 2026 da 04:48 UTCmonitoring

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

5. 11 Mezheven 2026 da 06:03 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 15:56 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. 11 Mae 2026 da 16:55 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. 11 Mae 2026 da 18:05 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. 11 Mae 2026 da 22:15 UTCidentified

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

5. 11 Mae 2026 da 22:23 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. 11 Mae 2026 da 23:37 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. 12 Mae 2026 da 00:58 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. 12 Mae 2026 da 01:46 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. 12 Mae 2026 da 03:03 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. 19 Mezheven 2026 da 00:56 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. 8 Mae 2026 da 08:37 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. 8 Mae 2026 da 09:12 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. 8 Mae 2026 da 09:59 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. 8 Mae 2026 da 10:14 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. 8 Mae 2026 da 11:41 UTCresolved

   This incident has been resolved.

1. 1 Mae 2026 da 14:29 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. 1 Mae 2026 da 14:50 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. 1 Mae 2026 da 15:47 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. 1 Mae 2026 da 16:42 UTCresolved

   This incident has been resolved.

1. 28 Ebrel 2026 da 11:54 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. 28 Ebrel 2026 da 12:58 UTCresolved

   This incident has been resolved.

1. 10 Meurzh 2026 da 10:20 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. 10 Meurzh 2026 da 11:32 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. 10 Meurzh 2026 da 12:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 Meurzh 2026 da 14:02 UTCresolved

   This incident has been resolved.

1. 4 Meurzh 2026 da 23:12 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. 4 Meurzh 2026 da 23:22 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. 4 Meurzh 2026 da 23:42 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. 5 Meurzh 2026 da 01:36 UTCresolved

   This incident has been resolved

1. 4 Meurzh 2026 da 15:59 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. 4 Meurzh 2026 da 16:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 Meurzh 2026 da 16:13 UTCmonitoring

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

4. 4 Meurzh 2026 da 18:34 UTCresolved

   This incident has been resolved.

5. 31 Meurzh 2026 da 01:15 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. 22 Genver 2026 da 23:25 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. 22 Genver 2026 da 23:26 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. 23 Genver 2026 da 06:00 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 Genver 2026 da 08:22 UTCresolved

   This incident has been resolved.

1. 5 Kerzu 2025 da 09:18 UTCinvestigating

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

2. 5 Kerzu 2025 da 09:42 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. 5 Kerzu 2025 da 10:30 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. 5 Kerzu 2025 da 11:34 UTCresolved

   This incident has been resolved

1. 25 Du 2025 da 05:24 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. 25 Du 2025 da 05:31 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. 25 Du 2025 da 05:37 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. 25 Du 2025 da 10:03 UTCresolved

   This incident has been resolved.