Starrez driftsforstyrrelser

1. 31. august 2026 kl. 23.11 UTCinvestigating

   Kunder i Australien Sydøst oplever i øjeblikket en serviceforstyrrelse Ingeniører arbejder aktivt på at opklare problemet. -Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

2. 31. august 2026 kl. 23.19 UTCidentified

   Problemet er blevet identificeret, og StarRez Ingeniører arbejder aktivt på en afbødning af problemet. Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

3. 31. august 2026 kl. 23.32 UTCidentified

   Et fix er blevet gennemført, og vi ser stabilitet vende tilbage til regionen. StarRez Ingeniører vil overvåge nøje for at bekræfte en tilbagevenden til normal drift Næste opdatering som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

4. 31. august 2026 kl. 23.32 UTCmonitoring

   Et fix er blevet gennemført, og vi ser stabilitet vende tilbage til regionen. StarRez Ingeniører vil overvåge nøje for at bekræfte en tilbagevenden til normal drift Næste opdatering som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

5. 1. september 2026 kl. 00.18 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. august 2026 kl. 16.02 UTCinvestigating

   THD-kunder, der bruger SFTP-serveren data- 03.datacenter.adirondacksolutions.com oplever en serviceforstyrrelse. Ingeniører arbejder aktivt på at afhjælpe problemet. Den næste opdatering skal ske inden for 60 minutter, eller som berettiget af ændringer i begivenheder.

2. 27. august 2026 kl. 17.05 UTCinvestigating

   Ingeniører arbejder aktivt på at afhjælpe problemet. Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder.

3. 27. august 2026 kl. 17.52 UTCidentified

   Problemet er blevet identificeret, og ingeniører er oprydning. Den næste opdatering skal ske inden for 60 minutter, eller som berettiget af ændringer i begivenheder.

4. 27. august 2026 kl. 18.39 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

5. 27. august 2026 kl. 20.06 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 13. august 2026 kl. 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. august 2026 kl. 15.29 UTCinvestigating

   Our upstream provider is continuing to investigate the issue.

3. 13. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 23.12 UTCmonitoring

   We are continuing to monitor for any further issues.

9. 14. august 2026 kl. 00.23 UTCresolved

   This incident has been resolved.

1. 13. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 06.30 UTCresolved

   This incident has been resolved.

1. 12. august 2026 kl. 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. august 2026 kl. 04.24 UTCmonitoring

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

3. 12. august 2026 kl. 06.50 UTCresolved

   This incident has been resolved.

1. 11. august 2026 kl. 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. august 2026 kl. 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. august 2026 kl. 20.27 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11. august 2026 kl. 20.27 UTCresolved

   This incident has been resolved.

1. 23. juli 2026 kl. 14.56 UTCinvestigating

   Kunder i West US regionen oplever i øjeblikket en service afbrydelse - Ingeniører arbejder aktivt på at opklare problemet. - Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

2. 23. juli 2026 kl. 15.52 UTCidentified

   Vi har identificeret et problem med en opstrømsleverandør, der påvirker tilgængeligheden for alle klienter i West US-regionen. Vi har optrappet spørgsmålet med udbyderen for at fremskynde oprydningen og overvåger aktivt situationen. Yderligere opdateringer vil blive delt som mere information bliver tilgængelig.

3. 23. juli 2026 kl. 16.50 UTCidentified

   Leverandøren af opstrømsservice har bekræftet et netinfrastrukturproblem i West US-regionen. Vi overvåger situationen aktivt. Yderligere opdateringer vil blive delt som mere information bliver tilgængelig.

4. 23. juli 2026 kl. 18.07 UTCidentified

   Leverandøren af opstrømsservice har bekræftet et netinfrastrukturproblem i West US-regionen. Opstrømsspørgsmålet er endnu ikke løst. Vi følger aktivt katastrofeberedskabsprocedurer for at genoprette tilgængeligheden for de berørte kunder. Undskyld for ulejligheden. StarRez Team

5. 23. juli 2026 kl. 18.52 UTCmonitoring

   Leverandøren af opstrømstjenester har gennemført en oprydning af netinfrastrukturproblemet i West US-regionen. Kundens websted funktionalitet vil begynde at blive restaureret som fix er rullet ud Vi overvåger situationen aktivt. Yderligere opdateringer vil blive delt som mere information bliver tilgængelig.

6. 23. juli 2026 kl. 20.48 UTCresolved

   Denne hændelse er blevet løst.

