RFPIO Outage History

RFPIO is up right now

RFPIO had 29 outages in the last 2 years totaling 132h 20m of downtime — averaging 1.2 incidents per month.

There were 29 RFPIO outages since July 19, 2024 totaling 132h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.rfpio.com

Notice July 17, 2026

Import service degradation affected a subset of customers

Detected by Pingoru
Jul 17, 2026, 12:05 PM UTC
Resolved
Jul 17, 2026, 12:20 PM UTC
Duration
15m
Timeline · 4 updates
  1. investigating Jul 17, 2026, 12:05 PM UTC

    We are currently investigating an issue affecting the import service.

  2. identified Jul 17, 2026, 12:05 PM UTC

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

  3. monitoring Jul 17, 2026, 12:11 PM UTC

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

  4. resolved Jul 17, 2026, 12:20 PM UTC

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

Read the full incident report →

Notice June 26, 2026

Trust Center Product disruption affected a subset of customers

Detected by Pingoru
Jun 26, 2026, 12:15 PM UTC
Resolved
Jun 26, 2026, 04:30 PM UTC
Duration
4h 15m
Timeline · 4 updates
  1. investigating Jun 27, 2026, 07:45 AM UTC

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

  2. identified Jun 27, 2026, 07:46 AM UTC

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

  3. monitoring Jun 27, 2026, 07:47 AM UTC

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

  4. resolved Jun 27, 2026, 07:49 AM UTC

    Trust Center product is fully operational.

Read the full incident report →

Notice May 29, 2026

Azure Multi-Service Degradation in West US 2 Region

Detected by Pingoru
May 29, 2026, 08:40 AM UTC
Resolved
Jun 01, 2026, 03:53 AM UTC
Duration
2d 19h
Affected: Azure Pod2
Timeline · 2 updates
  1. investigating May 29, 2026, 08:40 AM UTC

    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. resolved Jun 01, 2026, 03:53 AM UTC

    All services have been confirmed to be operating normally.

Read the full incident report →

Minor May 21, 2026

Minor Service Disruptions for customers in GCP Pod1

Detected by Pingoru
May 21, 2026, 07:15 AM UTC
Resolved
May 21, 2026, 07:30 AM UTC
Duration
14m
Affected: GCP Pod1
Timeline · 4 updates
  1. investigating May 21, 2026, 08:09 AM UTC

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

  2. identified May 21, 2026, 08:10 AM UTC

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

  3. monitoring May 21, 2026, 08:11 AM UTC

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

  4. resolved May 21, 2026, 08:13 AM UTC

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

Read the full incident report →

Minor April 28, 2026

Major Service Disruptions for customers in GCP cluster.

Detected by Pingoru
Apr 28, 2026, 06:01 AM UTC
Resolved
Apr 28, 2026, 06:44 AM UTC
Duration
42m
Affected: GCP Pod1
Timeline · 4 updates
  1. investigating Apr 28, 2026, 06:01 AM UTC

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

  2. identified Apr 28, 2026, 06:04 AM UTC

    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. monitoring Apr 28, 2026, 06:27 AM UTC

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

  4. resolved Apr 28, 2026, 06:44 AM UTC

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

Read the full incident report →

Notice April 15, 2026

Azure OpenAI Service disruptions in US East Region

Detected by Pingoru
Apr 15, 2026, 05:06 AM UTC
Resolved
Apr 15, 2026, 12:37 PM UTC
Duration
7h 30m
Timeline · 3 updates
  1. investigating Apr 15, 2026, 05:06 AM UTC

    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. identified Apr 15, 2026, 05:08 AM UTC

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

  3. resolved Apr 15, 2026, 12:37 PM UTC

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

Read the full incident report →

Notice April 14, 2026

Translation service disruption affected a subset of customers

Detected by Pingoru
Apr 14, 2026, 04:32 PM UTC
Resolved
Apr 14, 2026, 05:01 PM UTC
Duration
28m
Timeline · 4 updates
  1. investigating Apr 14, 2026, 04:32 PM UTC

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

  2. identified Apr 14, 2026, 04:33 PM UTC

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

  3. monitoring Apr 14, 2026, 04:52 PM UTC

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

  4. resolved Apr 14, 2026, 05:01 PM UTC

    Translation services are confirmed to be functioning normally.

