Sympa HR incident

Issues with SFTP file transfers

Major Resolved View vendor source →

Sympa HR experienced a major incident on June 12, 2026 affecting Integrations, lasting 4h 15m. The incident has been resolved; the full update timeline is below.

Started
Jun 12, 2026, 09:08 AM UTC
Resolved
Jun 12, 2026, 01:23 PM UTC
Duration
4h 15m
Detected by Pingoru
Jun 12, 2026, 09:08 AM UTC

Affected components

Integrations

Update timeline

  1. investigating Jun 12, 2026, 09:08 AM UTC

    Dear Customer, We are currently experiencing issues with our SFTP servers. This may affect incoming and outgoing file transfers through Integrations / Connectivity, including CSV files and other automated file exchanges. Our team is investigating the issue and working to restore normal service as soon as possible. We will provide further updates as soon as more information is available. Your Sympa Team

  2. monitoring Jun 12, 2026, 09:57 AM UTC

    Dear Customer, The SFTP service has recovered and is currently available again. The service was unavailable today between 11:51 and 12:08 EEST, which may have affected incoming and outgoing file transfers through Integrations / Connectivity during that time. Integrations are expected to continue from where they left off now that the service is available again. Our team is monitoring the service to confirm continued stability before closing the incident. Your Sympa Team

  3. resolved Jun 12, 2026, 01:23 PM UTC

    Dear Customer, According to our monitoring, the SFTP service has remained stable and file transfers through Integrations / Connectivity are operating normally again. We are now closing this incident. Your Sympa Team

  4. postmortem Jul 02, 2026, 01:55 PM UTC

    **What happened** * The SFTP server became unavailable, preventing customers from connecting and exchanging files \(including CSV transfers\) through our Integrations and Connectivity features. **Why it happened** * This was caused by two separate issues. First, a disk-related fault made the server inaccessible. After we restored access, we identified a second issue: a network connectivity problem, caused by a security rule change, that continued to block customer connections on a recurring basis until it was fully resolved. **What we did** * Identified and resolved the network connectivity issue affecting the server. * Set up a new network connection for the server. * Adjusted the security configuration that was repeatedly blocking connectivity. * Verified the SFTP server was accessible and confirmed file transfers resumed successfully. **What we're doing to prevent this in future** * Improving monitoring and alerting for storage capacity, so similar issues are caught before they impact service. * Reviewing our recovery procedures to reduce time-to-resolution for infrastructure incidents. * Confirming the security configuration change is permanent so the connectivity issue cannot reoccur.