Is Sympa HR down?

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

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

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

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

Fix applied & monitoring We have applied a fix and our SFTP service is now accessible again. Incoming and outgoing file transfers through should now be working normally. Our team is actively monitoring the service to confirm it remains stable. We sincerely appreciate your patience during the disruption. We will post a final update later once we have confirmed the service is fully stable. Your Sympa Team

We are continuing to experience issues with our SFTP service, and connectivity has become unavailable again. Our team is actively investigating the situation and working to restore normal service as quickly as possible. We apologize for the continued disruption and will provide further updates as soon as more information becomes available.

SFTP service is currently accessible again, and incoming and outgoing file transfers are working. We are keeping this incident open while our team continues to monitor the situation closely and confirm the service remains stable. Further updates will be provided as monitoring continues. Your Sympa Team

Our monitoring confirms that SFTP traffic is operating normally again, and both incoming and outgoing file transfers are being processed successfully. The incident has now been resolved and we are closing this case. Integrations automatically resume processing from where they left off once connectivity is restored, and no data loss is expected as a result of this disruption. We will continue to monitor the service to ensure stable operation. Thank you for your patience, and we apologize for the inconvenience caused. Your Sympa Team

We are currently fixing an issue that affects a limited group of customers who are not yet using Sympa’s new user role model. Due to a change activated earlier than intended, some users’ access rights may temporarily not match the intended setup. This means that some users may see less information than expected, while in some cases users may also see information based on role settings that were still being prepared. The issue has been identified and our team is actively working to restore the intended access rights as quickly as possible. We apologise for the disruption and concern this may cause. We will provide the next update here as soon as the fix has progressed. Your Sympa Team

The issue has been identified and a fix is being implemented. Please note this issue is not affecting any customers using new roles already!

Recovery is progressing as planned. We expect the affected users’ access rights to be restored to their previous settings within the next few hours. Some users may regain the correct access sooner. We will share the next update by 12:00 EEST at the latest. Your Sympa Team

Recovery is progressing, and restoration is approximately 25% complete. Some customers may experience general slowness in Sympa during the recovery work. We apologise for the inconvenience. We will share the next update latest at 13:00 EEST. Your Sympa Team

According to further investigation, the experienced issues has resulted in restricted access rights to data and features in the system. The headline of the issue has been updated accordingly. Recovery process is approximately 80% completed. We also confirm that this issue only affects a small number of customers, and according to investigation customer with the Roles feature in use have not been affected by this issue. We will share the next update latest at 14:00 EEST. Your Sympa Team

The recovery process has been completed. The issue has been fixed. We apologise for any inconvenience this disruption may have caused. Your Sympa Team

**Timeline** May 20, 2026, 20:30 EET — Incident started May 21, 2026, 9:07 EET — Incident detected May 21, 2026, 9:17 EET — Incident recovery started May 21, 2026, 11:16 EET — First users access rights recovered May 21, 2026, 13:57 EET — Incident fully mitigated, all affected users access rights recovered   **What happened** During a scheduled update on May 20 at 20:30 EET, an update caused an issue that affected a limited group of customers' users who are not yet using Sympa’s new user roles. Some users’ access rights were temporarily more restricted than intended setup. The affected users didn't see any data in Sympa during the incident.   **Why it happened** An access rights update was applied to a broader group of organizations than planned.   **What we did** An investigation was initiated immediately upon detection on May 21 at 9:07 AM to identify the root cause. Access rights were restored from a backup taken before the incident, fully reverting all affected users to their correct state.   **How we ensure this never happens again** An additional validation check has been added to the process, and maintenance procedures have been strengthened with documented, peer-reviewed action steps required before initiating production changes.

Dear Customer, We are investigating an issue that affected some ongoing integrations. We have identified cases where integrations using the POST action to create new users were affected. The root cause has already been fixed and the correction has been deployed to production. Our team is now identifying affected users with missing Employee IDs and is working to correct the impacted data. We will continue to monitor the situation closely and provide further updates as needed. Your Sympa Team

Dear Customer, The implemented fix is working as expected, and we have moved this incident to monitoring. Integrations using the POST action to create new users are now operating normally in production. Our team is continuing to review previously affected cases, including users with missing Employee IDs, and is working to correct any impacted data where needed. We will continue to monitor the situation closely and provide further updates if needed. Your Sympa Team

Dear Customer, This incident has now been resolved. The fix has been deployed to production, and integrations using the POST action to create new users are operating normally. Our team has reviewed the affected cases related to missing Employee IDs and completed the required corrective actions. We will continue to follow up internally to ensure everything remains stable. Your Sympa Team

**What happened** Between 28 April and 8 May 2026, employees created through our API integration could be left without an automatically generated identifier number. The employees themselves were created successfully, but the identifier field remained empty, which may have affected downstream integrations that rely on this data. **Why this happened** A defect in our integration API caused the automatic identifier assignment to be skipped in a specific configuration scenario. **What we did** The issue was detected on 8 May 2026, and a fix was deployed the same day. Identifier numbers are now always assigned correctly when employees are created through the API. **How we are preventing recurrence** Additional automated test coverage has been implemented for this scenario. The affected functionality is now validated through code-level tests during development, and end-to-end system tests are being expanded to verify the behavior before future releases are deployed.

At the moment, the issue appears to impact at least Data Cards, including for example adding new employees, as well as approval-related functionality. Our team is actively investigating the situation to confirm the full scope and root cause. We will share more information as soon as it becomes available. We apologize for the disruption and will provide an update as soon as possible. Your Sympa Team

Dear Customer, We have taken mitigation actions to reduce the impact of the ongoing issues, including increasing capacity in the affected parts of the Sympa service. Based on our current observations, this appears to be helping to improve the situation with Sympa. Our investigation is still ongoing, and we are continuing to assess the full scope of the issue and whether there are additional related impacts. We will share another update as soon as more information becomes available. We apologize for the continued disruption and appreciate your patience. Your Sympa Team

Dear Customer, Service performance has now been restored, and the incident is resolved. We are continuing our internal investigation to confirm the root cause of the issue. We will share further information once the investigation has been completed. We apologize for the disruption and thank you for your patience. Your Sympa Team

### **What happened?** Customers experienced a period of degraded performance. During this time, some actions, including saving employee data and processing approvals, were slow or intermittently unavailable. ### **Why it happened?** The incident was caused by an internal processing issue that affected the system’s ability to handle requests reliably during the affected period. As a result, some customer-facing actions were delayed or did not complete as expected. ### **What we are doing to prevent this in the future:** * **Improved Alerting:** We are improving automated monitoring and alerting so our on-call engineers are notified earlier when similar error patterns begin to appear. This will help us investigate and respond before customers are significantly impacted. * **Resilience Improvements:** We are improving how the affected areas of the platform handle increased load and temporary internal failures, reducing the likelihood of similar degradation in the future. * **Development follow-up:** High-priority work items have been created for our development teams to improve the affected services and strengthen recovery handling for similar situations.