Read the full incident report →

Major March 26, 2026

Service Disruptions for Panasonic Customer in US West Region.

Detected by Pingoru
Mar 26, 2026, 12:54 PM UTC
Resolved
Mar 26, 2026, 12:56 PM UTC
Duration
1m
Affected: US Pod5
Timeline · 4 updates
  1. investigating Mar 26, 2026, 12:54 PM UTC

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

  2. identified Mar 26, 2026, 12:55 PM UTC

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

  3. monitoring Mar 26, 2026, 12:55 PM UTC

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

  4. resolved Mar 26, 2026, 12:56 PM UTC

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

Read the full incident report →

Minor March 26, 2026

Partial degradation of service unavailability for a subset of customers.

Detected by Pingoru
Mar 26, 2026, 08:30 AM UTC
Resolved
Mar 26, 2026, 10:15 AM UTC
Duration
1h 44m
Timeline · 4 updates
  1. investigating Mar 26, 2026, 09:58 AM UTC

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

  2. identified Mar 26, 2026, 09:59 AM UTC

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

  3. monitoring Mar 26, 2026, 10:30 AM UTC

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

  4. resolved Mar 26, 2026, 10:55 AM UTC

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

Read the full incident report →

Major March 23, 2026

Search service disruption affected a subset of customers in Oracle Environment

Detected by Pingoru
Mar 23, 2026, 05:45 AM UTC
Resolved
Mar 23, 2026, 07:15 AM UTC
Duration
1h 30m
Affected: OCI Pod1
Timeline · 4 updates
  1. investigating Mar 25, 2026, 08:49 AM UTC

    We are currently investigating search service instability within the Oracle Environment

  2. identified Mar 25, 2026, 08:51 AM UTC

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

  3. monitoring Mar 25, 2026, 08:51 AM UTC

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

  4. resolved Mar 25, 2026, 08:53 AM UTC

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

Read the full incident report →

Major March 19, 2026

Service Disruptions for customers in AWS EU-West

Detected by Pingoru
Mar 19, 2026, 02:12 PM UTC
Resolved
Mar 19, 2026, 02:30 PM UTC
Duration
17m
Affected: EU Pod1
Timeline · 4 updates
  1. investigating Mar 19, 2026, 04:30 PM UTC

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

  2. identified Mar 19, 2026, 04:31 PM UTC

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

  3. monitoring Mar 19, 2026, 04:32 PM UTC

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

  4. resolved Mar 19, 2026, 04:33 PM UTC

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

Read the full incident report →

Minor March 10, 2026

Degraded Performance: Azure OpenAI Services

Detected by Pingoru
Mar 10, 2026, 10:23 AM UTC
Resolved
Mar 11, 2026, 01:59 AM UTC
Duration
15h 36m
Timeline · 4 updates
  1. identified Mar 10, 2026, 10:23 AM UTC

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

  2. monitoring Mar 10, 2026, 10:24 AM UTC

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

  3. monitoring Mar 10, 2026, 01:29 PM UTC

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

  4. resolved Mar 11, 2026, 01:59 AM UTC

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

Read the full incident report →

Critical March 9, 2026

Major Service Disruptions for customers in AWS EU-West

Detected by Pingoru
Mar 09, 2026, 08:49 AM UTC
Resolved
Mar 09, 2026, 10:00 AM UTC
Duration
1h 10m
Affected: EU Pod1
Timeline · 3 updates
  1. investigating Mar 09, 2026, 10:20 AM UTC

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

  2. identified Mar 09, 2026, 10:21 AM UTC

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

  3. resolved Mar 09, 2026, 10:25 AM UTC

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

Read the full incident report →

Major February 7, 2026

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

