Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

Rfpio outage history

53 recorded Rfpio incidents since February 2024, with official updates, affected components, duration and resolution information.

Back to current status

AI service features degraded in the EU cluster

Started August 17, 2026 at 3:04 PM UTC · 1h 31m

IssuesMinor incident
Affected components
EU Pod1
  1. August 17, 2026 at 3:04 PM UTCinvestigating

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

  2. August 17, 2026 at 3:04 PM UTCidentified

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

  3. August 17, 2026 at 4:21 PM UTCmonitoring

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

  4. August 17, 2026 at 4:35 PM UTCresolved

    AI services have been restored and are now functioning normally.

Import service degradation affected a subset of customers

Started July 17, 2026 at 12:05 PM UTC · 15m

Pending
  1. July 17, 2026 at 12:05 PM UTCinvestigating

    We are currently investigating an issue affecting the import service.

  2. July 17, 2026 at 12:05 PM UTCidentified

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

  3. July 17, 2026 at 12:11 PM UTCmonitoring

    The team has implemented the fix and is now monitoring the service stability.

  4. July 17, 2026 at 12:20 PM UTCresolved

    Import services are now operating normally, and the issue has been resolved.

Trust Center Product disruption affected a subset of customers

Started June 26, 2026 at 12:15 PM UTC · 4h 15m

Pending
  1. June 27, 2026 at 7:45 AM UTCinvestigating

    We are currently experiencing an outage affecting the Trust Center product.

  2. June 27, 2026 at 7:46 AM UTCidentified

    Our team has identified the underlying issue and is actively working to restore service as quickly as possible.

  3. June 27, 2026 at 7:47 AM UTCmonitoring

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

  4. June 27, 2026 at 7:49 AM UTCresolved

    Trust Center product is fully operational.

Azure Multi-Service Degradation in West US 2 Region

Started May 29, 2026 at 8:40 AM UTC · 2d 19h

Pending
Affected components
Azure Pod2
  1. May 29, 2026 at 8:40 AM 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. June 1, 2026 at 3:53 AM UTCresolved

    All services have been confirmed to be operating normally.

Minor Service Disruptions for customers in GCP Pod1

Started May 21, 2026 at 7:15 AM UTC · 14m

IssuesMinor incident
Affected components
GCP Pod1
  1. May 21, 2026 at 8:09 AM UTCinvestigating

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

  2. May 21, 2026 at 8:10 AM UTCidentified

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

  3. May 21, 2026 at 8:11 AM UTCmonitoring

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

  4. May 21, 2026 at 8:13 AM UTCresolved

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

Major Service Disruptions for customers in GCP cluster.

Started April 28, 2026 at 6:01 AM UTC · 43m

IssuesMinor incident
Affected components
GCP Pod1
  1. April 28, 2026 at 6:01 AM UTCinvestigating

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

  2. April 28, 2026 at 6:04 AM 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. April 28, 2026 at 6:27 AM UTCmonitoring

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

  4. April 28, 2026 at 6:44 AM UTCresolved

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

Azure OpenAI Service disruptions in US East Region

Started April 15, 2026 at 5:06 AM UTC · 7h 31m

Pending
  1. April 15, 2026 at 5:06 AM 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. April 15, 2026 at 5:08 AM UTCidentified

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

  3. April 15, 2026 at 12:37 PM UTCresolved

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

Translation service disruption affected a subset of customers

Started April 14, 2026 at 4:32 PM UTC · 29m

Pending
  1. April 14, 2026 at 4:32 PM UTCinvestigating

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

  2. April 14, 2026 at 4:33 PM UTCidentified

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

  3. April 14, 2026 at 4:52 PM UTCmonitoring

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

  4. April 14, 2026 at 5:01 PM UTCresolved

    Translation services are confirmed to be functioning normally.

Service Disruptions for Panasonic Customer in US West Region.

Started March 26, 2026 at 12:54 PM UTC · 2m

OutageMajor incident
Affected components
US Pod5
  1. March 26, 2026 at 12:54 PM UTCinvestigating

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

  2. March 26, 2026 at 12:55 PM UTCidentified

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

  3. March 26, 2026 at 12:55 PM UTCmonitoring

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

  4. March 26, 2026 at 12:56 PM UTCresolved

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

Partial degradation of service unavailability for a subset of customers.

Started March 26, 2026 at 8:30 AM UTC · 1h 45m

IssuesMinor incident
  1. March 26, 2026 at 9:58 AM UTCinvestigating

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

  2. March 26, 2026 at 9:59 AM UTCidentified

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

  3. March 26, 2026 at 10:30 AM UTCmonitoring

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

  4. March 26, 2026 at 10:55 AM UTCresolved

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

