Rfpio 장애 기록

1. 2026년 8월 17일 오후 3:04 UTCinvestigating

   우리는 현재 고객이 AI 기능을 사용할 수없는 문제가 있습니다.

2. 2026년 8월 17일 오후 3:04 UTCidentified

   우리는 문제점의 원인을 확인하고, 팀은 고침에 일하고 있습니다.

3. 2026년 8월 17일 오후 4:21 UTCmonitoring

   팀은 수정을 시행하고 있으며, 서비스의 안정성을 밀접하게 모니터링하고 있습니다.

4. 2026년 8월 17일 오후 4:35 UTCresolved

   AI 서비스는 복원되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 17일 오후 12:05 UTCinvestigating

   우리는 현재 수입 서비스에 영향을 미치는 문제점을 조사하고 있습니다.

2. 2026년 7월 17일 오후 12:05 UTCidentified

   우리는 문제점의 원인을 확인하고, 팀은 고침에 일하고 있습니다.

3. 2026년 7월 17일 오후 12:11 UTCmonitoring

   팀은 수정을 구현하고 서비스 안정성을 모니터링하고 있습니다.

4. 2026년 7월 17일 오후 12:20 UTCresolved

   수입 서비스는 현재 운영되고 있으며, 문제는 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 27일 오전 7:45 UTCinvestigating

   우리는 현재 Trust Center 제품에 영향을 미치는 정전을 경험하고 있습니다.

2. 2026년 6월 27일 오전 7:46 UTCidentified

   우리의 팀은 underlying 문제점을 확인하고 가능한 빨리 회복하기 위하여 적극적으로 일하고 있습니다.

3. 2026년 6월 27일 오전 7:47 UTCmonitoring

   우리의 팀은 수정을 시행하고, 우리는 서비스의 안정성을 밀접하게 감시하고 있습니다.

4. 2026년 6월 27일 오전 7:49 UTCresolved

   Trust Center 제품은 완전히 운영됩니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 29일 오전 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. 2026년 6월 1일 오전 3:53 UTCresolved

   All services have been confirmed to be operating normally.

1. 2026년 5월 21일 오전 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. 2026년 5월 21일 오전 8:10 UTCidentified

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

3. 2026년 5월 21일 오전 8:11 UTCmonitoring

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

4. 2026년 5월 21일 오전 8:13 UTCresolved

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

1. 2026년 4월 28일 오전 6:01 UTCinvestigating

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

2. 2026년 4월 28일 오전 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. 2026년 4월 28일 오전 6:27 UTCmonitoring

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

4. 2026년 4월 28일 오전 6:44 UTCresolved

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

1. 2026년 4월 15일 오전 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. 2026년 4월 15일 오전 5:08 UTCidentified

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

3. 2026년 4월 15일 오후 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. 2026년 4월 14일 오후 4:32 UTCinvestigating

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

2. 2026년 4월 14일 오후 4:33 UTCidentified

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

3. 2026년 4월 14일 오후 4:52 UTCmonitoring

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

4. 2026년 4월 14일 오후 5:01 UTCresolved

   Translation services are confirmed to be functioning normally.

1. 2026년 3월 26일 오후 12:54 UTCinvestigating

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

2. 2026년 3월 26일 오후 12:55 UTCidentified

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

3. 2026년 3월 26일 오후 12:55 UTCmonitoring

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

4. 2026년 3월 26일 오후 12:56 UTCresolved

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

1. 2026년 3월 26일 오전 9:58 UTCinvestigating

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

2. 2026년 3월 26일 오전 9:59 UTCidentified

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

3. 2026년 3월 26일 오전 10:30 UTCmonitoring

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

4. 2026년 3월 26일 오전 10:55 UTCresolved

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

1. 2026년 3월 25일 오전 8:49 UTCinvestigating

   We are currently investigating search service instability within the Oracle Environment

2. 2026년 3월 25일 오전 8:51 UTCidentified

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

3. 2026년 3월 25일 오전 8:51 UTCmonitoring

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

4. 2026년 3월 25일 오전 8:53 UTCresolved

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

1. 2026년 3월 19일 오후 4:30 UTCinvestigating

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

2. 2026년 3월 19일 오후 4:31 UTCidentified

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

3. 2026년 3월 19일 오후 4:32 UTCmonitoring

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

4. 2026년 3월 19일 오후 4:33 UTCresolved

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

1. 2026년 3월 10일 오전 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. 2026년 3월 10일 오전 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. 2026년 3월 10일 오후 1: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. 2026년 3월 11일 오전 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. 2026년 3월 9일 오전 10:20 UTCinvestigating

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

2. 2026년 3월 9일 오전 10:21 UTCidentified

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

3. 2026년 3월 9일 오전 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. 2026년 2월 7일 오전 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. 2026년 2월 7일 오전 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. 2026년 2월 7일 오후 7:33 UTCmonitoring

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

4. 2026년 2월 7일 오후 7:35 UTCresolved

   The incident has been resolved.

1. 2025년 12월 1일 오전 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. 2025년 12월 1일 오전 11:17 UTCidentified

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

3. 2025년 12월 1일 오전 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. 2025년 11월 24일 오후 3:12 UTCinvestigating

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

2. 2025년 11월 24일 오후 3:13 UTCidentified

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

3. 2025년 11월 24일 오후 3: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. 2025년 11월 2일 오후 11:34 UTCinvestigating

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

2. 2025년 11월 2일 오후 11:35 UTCidentified

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

3. 2025년 11월 2일 오후 11: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. 2025년 11월 2일 오후 11:38 UTCresolved

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

1. 2025년 10월 20일 오전 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. 2025년 10월 20일 오전 10:05 UTCidentified

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

3. 2025년 10월 20일 오전 10:11 UTCmonitoring

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

4. 2025년 10월 21일 오전 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. 2025년 10월 16일 오전 4:59 UTCinvestigating

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

2. 2025년 10월 16일 오전 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. 2025년 10월 16일 오전 5:06 UTCmonitoring

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

4. 2025년 10월 16일 오전 5:07 UTCresolved

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