Detected by Pingoru
Feb 07, 2026, 08:00 AM UTC
Resolved
Feb 07, 2026, 07:35 PM UTC
Duration
11h 35m
Affected: Azure Pod1
Timeline · 4 updates
  1. investigating Feb 07, 2026, 09:45 AM UTC

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

  2. identified Feb 07, 2026, 09:47 AM UTC

    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. monitoring Feb 07, 2026, 07:33 PM UTC

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

  4. resolved Feb 07, 2026, 07:35 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor December 1, 2025

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

Detected by Pingoru
Dec 01, 2025, 11:16 AM UTC
Resolved
Dec 01, 2025, 11:24 AM UTC
Duration
8m
Affected: US Pod1
Timeline · 3 updates
  1. investigating Dec 01, 2025, 11:16 AM UTC

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

  2. identified Dec 01, 2025, 11:17 AM UTC

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

  3. resolved Dec 01, 2025, 11:24 AM UTC

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

Read the full incident report →

Minor November 24, 2025

Authentication Failure issue in one of the Azure Pod

Detected by Pingoru
Nov 24, 2025, 03:12 PM UTC
Resolved
Nov 24, 2025, 03:18 PM UTC
Duration
5m
Affected: Azure Pod1
Timeline · 3 updates
  1. investigating Nov 24, 2025, 03:12 PM UTC

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

  2. identified Nov 24, 2025, 03:13 PM UTC

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

  3. resolved Nov 24, 2025, 03:18 PM UTC

    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.

Read the full incident report →

Critical November 2, 2025

Major Service Disruptions for customers in AWS POD3

Detected by Pingoru
Nov 02, 2025, 11:34 PM UTC
Resolved
Nov 02, 2025, 11:38 PM UTC
Duration
4m
Affected: US Pod3
Timeline · 4 updates
  1. investigating Nov 02, 2025, 11:34 PM UTC

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

  2. identified Nov 02, 2025, 11:35 PM UTC

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

  3. monitoring Nov 02, 2025, 11:38 PM UTC

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

  4. resolved Nov 02, 2025, 11:38 PM UTC

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

Read the full incident report →

Critical October 20, 2025

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

Detected by Pingoru
Oct 20, 2025, 07:11 AM UTC
Resolved
Oct 20, 2025, 10:00 PM UTC
Duration
14h 49m
Affected: US Pod2US Pod9US Pod11
Timeline · 4 updates
  1. investigating Oct 20, 2025, 10:00 AM UTC

    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. identified Oct 20, 2025, 10:05 AM UTC

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

  3. monitoring Oct 20, 2025, 10:11 AM UTC

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

  4. resolved Oct 21, 2025, 03:49 AM UTC

    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.

Read the full incident report →

Critical October 16, 2025

Major Service Disruptions for customers in AWS POD1

Detected by Pingoru
Oct 16, 2025, 04:47 AM UTC
Resolved
Oct 16, 2025, 04:54 AM UTC
Duration
7m
Affected: US Pod1
Timeline · 4 updates
  1. investigating Oct 16, 2025, 04:59 AM UTC

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

  2. identified Oct 16, 2025, 05:02 AM UTC

    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. monitoring Oct 16, 2025, 05:06 AM UTC

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

  4. resolved Oct 16, 2025, 05:07 AM UTC

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

Read the full incident report →

Notice October 13, 2025

Partial degradation of external services on AWS

Detected by Pingoru
Oct 13, 2025, 03:00 PM UTC
Resolved
Oct 13, 2025, 04:30 PM UTC
Duration
1h 30m
Affected: Domain Service
Timeline · 3 updates
  1. identified Oct 14, 2025, 10:55 AM UTC

    We are currently investigating an issue impacting the AWS External Service. The service is experiencing intermittent failures.

  2. monitoring Oct 14, 2025, 10:55 AM UTC

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

  3. resolved Oct 14, 2025, 10:58 AM UTC

    The issue has been resolved, and the AWS External Service is now functioning normally and no new health check failures have been detected.

Read the full incident report →

Minor September 23, 2025

Planned Cloud Maintenance on Oracle compute services

