RecoveryLink Outage History

RecoveryLink is up right now

RecoveryLink had 2 outages in the last 2 years totaling 44h 28m of downtime, averaging 0.1 incidents per month.

There were 2 RecoveryLink outages since November 5, 2024 totaling 44h 28m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.myrecoverylink.com

Major June 12, 2025

Application Connectivity: Google Cloud Platform Outage

Detected by Pingoru
Jun 12, 2025, 06:34 PM UTC
Resolved
Jun 14, 2025, 12:01 PM UTC
Duration
1d 17h
Affected: Electronic Recovery Record
Timeline · 4 updates
  1. investigating Jun 12, 2025, 06:34 PM UTC

    We are aware that our core application infrastructure provider (Google Cloud Platform) is experiencing a major outage. Users may experience degraded performance, including inability to login. We are monitoring the situation closely for resolution.

  2. identified Jun 12, 2025, 07:04 PM UTC

    The issue has been identified as a major outage at a third party provider, Google Cloud Platform. The Google team is working on resolving their outage as our team continues to monitor the issue.

  3. monitoring Jun 12, 2025, 07:20 PM UTC

    A fix has begun to be implement by the Google team. We are seeing improvements and login capabilities returning to most customers at this time.

  4. resolved Jun 14, 2025, 12:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 5, 2024

Primary Outage - Core Platform

Detected by Pingoru
Nov 05, 2024, 06:40 PM UTC
Resolved
Nov 05, 2024, 09:42 PM UTC
Duration
3h 1m
Affected: Electronic Recovery Record
Timeline · 4 updates
  1. investigating Nov 05, 2024, 06:40 PM UTC

    We are currently investigating this issue.

  2. identified Nov 05, 2024, 07:26 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 05, 2024, 07:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Nov 05, 2024, 09:42 PM UTC

    This incident has been resolved.

Read the full incident report →