7. 31. juli 2026 kl. 13.22 UTCpostmortem

   * * Oversigt * * Den 23. juli 2026 oplevede StarRez en serviceafbrydelse, der påvirkede StarRez Cloud kunder i det vestlige USA. StarRez Cloud applikationer var ikke tilgængelige for berørte kunder begynder omkring 14: 44 UTC. Alle berørte kundesteder blev genoprettet til fuld drift den 23. juli 2026 kl. 19: 24 UTC. * * Rodårsag * * Afbrydelsen skyldtes et regionalt netværksbrud udløst af en udbyder af opstrømstjenester. Ændringen fik berørte kundemiljøer til at blive midlertidigt utilgængelige i en række timer, mens opstrøms-udbyder arbejdede for at løse netværksproblemer. * * Opløsning * * StarRez ingeniører identificerede problemet hurtigt og tog omgående skridt til at bekræfte omfanget af udfald og rejse høj sværhedsgrad support sager med opstrøms udbyder. Efter bekræftelse af udfald med opstrøms udbyder, vores ingeniører begyndte at udføre en katastrofe genopretningsplan for at bringe kundesider tilbage online i en nærliggende cloud-region. Når opstrøms udbyder løst de underliggende netværksproblemer, alle kundesites blev genoprettet til deres konfigurerede cloud-region i det vestlige USA og blev bekræftet fuldt operationelle af 19: 24 UTC, ca. 4,5 timer efter afbrydelsen begyndte. * * Næste skridt * * StarRez vil fortsat overvåge regional infrastruktur sundhed og koordinere med opstrøms udbydere for at minimere virkningen af eventuelle fremtidige forstyrrelser.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. juni 2026 kl. 05.53 UTCinvestigating

   Kunder i den centrale amerikanske region har i øjeblikket en service afbrydelse Ingeniører arbejder aktivt på at opklare problemet. -Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

2. 26. juni 2026 kl. 06.01 UTCidentified

   Problemet er blevet identificeret, og ingeniører er oprydning at bringe websteder tilbage online. Ingeniører arbejder aktivt på at opklare problemet. -Næste opdatering forventes inden for 60 minutter, eller som berettiget af en ændring af begivenheder. Undskyld for ulejligheden. StarRez Team

3. 26. juni 2026 kl. 06.10 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 26. juni 2026 kl. 06.10 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

5. 26. juni 2026 kl. 06.13 UTCresolved

   Denne hændelse er blevet løst.

6. 30. juni 2026 kl. 01.51 UTCpostmortem

   * * Oversigt * * Den 26. juni 2026 oplevede StarRez en serviceafbrydelse, der påvirkede StarRez Cloud-kunder i den centrale amerikanske region. StarRez Cloud applikationer var ikke tilgængelige for berørte kunder begynder omkring 05: 47 UTC. Alle berørte kundesteder blev genoprettet til fuld drift ved 06: 06 UTC den 26. juni 2026. * * Rodårsag * * Afbrydelsen skyldtes en konfigurationsændring anvendt på infrastruktur, der understøtter StarRez Cloud i den centrale amerikanske region. Ændringen forårsagede, at kundemiljøer blev midlertidigt utilgængelige, mens infrastrukturen stabiliserede sig. * * Opløsning * * StarRez ingeniører identificerede problemet hurtigt og tog omgående skridt til at genoprette den berørte infrastruktur til en sund stat. Alle kundesteder i den centrale amerikanske region blev bekræftet fuldt operationelle af 06: 06 UTC, ca. 19 minutter efter afbrydelsen begyndte. * * Næste skridt * * StarRez er ved at gennemføre yderligere vagter omkring konfiguration til cloud ressourcer for at forhindre gentagelse af denne klasse af spørgsmål i fremtiden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 00.14 UTCresolved

   This incident has been resolved.

1. 11. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 04.48 UTCmonitoring

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

5. 11. juni 2026 kl. 06.03 UTCresolved

   This incident has been resolved.

1. 11. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 11.41 UTCresolved

   This incident has been resolved.

1. 1. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 16.42 UTCresolved

   This incident has been resolved.

1. 28. april 2026 kl. 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. april 2026 kl. 12.58 UTCresolved

   This incident has been resolved.

1. 10. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 12.59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. marts 2026 kl. 14.02 UTCresolved

   This incident has been resolved.

1. 4. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 01.36 UTCresolved

   This incident has been resolved

1. 4. marts 2026 kl. 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. marts 2026 kl. 16.02 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. marts 2026 kl. 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. marts 2026 kl. 18.34 UTCresolved

   This incident has been resolved.

5. 31. marts 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 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. januar 2026 kl. 06.00 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23. januar 2026 kl. 08.22 UTCresolved

   This incident has been resolved.

1. 5. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 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. december 2025 kl. 11.34 UTCresolved

   This incident has been resolved

1. 25. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 10.03 UTCresolved

   This incident has been resolved.