Störungsverlauf von Starrez

1. 31. August 2026 um 23:11 UTCinvestigating

   Kunden in Australien South East erleben derzeit eine Service-Störung Ingenieure arbeiten aktiv daran, das Problem zu beheben. -Das nächste Update wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

2. 31. August 2026 um 23:19 UTCidentified

   Das Problem wurde identifiziert und StarRez Engineers arbeiten aktiv an einer Minderung des Problems. Die nächste Aktualisierung wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

3. 31. August 2026 um 23:32 UTCidentified

   Es wurde ein Fix umgesetzt, und wir sehen eine Rückkehr der Stabilität in die Region. StarRez Engineers wird die Rückkehr zum Normalbetrieb genau beobachten Nächste Aktualisierung, wie durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

4. 31. August 2026 um 23:32 UTCmonitoring

   Es wurde ein Fix umgesetzt, und wir sehen eine Rückkehr der Stabilität in die Region. StarRez Engineers wird die Rückkehr zum Normalbetrieb genau beobachten Nächste Aktualisierung, wie durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

5. 1. September 2026 um 00:18 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. August 2026 um 16:02 UTCinvestigating

   THD-Kunden, die den SFTP-Server data-03.datacenter.adirondacksolutions.com nutzen, erleben eine Serviceunterbrechung. Ingenieure arbeiten aktiv daran, das Problem zu beheben. Das nächste Update ist innerhalb von 60 Minuten fällig oder wie durch Änderungen von Ereignissen gerechtfertigt.

2. 27. August 2026 um 17:05 UTCinvestigating

   Ingenieure arbeiten aktiv daran, das Problem zu beheben. Die nächste Aktualisierung wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt.

3. 27. August 2026 um 17:52 UTCidentified

   Das Problem wurde identifiziert und Ingenieure beheben. Das nächste Update ist innerhalb von 60 Minuten fällig oder wie durch Änderungen von Ereignissen gerechtfertigt.

4. 27. August 2026 um 18:39 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 27. August 2026 um 20:06 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. August 2026 um 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 um 15:29 UTCinvestigating

   Our upstream provider is continuing to investigate the issue.

3. 13. August 2026 um 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 um 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 um 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 um 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 um 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 um 23:12 UTCmonitoring

   We are continuing to monitor for any further issues.

9. 14. August 2026 um 00:23 UTCresolved

   This incident has been resolved.

1. 13. August 2026 um 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 um 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 um 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 um 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 um 06:30 UTCresolved

   This incident has been resolved.

1. 12. August 2026 um 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 um 04:24 UTCmonitoring

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

3. 12. August 2026 um 06:50 UTCresolved

   This incident has been resolved.

1. 11. August 2026 um 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 um 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 um 20:27 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 11. August 2026 um 20:27 UTCresolved

   This incident has been resolved.

1. 23. Juli 2026 um 14:56 UTCinvestigating

   Kunden in der Region West-USA erleben derzeit eine Service-Störung Ingenieure arbeiten aktiv daran, das Problem zu beheben. - Das nächste Update wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

2. 23. Juli 2026 um 15:52 UTCidentified

   Wir haben ein Problem mit einem vorgelagerten Dienstleister identifiziert, das sich auf die Verfügbarkeit für alle Kunden in der Region West US auswirkt. Wir haben das Problem mit dem Anbieter eskaliert, um die Sanierung zu beschleunigen, und überwachen die Situation aktiv. Weitere Updates werden geteilt, sobald mehr Informationen verfügbar sind.

3. 23. Juli 2026 um 16:50 UTCidentified

   Der Upstream-Dienstleister hat ein Problem mit der Netzwerkinfrastruktur in der Region West-USA bestätigt. Wir beobachten die Situation aktiv. Weitere Updates werden geteilt, sobald mehr Informationen verfügbar sind.

4. 23. Juli 2026 um 18:07 UTCidentified

   Der Upstream-Dienstleister hat ein Problem mit der Netzwerkinfrastruktur in der Region West-USA bestätigt. Das Upstream-Problem ist noch nicht gelöst. Wir verfolgen aktiv Disaster-Recovery-Verfahren, um die Verfügbarkeit für betroffene Kunden wiederherzustellen. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

5. 23. Juli 2026 um 18:52 UTCmonitoring

   Der vorgelagerte Dienstleister hat eine Behebung für das Problem der Netzwerkinfrastruktur in der Region West-USA implementiert. Die Funktionalität der Kundenwebsite wird wiederhergestellt, wenn der Fix ausgerollt wird Wir beobachten die Situation aktiv. Weitere Updates werden geteilt, sobald mehr Informationen verfügbar sind.

6. 23. Juli 2026 um 20:48 UTCresolved

   Dieser Vorfall wurde behoben.

