Rfpio driftsforstyrrelser

1. 17. august 2026 kl. 15.04 UTCinvestigating

   Vi undersøger i øjeblikket et problem, hvor nogle af kunderne var ude af stand til at bruge AI-funktioner.

2. 17. august 2026 kl. 15.04 UTCidentified

   Vi har identificeret årsagen til problemet, og holdet arbejder på et fix.

3. 17. august 2026 kl. 16.21 UTCmonitoring

   Holdet har implementeret fixet, og vi overvåger nøje stabiliteten i tjenesterne.

4. 17. august 2026 kl. 16.35 UTCresolved

   AI tjenester er blevet genoprettet og fungerer nu normalt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 17. juli 2026 kl. 12.05 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et spørgsmål, der berører importtjenesten.

2. 17. juli 2026 kl. 12.05 UTCidentified

   Vi har identificeret årsagen til problemet, og holdet arbejder på et fix.

3. 17. juli 2026 kl. 12.11 UTCmonitoring

   Holdet har implementeret fixet og overvåger nu tjenestens stabilitet.

4. 17. juli 2026 kl. 12.20 UTCresolved

   Importtjenesterne fungerer nu normalt, og problemet er løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juni 2026 kl. 07.45 UTCinvestigating

   Vi oplever i øjeblikket en afbrydelse, der påvirker Trust Center produktet.

2. 27. juni 2026 kl. 07.46 UTCidentified

   Vores team har identificeret det underliggende problem og arbejder aktivt på at genoprette tjenesten så hurtigt som muligt.

3. 27. juni 2026 kl. 07.47 UTCmonitoring

   Vores team har implementeret fixet, og vi overvåger nøje stabiliteten af tjenesterne.

4. 27. juni 2026 kl. 07.49 UTCresolved

   Trust Center produkt er fuldt operationelt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. maj 2026 kl. 08.40 UTCinvestigating

   We are aware of an ongoing Microsoft Azure infrastructure incident affecting multiple services in the West US 2 region. Customers may experience increased latency, intermittent connectivity, request timeouts, or service accessibility issues for workloads that depend on Azure resources hosted in this region. Current Status Microsoft has reported a power-related event impacting infrastructure within the West US 2 region. The incident is affecting several Azure services, including compute, storage, networking, monitoring, and database services. At this time, we are closely monitoring updates from Microsoft regarding the incident and its resolution. Microsoft is actively working to restore affected infrastructure components and services. Additional Information Customers can track the latest updates directly from Microsoft Azure Status: https://azure.status.microsoft/en-gb/status

2. 1. juni 2026 kl. 03.53 UTCresolved

   All services have been confirmed to be operating normally.

1. 21. maj 2026 kl. 08.09 UTCinvestigating

   We are currently investigating an issue affecting GCP Pod1 infrastructure, which has resulted in authentication problems for a subset of customers.

2. 21. maj 2026 kl. 08.10 UTCidentified

   We have identified the cause of the issue on GCP Pod1, and the team is working on a fix.

3. 21. maj 2026 kl. 08.11 UTCmonitoring

   The team has implemented the fix and is now monitoring the environment’s stability.

4. 21. maj 2026 kl. 08.13 UTCresolved

   All services on GCP Pod1 have been confirmed to be operating normally.

1. 28. april 2026 kl. 06.01 UTCinvestigating

   We are currently investigating an issue affecting customers in the GCP cluster, which is causing a service outage.

2. 28. april 2026 kl. 06.04 UTCidentified

   We are currently investigating a major outage affecting customers in GCP POD1. The impacted service is failing health checks and cannot be reached from the database.

3. 28. april 2026 kl. 06.27 UTCmonitoring

   The issue was identified as a database scaling issue, which caused connectivity failures. The team is closely monitoring the services.

4. 28. april 2026 kl. 06.44 UTCresolved

   The issue has been resolved, and the service is now functioning normally. No new health check failures have been detected.

1. 15. april 2026 kl. 05.06 UTCinvestigating

   Azure OpenAI services are currently experiencing issues in the US East regions. Customers using AI-powered features may see intermittent HTTP 5XX errors and higher latency, which can lead to 408 timeouts in these regions.

