PayFit Outage History

PayFit had 2 outages in the last 2 years totaling 28h 50m of downtime — averaging 0.1 incidents per month.

There were 2 PayFit outages since May 20, 2025 totaling 28h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.payfit.com

Minor April 27, 2026

Service degraded due to AWS outage in the Paris region

Detected by Pingoru: Apr 27, 2026, 10:58 AM UTC
Resolved: Apr 27, 2026, 11:59 AM UTC
Duration: 1h 1m

Affected: Payslip previewRun PayrollLeave managementImportsContract terminationHelp center

Timeline · 1 update

resolved Apr 27, 2026, 11:59 AM UTC

From 12:58 to 13:24 CEST, an AWS outage in the Paris region (power outage in one of their datacenters) caused widespread service disruption across our app and some connected services. While the AWS issue has been resolved, you may have experienced temporary unavailability, delays, or intermittent slowness while it was ongoing or during recovery. We continue to monitor performance and stabilize affected components.

Read the full incident report →

Minor October 20, 2025

Service degraded

Detected by Pingoru: Oct 20, 2025, 07:57 AM UTC
Resolved: Oct 21, 2025, 11:46 AM UTC
Duration: 1d 3h

Affected: Login pagePayslip previewRun PayrollLeave managementImportsContract terminationExpensesStandard integrationsHelp centerCustom integrations

Timeline · 3 updates

investigating Oct 20, 2025, 07:57 AM UTC

We are currently experiencing issues with our service related to one of our Third-parties, including the slow loading of certain pages. Our team is working hard to resolve the problem as soon as possible. We sincerely apologise for the inconvenience. Impact: 🇫🇷 🇬🇧 🇪🇸 customers
monitoring Oct 20, 2025, 09:54 AM UTC

Our team has identified the root cause of the outage, and PayFit is gradually being restored. We are closely monitoring the situation and will continue to provide updates.
resolved Oct 21, 2025, 11:46 AM UTC

The outage has been resolved, and PayFit is now fully operational. Thank you for your patience while we resolved this issue. We are working on ways to prevent similar incidents in the future.

Read the full incident report →