Historique des pannes de Rfpio

1. 17 août 2026 à 15:04 UTCinvestigating

   Nous enquêtons actuellement sur une question où certains clients n'ont pas pu utiliser les fonctionnalités d'IA.

2. 17 août 2026 à 15:04 UTCidentified

   Nous avons identifié la cause du problème, et l'équipe travaille sur une solution.

3. 17 août 2026 à 16:21 UTCmonitoring

   L'équipe a mis en place la solution et nous surveillons de près la stabilité des services.

4. 17 août 2026 à 16:35 UTCresolved

   Les services d'IA ont été restaurés et fonctionnent maintenant normalement.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 juillet 2026 à 12:05 UTCinvestigating

   Nous enquêtons actuellement sur un problème touchant le service d'importation.

2. 17 juillet 2026 à 12:05 UTCidentified

   Nous avons identifié la cause du problème, et l'équipe travaille sur une solution.

3. 17 juillet 2026 à 12:11 UTCmonitoring

   L'équipe a mis en œuvre le correctif et surveille maintenant la stabilité du service.

4. 17 juillet 2026 à 12:20 UTCresolved

   Les services d'importation fonctionnent maintenant normalement, et le problème a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 27 juin 2026 à 07:45 UTCinvestigating

   Nous vivons actuellement une panne affectant le produit Trust Center.

2. 27 juin 2026 à 07:46 UTCidentified

   Notre équipe a identifié le problème sous-jacent et s'emploie activement à rétablir le service le plus rapidement possible.

3. 27 juin 2026 à 07:47 UTCmonitoring

   Notre équipe a mis en place la solution et nous surveillons de près la stabilité des services.

4. 27 juin 2026 à 07:49 UTCresolved

   Trust Center produit est pleinement opérationnel.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 29 mai 2026 à 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 juin 2026 à 03:53 UTCresolved

   All services have been confirmed to be operating normally.

1. 21 mai 2026 à 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 mai 2026 à 08:10 UTCidentified

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

3. 21 mai 2026 à 08:11 UTCmonitoring

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

4. 21 mai 2026 à 08:13 UTCresolved

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

1. 28 avril 2026 à 06:01 UTCinvestigating

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

2. 28 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 05:08 UTCidentified

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

3. 15 avril 2026 à 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 avril 2026 à 16:32 UTCinvestigating

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

2. 14 avril 2026 à 16:33 UTCidentified

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

3. 14 avril 2026 à 16:52 UTCmonitoring

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

4. 14 avril 2026 à 17:01 UTCresolved

   Translation services are confirmed to be functioning normally.

1. 26 mars 2026 à 12:54 UTCinvestigating

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

2. 26 mars 2026 à 12:55 UTCidentified

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

3. 26 mars 2026 à 12:55 UTCmonitoring

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

4. 26 mars 2026 à 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 mars 2026 à 09:58 UTCinvestigating

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

2. 26 mars 2026 à 09:59 UTCidentified

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

3. 26 mars 2026 à 10:30 UTCmonitoring

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

4. 26 mars 2026 à 10:55 UTCresolved

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

1. 25 mars 2026 à 08:49 UTCinvestigating

   We are currently investigating search service instability within the Oracle Environment

2. 25 mars 2026 à 08:51 UTCidentified

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

3. 25 mars 2026 à 08:51 UTCmonitoring

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

4. 25 mars 2026 à 08:53 UTCresolved

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

1. 19 mars 2026 à 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 mars 2026 à 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 mars 2026 à 16:32 UTCmonitoring

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

4. 19 mars 2026 à 16:33 UTCresolved

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

1. 10 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 février 2026 à 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 février 2026 à 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 février 2026 à 19:33 UTCmonitoring

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

4. 7 février 2026 à 19:35 UTCresolved

   The incident has been resolved.

1. 1 décembre 2025 à 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 décembre 2025 à 11:17 UTCidentified

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

3. 1 décembre 2025 à 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 novembre 2025 à 15:12 UTCinvestigating

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

2. 24 novembre 2025 à 15:13 UTCidentified

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

3. 24 novembre 2025 à 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 novembre 2025 à 23:34 UTCinvestigating

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

2. 2 novembre 2025 à 23:35 UTCidentified

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

3. 2 novembre 2025 à 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 novembre 2025 à 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 octobre 2025 à 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 octobre 2025 à 10:05 UTCidentified

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

3. 20 octobre 2025 à 10:11 UTCmonitoring

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

4. 21 octobre 2025 à 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 octobre 2025 à 04:59 UTCinvestigating

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

2. 16 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 05:07 UTCresolved

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