Historial de interrupciones de Rfpio

1. 17 de agosto de 2026 a las 15:04 UTCinvestigating

   Actualmente estamos investigando un problema donde algunos de los clientes no pudieron usar características de IA.

2. 17 de agosto de 2026 a las 15:04 UTCidentified

   Hemos identificado la causa del problema, y el equipo está trabajando en una solución.

3. 17 de agosto de 2026 a las 16:21 UTCmonitoring

   El equipo ha implementado la solución, y estamos monitoreando de cerca la estabilidad de los servicios.

4. 17 de agosto de 2026 a las 16:35 UTCresolved

   Los servicios de inteligencia artificial han sido restaurados y ahora funcionan normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de julio de 2026 a las 12:05 UTCinvestigating

   Actualmente estamos investigando una cuestión que afecta al servicio de importación.

2. 17 de julio de 2026 a las 12:05 UTCidentified

   Hemos identificado la causa del problema, y el equipo está trabajando en una solución.

3. 17 de julio de 2026 a las 12:11 UTCmonitoring

   El equipo ha implementado la solución y ahora está monitoreando la estabilidad del servicio.

4. 17 de julio de 2026 a las 12:20 UTCresolved

   Los servicios de importación están operando normalmente, y la cuestión se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 27 de junio de 2026 a las 7:45 UTCinvestigating

   Actualmente estamos experimentando un outage que afecta al producto del Centro Fiduciario.

2. 27 de junio de 2026 a las 7:46 UTCidentified

   Nuestro equipo ha identificado la cuestión subyacente y está trabajando activamente para restaurar el servicio lo antes posible.

3. 27 de junio de 2026 a las 7:47 UTCmonitoring

   Nuestro equipo ha implementado la solución, y estamos monitoreando de cerca la estabilidad de los servicios.

4. 27 de junio de 2026 a las 7:49 UTCresolved

   El producto del centro de confianza está totalmente operativo.

Traducido automáticamente desde la actualización oficial del incidente.

1. 29 de mayo de 2026 a las 8: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 de junio de 2026 a las 3:53 UTCresolved

   All services have been confirmed to be operating normally.

1. 21 de mayo de 2026 a las 8: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 de mayo de 2026 a las 8:10 UTCidentified

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

3. 21 de mayo de 2026 a las 8:11 UTCmonitoring

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

4. 21 de mayo de 2026 a las 8:13 UTCresolved

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

1. 28 de abril de 2026 a las 6:01 UTCinvestigating

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

2. 28 de abril de 2026 a las 6: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 de abril de 2026 a las 6:27 UTCmonitoring

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

4. 28 de abril de 2026 a las 6:44 UTCresolved

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

1. 15 de abril de 2026 a las 5: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 de abril de 2026 a las 5:08 UTCidentified

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

3. 15 de abril de 2026 a las 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 de abril de 2026 a las 16:32 UTCinvestigating

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

2. 14 de abril de 2026 a las 16:33 UTCidentified

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

3. 14 de abril de 2026 a las 16:52 UTCmonitoring

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

4. 14 de abril de 2026 a las 17:01 UTCresolved

   Translation services are confirmed to be functioning normally.

1. 26 de marzo de 2026 a las 12:54 UTCinvestigating

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

2. 26 de marzo de 2026 a las 12:55 UTCidentified

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

3. 26 de marzo de 2026 a las 12:55 UTCmonitoring

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

4. 26 de marzo de 2026 a las 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 de marzo de 2026 a las 9:58 UTCinvestigating

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

2. 26 de marzo de 2026 a las 9:59 UTCidentified

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

3. 26 de marzo de 2026 a las 10:30 UTCmonitoring

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

4. 26 de marzo de 2026 a las 10:55 UTCresolved

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

1. 25 de marzo de 2026 a las 8:49 UTCinvestigating

   We are currently investigating search service instability within the Oracle Environment

2. 25 de marzo de 2026 a las 8:51 UTCidentified

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

3. 25 de marzo de 2026 a las 8:51 UTCmonitoring

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

4. 25 de marzo de 2026 a las 8:53 UTCresolved

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

1. 19 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 16:32 UTCmonitoring

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

4. 19 de marzo de 2026 a las 16:33 UTCresolved

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

1. 10 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 1: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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de febrero de 2026 a las 9: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 de febrero de 2026 a las 9: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 de febrero de 2026 a las 19:33 UTCmonitoring

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

4. 7 de febrero de 2026 a las 19:35 UTCresolved

   The incident has been resolved.

1. 1 de diciembre de 2025 a las 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 de diciembre de 2025 a las 11:17 UTCidentified

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

3. 1 de diciembre de 2025 a las 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 de noviembre de 2025 a las 15:12 UTCinvestigating

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

2. 24 de noviembre de 2025 a las 15:13 UTCidentified

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

3. 24 de noviembre de 2025 a las 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 de noviembre de 2025 a las 23:34 UTCinvestigating

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

2. 2 de noviembre de 2025 a las 23:35 UTCidentified

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

3. 2 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 10:05 UTCidentified

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

3. 20 de octubre de 2025 a las 10:11 UTCmonitoring

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

4. 21 de octubre de 2025 a las 3: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 de octubre de 2025 a las 4:59 UTCinvestigating

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

2. 16 de octubre de 2025 a las 5: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 de octubre de 2025 a las 5:06 UTCmonitoring

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

4. 16 de octubre de 2025 a las 5:07 UTCresolved

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