7. 31. Juli 2026 um 13:22 UTCpostmortem

   **Übersicht ** Am 23. Juli 2026 erlebte StarRez eine Serviceunterbrechung, die StarRez Cloud-Kunden in der West-US-Region betraf. StarRez Cloud-Anwendungen waren für betroffene Kunden ab ca. 14:44 UTC nicht verfügbar. Alle betroffenen Kundenstandorte wurden am 23. Juli 2026 bis 19:24 Uhr UTC wieder in Betrieb genommen. **Wurzelursache** Die Störung wurde durch einen regionalen Netzwerkausfall verursacht, der von einem Upstream-Dienstleister ausgelöst wurde. Die Änderung führte dazu, dass betroffene Kundenumgebungen für einige Stunden vorübergehend nicht verfügbar waren, während der Upstream-Dienstleister daran arbeitete, die Netzwerkprobleme zu lösen. **Resolution** Die StarRez-Ingenieure erkannten das Problem umgehend und ergriffen sofortige Maßnahmen, um den Umfang des Ausfalls zu bestätigen und hochgradige Supportfälle beim Upstream-Anbieter anzusprechen. Nachdem wir den Ausfall beim Upstream-Anbieter bestätigt hatten, begannen unsere Ingenieure mit der Ausführung eines Disaster-Recovery-Plans, um Kundenstandorte in einer benachbarten Cloud-Region wieder online zu bringen. Nachdem der Upstream-Anbieter die zugrunde liegenden Netzwerkprobleme behoben hatte, wurden alle Kundenstandorte in ihrer konfigurierten Cloud-Region im Westen der USA wiederhergestellt und bis 19:24 UTC, etwa 4,5 Stunden nach Beginn der Störung, voll funktionsfähig bestätigt. **Nächste Schritte** StarRez wird die regionale Infrastruktur weiterhin überwachen und sich mit Upstream-Anbietern abstimmen, um die Auswirkungen zukünftiger Störungen zu minimieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. Juni 2026 um 05:53 UTCinvestigating

   Kunden in der zentralen US-Region haben derzeit eine Service-Störung Ingenieure arbeiten aktiv daran, das Problem zu beheben. -Das nächste Update wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

2. 26. Juni 2026 um 06:01 UTCidentified

   Das Problem wurde identifiziert und Ingenieure beheben, um Websites wieder online zu bringen. Ingenieure arbeiten aktiv daran, das Problem zu beheben. -Das nächste Update wird innerhalb von 60 Minuten erwartet oder durch eine Änderung der Ereignisse gerechtfertigt. Entschuldigung für jegliche Unannehmlichkeiten, StarRez Team

3. 26. Juni 2026 um 06:10 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 26. Juni 2026 um 06:10 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

5. 26. Juni 2026 um 06:13 UTCresolved

   Dieser Vorfall wurde behoben.

6. 30. Juni 2026 um 01:51 UTCpostmortem

   **Übersicht ** Am 26. Juni 2026 erlebte StarRez eine Serviceunterbrechung, die StarRez Cloud-Kunden in der zentralen US-Region betraf. StarRez Cloud-Anwendungen waren für betroffene Kunden ab etwa 05:47 UTC nicht verfügbar. Alle betroffenen Kundenstandorte wurden am 26. Juni 2026 bis 06:06 UTC wieder in Betrieb genommen. **Wurzelursache** Die Störung wurde durch eine Konfigurationsänderung verursacht, die auf die Infrastruktur angewendet wurde, die StarRez Cloud in der zentralen US-Region unterstützt. Die Änderung führte dazu, dass betroffene Kundenumgebungen vorübergehend nicht mehr verfügbar waren, während sich die Infrastruktur stabilisierte. **Resolution** Die StarRez-Ingenieure erkannten das Problem umgehend und ergriffen sofortige Maßnahmen, um die betroffene Infrastruktur in einen gesunden Zustand zu versetzen. Alle Kundenstandorte in der zentralen US-Region wurden bis 06:06 UTC, etwa 19 Minuten nach Beginn der Störung, als voll funktionsfähig bestätigt. **Nächste Schritte** StarRez implementiert weitere Leitplanken für die Konfiguration von Cloud-Ressourcen, um ein Wiederauftreten dieser Problemklasse in Zukunft zu verhindern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 12. Juni 2026 um 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 um 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 um 00:14 UTCresolved

   This incident has been resolved.

1. 11. Juni 2026 um 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 um 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 um 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 um 04:48 UTCmonitoring

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

5. 11. Juni 2026 um 06:03 UTCresolved

   This incident has been resolved.

1. 11. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 11:41 UTCresolved

   This incident has been resolved.

1. 1. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 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. Mai 2026 um 16:42 UTCresolved

   This incident has been resolved.

1. 28. April 2026 um 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 um 12:58 UTCresolved

   This incident has been resolved.

1. 10. März 2026 um 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. März 2026 um 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. März 2026 um 12:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. März 2026 um 14:02 UTCresolved

   This incident has been resolved.

1. 4. März 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 01:36 UTCresolved

   This incident has been resolved

1. 4. März 2026 um 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. März 2026 um 16:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. März 2026 um 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. März 2026 um 18:34 UTCresolved

   This incident has been resolved.

5. 31. März 2026 um 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 um 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 um 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 um 06:00 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23. Januar 2026 um 08:22 UTCresolved

   This incident has been resolved.

1. 5. Dezember 2025 um 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. Dezember 2025 um 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. Dezember 2025 um 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. Dezember 2025 um 11:34 UTCresolved

   This incident has been resolved

1. 25. November 2025 um 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 um 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 um 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 um 10:03 UTCresolved

   This incident has been resolved.