Istoricul incidentelor Starrez

1. 31 august 2026 la 23:11 UTCinvestigating

   Clienţii din Australia de Sud-Est se confruntă în prezent cu o întrerupere a serviciilor - Motoarele lucrează activ pentru a remedia problema. -Următoarea actualizare aşteptată în 60 de minute, sau după cum se justifică printr-o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

2. 31 august 2026 la 23:19 UTCidentified

   Problema a fost identificată și inginerii StarRez lucrează activ la atenuarea problemei. Următoarea actualizare aşteptată în decurs de 60 de minute, sau după cum se justifică printr-o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

3. 31 august 2026 la 23:32 UTCidentified

   A fost pusă în aplicare o soluţie şi vedem cum stabilitatea revine în regiune. Inginerii StarRez vor monitoriza îndeaproape pentru a confirma o revenire la funcționarea normală Următoarea actualizare este justificată de o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

4. 31 august 2026 la 23:32 UTCmonitoring

   A fost pusă în aplicare o soluţie şi vedem cum stabilitatea revine în regiune. Inginerii StarRez vor monitoriza îndeaproape pentru a confirma o revenire la funcționarea normală Următoarea actualizare este justificată de o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

5. 1 septembrie 2026 la 00:18 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 27 august 2026 la 16:02 UTCinvestigating

   Clientii THD folosind serverul SFTP date-03.datacenter.adirondacksolutions.com se confrunta cu o perturbare a serviciilor. Inginerii lucrează activ la remedierea problemei. Următoarea actualizare este datorată în termen de 60 de minute, sau după cum se justifică prin modificări ale evenimentelor.

2. 27 august 2026 la 17:05 UTCinvestigating

   Inginerii lucrează activ la remedierea problemei. Următoarea actualizare aşteptată în decurs de 60 de minute, sau după cum se justifică printr-o schimbare a evenimentelor.

3. 27 august 2026 la 17:52 UTCidentified

   Problema a fost identificată și inginerii sunt de remediere. Următoarea actualizare este datorată în termen de 60 de minute, sau după cum se justifică prin modificări ale evenimentelor.

4. 27 august 2026 la 18:39 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

5. 27 august 2026 la 20:06 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

   Our upstream provider is continuing to investigate the issue.

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

   We are continuing to monitor for any further issues.

9. 14 august 2026 la 00:23 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 12 august 2026 la 06:50 UTCresolved

   This incident has been resolved.

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

   We are continuing to monitor for any further issues.

4. 11 august 2026 la 20:27 UTCresolved

   This incident has been resolved.

1. 23 iulie 2026 la 14:56 UTCinvestigating

   Clienţii din regiunea vest-americană se confruntă în prezent cu o perturbare a serviciilor - Inginerii lucrează activ pentru a remedia problema. - Următoarea actualizare aşteptată în 60 de minute, sau după cum se justifică prin schimbarea evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

2. 23 iulie 2026 la 15:52 UTCidentified

   Am identificat o problemă cu un furnizor de servicii în amonte care afectează disponibilitatea tuturor clienților din regiunea vest-americană. Am escaladat problema cu furnizorul pentru a accelera remedierea și monitorizează în mod activ situația. Alte actualizări vor fi comunicate pe măsură ce devin disponibile mai multe informații.

3. 23 iulie 2026 la 16:50 UTCidentified

   Furnizorul de servicii din amonte a confirmat o problemă de infrastructură de rețea în regiunea vest-americană. Monitorizăm în mod activ situaţia. Alte actualizări vor fi comunicate pe măsură ce devin disponibile mai multe informații.

4. 23 iulie 2026 la 18:07 UTCidentified

   Furnizorul de servicii din amonte a confirmat o problemă de infrastructură de rețea în regiunea vest-americană. Problema din amonte nu a fost încă rezolvată. Urmărim în mod activ procedurile de recuperare a dezastrelor pentru a restabili disponibilitatea pentru clienții afectați. Îmi cer scuze pentru neplăceri. Echipa StarRez

5. 23 iulie 2026 la 18:52 UTCmonitoring

   Furnizorul de servicii din amonte a implementat un fix de remediere pentru problema infrastructurii de rețea din regiunea vest-americană. Funcţionalitatea site-ului clienţilor va începe să fie restabilită pe măsură ce fix este rulat Monitorizăm în mod activ situaţia. Alte actualizări vor fi comunicate pe măsură ce devin disponibile mai multe informații.

6. 23 iulie 2026 la 20:48 UTCresolved

   Acest incident a fost rezolvat.