Search service disruption affected a subset of customers in Oracle Environment

Started March 23, 2026 at 5:45 AM UTC · 1h 30m

OutageMajor incident
Affected components
OCI Pod1
  1. March 25, 2026 at 8:49 AM UTCinvestigating

    We are currently investigating search service instability within the Oracle Environment

  2. March 25, 2026 at 8:51 AM UTCidentified

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

  3. March 25, 2026 at 8:51 AM UTCmonitoring

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

  4. March 25, 2026 at 8:53 AM UTCresolved

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

Service Disruptions for customers in AWS EU-West

Started March 19, 2026 at 2:12 PM UTC · 18m

OutageMajor incident
Affected components
EU Pod1
  1. March 19, 2026 at 4:30 PM UTCinvestigating

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

  2. March 19, 2026 at 4:31 PM UTCidentified

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

  3. March 19, 2026 at 4:32 PM UTCmonitoring

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

  4. March 19, 2026 at 4:33 PM UTCresolved

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

Degraded Performance: Azure OpenAI Services

Started March 10, 2026 at 10:23 AM UTC · 15h 37m

IssuesMinor incident
  1. March 10, 2026 at 10:23 AM UTCidentified

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

  2. March 10, 2026 at 10:24 AM UTCmonitoring

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

  3. March 10, 2026 at 1:29 PM UTCmonitoring

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

  4. March 11, 2026 at 1:59 AM UTCresolved

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

Major Service Disruptions for customers in AWS EU-West

Started March 9, 2026 at 8:49 AM UTC · 1h 11m

OutageCritical incident
Affected components
EU Pod1
  1. March 9, 2026 at 10:20 AM UTCinvestigating

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

  2. March 9, 2026 at 10:21 AM UTCidentified

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

  3. March 9, 2026 at 10:25 AM UTCresolved

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

Partial degradation of Azure POD service unavailability for a subset of customers.

Started February 7, 2026 at 8:00 AM UTC · 11h 35m

OutageMajor incident
Affected components
Azure Pod1
  1. February 7, 2026 at 9:45 AM 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. February 7, 2026 at 9:47 AM 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. February 7, 2026 at 7:33 PM UTCmonitoring

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

  4. February 7, 2026 at 7:35 PM UTCresolved

    The incident has been resolved.

Partial degradation of POD1 service unavailability for a subset of customers.

Started December 1, 2025 at 11:16 AM UTC · 9m

IssuesMinor incident
Affected components
US Pod1
  1. December 1, 2025 at 11:16 AM UTCinvestigating

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

  2. December 1, 2025 at 11:17 AM UTCidentified

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

  3. December 1, 2025 at 11:24 AM UTCresolved

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

Authentication Failure issue in one of the Azure Pod

Started November 24, 2025 at 3:12 PM UTC · 5m

IssuesMinor incident
Affected components
Azure Pod1
  1. November 24, 2025 at 3:12 PM UTCinvestigating

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

  2. November 24, 2025 at 3:13 PM UTCidentified

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

  3. November 24, 2025 at 3:18 PM 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.

Major Service Disruptions for customers in AWS POD3

Started November 2, 2025 at 11:34 PM UTC · 4m

OutageCritical incident
Affected components
US Pod3
  1. November 2, 2025 at 11:34 PM UTCinvestigating

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

  2. November 2, 2025 at 11:35 PM UTCidentified

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

  3. November 2, 2025 at 11:38 PM UTCmonitoring

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

  4. November 2, 2025 at 11:38 PM UTCresolved

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

Major service disruptions for customers in AWS US-East -1 region

Started October 20, 2025 at 7:11 AM UTC · 14h 50m

OutageCritical incident
Affected components
US Pod9US Pod11US Pod2
  1. October 20, 2025 at 10:00 AM 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. October 20, 2025 at 10:05 AM UTCidentified

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

  3. October 20, 2025 at 10:11 AM UTCmonitoring

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

  4. October 21, 2025 at 3:49 AM 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.

Major Service Disruptions for customers in AWS POD1

Started October 16, 2025 at 4:47 AM UTC · 7m

OutageCritical incident
Affected components
US Pod1
  1. October 16, 2025 at 4:59 AM UTCinvestigating

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

  2. October 16, 2025 at 5:02 AM 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. October 16, 2025 at 5:06 AM UTCmonitoring

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

  4. October 16, 2025 at 5:07 AM UTCresolved

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