2. 15. april 2026 kl. 05.08 UTCidentified

   The Azure team has detected this issue through their monitoring and is currently working on a fix.

3. 15. april 2026 kl. 12.37 UTCresolved

   The Azure OpenAI service degradation has been resolved, and all AI-powered features are now fully operational following confirmed stability from Microsoft.

1. 14. april 2026 kl. 16.32 UTCinvestigating

   We are currently investigating an issue where some of the customers were unable to use translation services.

2. 14. april 2026 kl. 16.33 UTCidentified

   We have identified the cause of the issue, and the team is working on a fix.

3. 14. april 2026 kl. 16.52 UTCmonitoring

   The team has implemented the fix, and we are closely monitoring the stability of the services.

4. 14. april 2026 kl. 17.01 UTCresolved

   Translation services are confirmed to be functioning normally.

1. 26. marts 2026 kl. 12.54 UTCinvestigating

   We are currently investigating an issue affecting service availability for a Panasonic customer in the US West region.

2. 26. marts 2026 kl. 12.55 UTCidentified

   We have identified the cause of the service disruptions, and the team is working on a fix.

3. 26. marts 2026 kl. 12.55 UTCmonitoring

   The team has applied the fix, and we are closely monitoring the stability of the environment.

4. 26. marts 2026 kl. 12.56 UTCresolved

   The issue has been fully resolved. All services have been confirmed as stable, and performance has returned to normal level.

1. 26. marts 2026 kl. 09.58 UTCinvestigating

   We are investigating reports of intermittent latency and partial service degradation. Users may experience slower response time.

2. 26. marts 2026 kl. 09.59 UTCidentified

   We have identified the issue, and the team is currently working on a fix.

3. 26. marts 2026 kl. 10.30 UTCmonitoring

   The team has applied the fix, and we are closely monitoring the stability of the environment.

4. 26. marts 2026 kl. 10.55 UTCresolved

   All services have been fully restored and are now operating normally.

1. 25. marts 2026 kl. 08.49 UTCinvestigating

   We are currently investigating search service instability within the Oracle Environment

2. 25. marts 2026 kl. 08.51 UTCidentified

   The root cause has been identified, and the team is working on a fix.

3. 25. marts 2026 kl. 08.51 UTCmonitoring

   We are monitoring system performance and data consistency to ensure the environment remains stable.

4. 25. marts 2026 kl. 08.53 UTCresolved

   The issue is now fully resolved, and the search service is functioning normally.

1. 19. marts 2026 kl. 16.30 UTCinvestigating

   We are currently investigating an issue impacting service availability on EU Pod1, which has resulted in site downtime for customers.

2. 19. marts 2026 kl. 16.31 UTCidentified

   We have identified the cause of the service disruptions on EU Pod1, and the team is working on a fix.

3. 19. marts 2026 kl. 16.32 UTCmonitoring

   The team has applied the fix, and we are closely monitoring the stability of the environment.

4. 19. marts 2026 kl. 16.33 UTCresolved

   All services on EU Pod1 have been confirmed to be operating normally.

1. 10. marts 2026 kl. 10.23 UTCidentified

   Azure OpenAI services are currently experiencing issues across multiple regions. Customers using AI-powered features may encounter service disruptions or reduced performance.

2. 10. marts 2026 kl. 10.24 UTCmonitoring

   We are actively monitoring the situation and will provide regular updates as soon as we receive additional information from Microsoft Azure.

3. 10. marts 2026 kl. 13.29 UTCmonitoring

   We are actively monitoring the Azure status page, and the service has not yet recovered. We will provide updates on the progress.

4. 11. marts 2026 kl. 01.59 UTCresolved

   The Azure OpenAI service degradation has been resolved, and all AI-powered features are now fully operational following confirmed stability from Microsoft.

1. 9. marts 2026 kl. 10.20 UTCinvestigating

   We are currently investigating an issue impacting service availability on EU Pod1, which has resulted in site downtime for customers.

