RFPIO Outage History

RFPIO is up right now

There were 10 RFPIO outages since February 7, 2026 totaling 40h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.rfpio.com

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 →

Looking to track RFPIO downtime and outages?

Pingoru polls RFPIO's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when RFPIO reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track RFPIO alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring RFPIO for free

5 free monitors · No credit card required