Revers.io Outage History

Revers.io is up right now

Revers.io had 3 outages in the last 2 years totaling 9h 48m of downtime, averaging 0.1 incidents per month.

There were 3 Revers.io outages since January 3, 2025 totaling 9h 48m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.revers.io

Minor May 22, 2026

Elevated Errors

Detected by Pingoru
May 22, 2026, 08:05 AM UTC
Resolved
May 22, 2026, 10:24 AM UTC
Duration
2h 18m
Affected: BackOfficeSelfCare
Timeline · 3 updates
  1. investigating May 22, 2026, 08:05 AM UTC

    We're experiencing an elevated level of errors and are currently looking into the issue.

  2. identified May 22, 2026, 08:29 AM UTC

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

  3. resolved May 22, 2026, 10:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025

Issue with third-party providers

Detected by Pingoru
Nov 18, 2025, 12:00 PM UTC
Resolved
Nov 18, 2025, 03:16 PM UTC
Duration
3h 16m
Affected: BackOfficeSelfCare
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 12:00 PM UTC

    We are aware of, and investigating an issue with our third-party providers which potentially impacts multiple actions. We are currently monitoring closely.

  2. resolved Nov 18, 2025, 03:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 14, 2025

Elevated API Errors

Detected by Pingoru
Oct 14, 2025, 08:09 AM UTC
Resolved
Oct 14, 2025, 12:23 PM UTC
Duration
4h 13m
Affected: BackOfficeSelfCarePartner Manager
Timeline · 4 updates
  1. investigating Oct 14, 2025, 08:09 AM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. identified Oct 14, 2025, 10:20 AM UTC

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

  3. monitoring Oct 14, 2025, 11:21 AM UTC

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

  4. resolved Oct 14, 2025, 12:23 PM UTC

    This incident has been resolved.

Read the full incident report →