PlanPro Outage History

PlanPro is up right now

PlanPro had 3 outages in the last 2 years totaling 21h 15m of downtime — averaging 0.1 incidents per month.

There were 3 PlanPro outages since November 20, 2024 totaling 21h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://planpro.statuspage.io

Critical May 27, 2026

PlanPro Outage

Detected by Pingoru
May 27, 2026, 12:54 PM UTC
Resolved
May 27, 2026, 01:28 PM UTC
Duration
34m
Affected: Web
Timeline · 4 updates
  1. investigating May 27, 2026, 12:54 PM UTC

    Investigating We are currently investigating an issue affecting the availability of iDocs. Our technical team is working to identify the cause and restore service as quickly as possible.

  2. investigating May 27, 2026, 01:02 PM UTC

    We have identified the issue affecting PlanPro and are actively working on implementing a resolution. We will continue to provide updates as progress is made.

  3. monitoring May 27, 2026, 01:02 PM UTC

    A fix has been implemented for the PlanPro issue, and services are recovering. We are currently monitoring the environment to ensure the platform remains stable and fully operational.

  4. resolved May 27, 2026, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

PlanPro Down due to Cloudflare outage

Detected by Pingoru
Nov 18, 2025, 12:15 PM UTC
Resolved
Nov 18, 2025, 02:59 PM UTC
Duration
2h 43m
Affected: Web
Timeline · 2 updates
  1. investigating Nov 18, 2025, 12:15 PM UTC

    https://www.cloudflarestatus.com/

  2. resolved Nov 18, 2025, 02:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 20, 2024

Cannot create Applicants

Detected by Pingoru
Nov 20, 2024, 11:35 AM UTC
Resolved
Nov 21, 2024, 05:32 AM UTC
Duration
17h 56m
Affected: Web
Timeline · 3 updates
  1. investigating Nov 20, 2024, 11:35 AM UTC

    Cannot create new applicants on the system support team is investigating

  2. monitoring Nov 20, 2024, 11:42 AM UTC

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

  3. resolved Nov 21, 2024, 05:32 AM UTC

    This incident has been resolved.

Read the full incident report →