2. 9. marts 2026 kl. 10.21 UTCidentified

   We have identified the cause of the service disruptions on EU Pod1, and the team is working on a fix.

3. 9. marts 2026 kl. 10.25 UTCresolved

   The team has applied the fix and resolved the issue. All services on EU Pod1 have been confirmed to be operating normally.

1. 7. februar 2026 kl. 09.45 UTCinvestigating

   We are currently investigating an issue affecting service availability on Azure Pod, which has led to site unavailability for a subset of customers.

2. 7. februar 2026 kl. 09.47 UTCidentified

   Azure has posted the following to their public Status Page: https://azure.status.microsoft/en-us/status Ongoing Service Degradation in West US region Starting at 08:00 UTC, we became aware of an issue affecting multiple services for a subset of customers in the West US region.Our engineering teams are actively investigating and working to mitigate the service disruption impacting the region.We will provide more information as soon as it becomes available.

3. 7. februar 2026 kl. 19.33 UTCmonitoring

   All services in the impacted Azure West US region have recovered. We will continue to monitor and provide updates.

4. 7. februar 2026 kl. 19.35 UTCresolved

   The incident has been resolved.

1. 1. december 2025 kl. 11.16 UTCinvestigating

   We are currently investigating an issue affecting service availability on Pod1, which has led to site unavailability for a subset of customers.

2. 1. december 2025 kl. 11.17 UTCidentified

   We have identified the cause of the service disruptions on Pod1, and the team is working on a fix.

3. 1. december 2025 kl. 11.24 UTCresolved

   The team has applied the fix and resolved the issue. All services on Pod1 have been confirmed to be operating normally.

1. 24. november 2025 kl. 15.12 UTCinvestigating

   We are currently investigating an issue that is causing intermittent failures for users of the Azure pod login service.

2. 24. november 2025 kl. 15.13 UTCidentified

   The team has identified the issue and is currently working on a fix.

3. 24. november 2025 kl. 15.18 UTCresolved

   The team has applied the fix and resolved the issue. The authentication service is now functioning normally, and no new health check failures have been detected.

1. 2. november 2025 kl. 23.34 UTCinvestigating

   We are currently investigating an issue where POD3 is unable to establish a connection to the Database

2. 2. november 2025 kl. 23.35 UTCidentified

   The affected service reporting failed health checks and is unreachable from the database.

3. 2. november 2025 kl. 23.38 UTCmonitoring

   The replica node has been restored.POD 3 is now able to connect to the database, and services are functioning as expected.

4. 2. november 2025 kl. 23.38 UTCresolved

   The issue has been resolved, and the service is now functioning normally. No new health check failures have been detected.

1. 20. oktober 2025 kl. 10.00 UTCinvestigating

   We are currently facing an outage in AWS East-1 (North Virginia) region, AWS has reported a service disruption in the region, impacting multiple services. Customers in this region might face degraded performance, increased latency.

2. 20. oktober 2025 kl. 10.05 UTCidentified

   AWS is currently investigating increased error rates and latencies affecting multiple services. AWS is working on a fix.

3. 20. oktober 2025 kl. 10.11 UTCmonitoring

   AWS has implemented initial mitigations and is closely monitoring the impacted services in the US-EAST-1 region.

4. 21. oktober 2025 kl. 03.49 UTCresolved

   All impacted AWS services had fully recovered, and operations returned to normal across the US-EAST-1 region. Our internal workloads and monitoring confirm stable and healthy service performance across all integrated AWS environments.

1. 16. oktober 2025 kl. 04.59 UTCinvestigating

   We are currently investigating an issue impacting the customers in AWS POD1 . The service is experiencing outage for customers.

2. 16. oktober 2025 kl. 05.02 UTCidentified

   We are currently investigating a major outage impacting customers in AWS POD1. The affected service reporting failed health checks and is unreachable from the database.

3. 16. oktober 2025 kl. 05.06 UTCmonitoring

   The issue was identified as a database scaling issue, which caused connectivity failures. The team is closely monitoring the services.

4. 16. oktober 2025 kl. 05.07 UTCresolved

   The issue has been resolved, and the service is now functioning normally. No new health check failures have been detected.