Detected by Pingoru
Sep 23, 2025, 05:31 AM UTC
Resolved
Sep 23, 2025, 07:06 AM UTC
Duration
1h 34m
Affected: OCI Pod1
Timeline · 3 updates
  1. monitoring Sep 23, 2025, 05:31 AM UTC

    Oracle is performing maintenance on compute services. During the maintenance timeframe customers in the impacted regions may experience a short service interruptions(less than 5mins)

  2. monitoring Sep 23, 2025, 05:38 AM UTC

    Our engineering teams are actively monitoring all service components to ensure operational continuity. Further updates will be provided as additional information becomes available.

  3. resolved Sep 23, 2025, 07:06 AM UTC

    Planned maintenance has been completed.

Read the full incident report →

Major September 15, 2025

Search service disruption affected a subset of customers

Detected by Pingoru
Sep 15, 2025, 03:32 PM UTC
Resolved
Sep 15, 2025, 03:52 PM UTC
Duration
20m
Affected: US Pod2
Timeline · 4 updates
  1. investigating Sep 16, 2025, 04:43 AM UTC

    Some customers were unable to access search services in AWS POD2, and the services became unavailable on September 15 at 21:02 IST.

  2. identified Sep 16, 2025, 04:43 AM UTC

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

  3. monitoring Sep 16, 2025, 04:45 AM UTC

    Search Services on AWS POD2 have been restored. We are actively monitoring the system to ensure stability.

  4. resolved Sep 16, 2025, 04:46 AM UTC

    The issue has been resolved, and search services are operating normally.RCA will be shared shortly.

Read the full incident report →

Major June 6, 2025

Some of the Customers were not able to access the Content Library

Detected by Pingoru
Jun 06, 2025, 02:05 PM UTC
Resolved
Jun 06, 2025, 02:21 PM UTC
Duration
15m
Affected: US Pod2
Timeline · 4 updates
  1. investigating Jun 06, 2025, 02:15 PM UTC

    Some of the Customers were not able to access the Content Library

  2. identified Jun 06, 2025, 02:16 PM UTC

    A service disruption has impacted access to the Content Library for some customers in the US region. We have identified the affected service and are actively working on restoring it.

  3. monitoring Jun 06, 2025, 02:17 PM UTC

    The affected service has been restored. We are continuing to monitor our services.

  4. resolved Jun 06, 2025, 02:21 PM UTC

    The incident has been resolved. We will update the RCA soon.

Read the full incident report →

Major March 13, 2025

Some of the Customers may encounter disruptions in the application

Detected by Pingoru
Mar 13, 2025, 07:28 PM UTC
Resolved
Mar 13, 2025, 07:45 PM UTC
Duration
16m
Affected: US Pod1
Timeline · 4 updates
  1. investigating Mar 17, 2025, 11:22 AM UTC

    Some of the Customers were not able to access the Content Library

  2. identified Mar 17, 2025, 11:24 AM UTC

    A service disruption has impacted access to the Content Library for some customers in the US region. We have identified the affected service and are actively working on restoring it.

  3. monitoring Mar 17, 2025, 11:25 AM UTC

    The affected service has been restored. We are continuing to monitor our services.

  4. resolved Mar 17, 2025, 11:26 AM UTC

    The incident has been resolved. We will update the RCA soon.

Read the full incident report →

Major February 24, 2025

Some customers reported login issues

Detected by Pingoru
Feb 24, 2025, 04:22 PM UTC
Resolved
Feb 24, 2025, 04:54 PM UTC
Duration
31m
Affected: US Pod1
Timeline · 4 updates
  1. investigating Feb 24, 2025, 04:50 PM UTC

    We are currently investigating the issue.

  2. identified Feb 24, 2025, 04:52 PM UTC

    A disruption in one of our services has caused login issues for some customers in a US region. We have identified the affected service and are actively working to restore it.

  3. monitoring Feb 24, 2025, 04:53 PM UTC

    The affected service has been restored. We are continuing to monitor our services.

  4. resolved Feb 24, 2025, 04:54 PM UTC

    The incident has been resolved. RCA: A sudden increase in search service temporarily affected application accessibility. Our team acted immediately to restore the service and has implemented improvements to ensure stability moving forward.

Read the full incident report →