7. 31 iulie 2026 la 13:22 UTCpostmortem

   **Overview** La 23 iulie 2026, StarRez s-a confruntat cu o perturbare a serviciilor care afectează clienții StarRez Cloud din regiunea vest-americană. Aplicațiile StarRez Cloud nu au fost disponibile pentru clienții afectați începând cu aproximativ 14:44 UTC. Toate site-urile de clienți afectate au fost restaurate la funcționarea completă de 19:24 UTC la 23 iulie 2026. **Root Cause** Perturbația a fost cauzată de o întrerupere de rețea la nivel regional declanșată de un furnizor de servicii din amonte. Modificarea a determinat ca mediile de clienți afectate să devină temporar indisponibile pentru mai multe ore, în timp ce furnizorul de servicii din amonte a lucrat pentru a rezolva problemele de rețea. **Rezoluţie** Inginerii StarRez au identificat problema cu promptitudine și au luat măsuri imediate pentru a confirma domeniul de aplicare al întreruperii și a ridica cazuri de sprijin de mare severitate la furnizorul din amonte. După confirmarea întreruperii cu furnizorul din amonte, inginerii noştri au început să execute un plan de recuperare în caz de dezastru pentru a readuce site-urile clienţilor online într-o regiune învecinată a norilor. Odată ce furnizorul din amonte a rezolvat problemele de rețea subiacente, toate site-urile de clienți au fost restaurate în regiunea cloud configurată din vestul SUA și au fost confirmate pe deplin operaționale până la 19:24 UTC, la aproximativ 4,5 ore după începerea întreruperii. **Următoarele etape** StarRez va continua monitorizarea sănătăţii infrastructurii regionale şi va coordona cu furnizorii din amonte pentru a minimiza impactul eventualelor perturbări viitoare.

Traducere automată din actualizarea oficială a incidentului.

1. 26 iunie 2026 la 05:53 UTCinvestigating

   Clienţii din regiunea centrală a SUA au în prezent o întrerupere a serviciilor - Motoarele lucrează activ pentru a remedia problema. -Următoarea actualizare aşteptată în 60 de minute, sau după cum se justifică printr-o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

2. 26 iunie 2026 la 06:01 UTCidentified

   Problema a fost identificată și inginerii sunt de remediere pentru a aduce site-uri înapoi on-line. - Motoarele lucrează activ pentru a remedia problema. -Următoarea actualizare aşteptată în 60 de minute, sau după cum se justifică printr-o schimbare a evenimentelor. Îmi cer scuze pentru neplăceri. Echipa StarRez

3. 26 iunie 2026 la 06:10 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 26 iunie 2026 la 06:10 UTCmonitoring

   Continuăm să monitorizăm orice alte probleme.

5. 26 iunie 2026 la 06:13 UTCresolved

   Acest incident a fost rezolvat.

6. 30 iunie 2026 la 01:51 UTCpostmortem

   **Overview** La 26 iunie 2026, StarRez s-a confruntat cu o perturbare a serviciilor care afectează clienții StarRez Cloud din regiunea centrală a SUA. Aplicațiile StarRez Cloud nu au fost disponibile pentru clienții afectați începând cu aproximativ 05:47 UTC. Toate site-urile de clienți afectate au fost restaurate la funcționarea completă de 06:06 UTC la 26 iunie 2026. **Root Cause** Întreruperea a fost cauzată de o modificare a configurației aplicată infrastructurii care sprijină StarRez Cloud în regiunea centrală a SUA. Modificarea a determinat ca mediile de clienţi afectate să devină temporar indisponibile în timp ce infrastructura s-a stabilizat. **Rezoluţie** Inginerii StarRez au identificat problema cu promptitudine și au luat măsuri imediate pentru a restabili infrastructura afectată într-o stare sănătoasă. Toate site-urile clienților din regiunea centrală a SUA au fost confirmate complet operaționale până la 06:06 UTC, la aproximativ 19 minute după începerea întreruperii. **Următoarele etape** StarRez implementează noi balustrade în jurul configuraţiei pentru a preveni repetarea acestei clase de probleme în viitor.

Traducere automată din actualizarea oficială a incidentului.

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

   This incident has been resolved.

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

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

5. 11 iunie 2026 la 06:03 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 la 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 iunie 2026 la 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 la 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 la 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 la 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 la 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 la 11:41 UTCresolved

   This incident has been resolved.

1. 1 mai 2026 la 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 la 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 la 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 la 16:42 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 10 martie 2026 la 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 martie 2026 la 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 martie 2026 la 12:59 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 martie 2026 la 14:02 UTCresolved

   This incident has been resolved.

1. 4 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 01:36 UTCresolved

   This incident has been resolved

1. 4 martie 2026 la 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 martie 2026 la 16:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 martie 2026 la 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 martie 2026 la 18:34 UTCresolved

   This incident has been resolved.

5. 31 martie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 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 ianuarie 2026 la 06:00 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 ianuarie 2026 la 08:22 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved

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

   This incident has been resolved.