Planday incident

Service disruption caused by a third party provider

Minor Resolved View vendor source →

Planday experienced a minor incident on October 9, 2025 affecting Web and Open API, lasting 9h 20m. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2025, 08:47 AM UTC
Resolved
Oct 09, 2025, 06:07 PM UTC
Duration
9h 20m
Detected by Pingoru
Oct 09, 2025, 08:47 AM UTC

Affected components

WebOpen API

Update timeline

  1. investigating Oct 09, 2025, 08:47 AM UTC

    We are currently experiencing a service disruption due to an incident at one of our third-party providers. We will update here as soon as we receive additional information from our provider.

  2. identified Oct 09, 2025, 09:26 AM UTC

    Our third party provider is still investigating and working on a mitigating the issue on their end that is causing a service disruption in our product. We will update here as soon as we receive additional information from our provider.

  3. identified Oct 09, 2025, 09:36 AM UTC

    Our third party provider is still investigating and working on a mitigating the issue on their end that is causing a service disruption in our product. We will update here as soon as we receive additional information from our provider.

  4. monitoring Oct 09, 2025, 11:20 AM UTC

    Our monitoring shows that the issue is currently mitigated for our users. We will, however, keep this incident open until our third party provider confirms permanent fix.

  5. monitoring Oct 09, 2025, 12:34 PM UTC

    While our third-party provider has reported that the majority of impact is mitigated, some Planday users might experience intermittent performance issues in the product. We are currently monitoring the incident at our service provider and will update this page as events warrant.

  6. monitoring Oct 09, 2025, 03:02 PM UTC

    Our provider is still working on fully mitigating the issue on their end. We will continue monitoring the incident at our service provider and will update this page as events warrant.

  7. resolved Oct 09, 2025, 06:07 PM UTC

    The incident has been resolved.