Sympa HR Outage History

Started Sep 14, 2026, 06:25 AM UTC· resolved Sep 14, 2026, 11:45 AM UTC

1. identified Sep 14, 2026, 06:25 AM UTC

   Dear Customers, We have applied a fix for the eSign issue that began on Friday, September 11 at approximately 11:50 EETS. The main issue was addressed on Monday, September 14 at approximately 08:30 EETS. The issue affected the eSign process as follows: 1. Documents were successfully sent from Sympa to the eSign service. 2. Recipients were able to open and sign the documents in the eSign service. 3. After signing, information about the completed signing did not return to Sympa as expected. As a result, some signed documents remained incomplete in Sympa. Our team is monitoring the fix and handling the affected documents. If your documents were affected, please do not retry or resubmit them at this time. We are handling the affected documents for you, and no action is currently required from you. We will provide another update as soon as our monitoring and review of the affected documents have progressed. We apologize for the disruption and appreciate your patience. Your Sympa Team

2. resolved Sep 14, 2026, 11:45 AM UTC

   Dear Customers, The eSign disruption has been resolved, and the service has been restored to normal operation. New eSign documents are now being processed normally between Sympa and the eSign service. Our team is continuing to identify documents that were affected during the disruption between Friday, September 11 and Monday, September 14. We will correct the statuses of the affected documents as needed. If your document was affected during this period, no action is required from you at this time. Please do not retry or resubmit the document, as our team is handling the affected documents. We apologize for the disruption and appreciate your patience. Your Sympa Team

3. postmortem Sep 22, 2026, 05:49 AM UTC

   **What happened** Limited number of customers experienced a delay in the status updates of electronic signing \(e-signing\) documents. Specifically, between September 11 and September 14, document statuses from our e-signing vendors were not correctly reflected within Sympa. Limited number of customers and some documents were affected, primarily involving the e-sign vendor Scrive, with a few instances involving e-sign vendor Verified. **Why it happened** The issue was caused by a service interruption in our internal message processing system. A limit was reached, which prevented the system from receiving or processing new status updates from our e-signing partners. As a result, when vendors attempted to send document updates to Sympa, the information could not be recorded. Documents processing in e-signing partners system were not impacted and document statuses in Sympa side were fixed 21.9. **What we did** * **Immediate Fix:** We improved message processing system, which restored the system's ability to receive updates. * **Data Recovery:** We have identified all affected documents and have coordinated with our e-signing vendors to re-send the missing status updates to ensure all records are accurate. This fixes status of all documents which status was incorrect. This step was completed 21.9. * **Prevention:** We have found a root cause why the message volume increased and are implementing fixes and improving monitoring and automated alerts to prevent storage limits from being reached in the future. * **Communication:** We are directly contacted all the affected customers to provide specific updates regarding their documents. ‌ Your Sympa Team

Read the full incident report →

Started Aug 31, 2026, 07:09 AM UTC· resolved Aug 31, 2026, 09:36 AM UTC

1. investigating Aug 31, 2026, 07:09 AM UTC

   Dear Customers, We are currently investigating degraded performance affecting the login service. Customers can still log in, but the login process may take significantly longer than usual. Our team is actively investigating the cause and working to restore normal login performance. We apologize for the disruption and appreciate your patience. Your Sympa Team

2. monitoring Aug 31, 2026, 07:29 AM UTC

   Dear Customers, We have taken corrective action to address the degraded performance affecting the login service. According to our monitoring, the login service started operating normally at 10:25 EEST. Our team is continuing to monitor the service closely to confirm that performance remains stable. We apologize for the disruption and appreciate your patience. Your Sympa Team

3. resolved Aug 31, 2026, 09:36 AM UTC

   Dear Customers, The login service has continued to operate normally, and our monitoring confirms that performance remains stable. We are therefore closing this incident. We apologize for the disruption and appreciate your patience. Your Sympa Team

4. postmortem Sep 01, 2026, 09:07 AM UTC

   **What happened** Between the evening of 30 August and mid-morning on 31 August, some customers experienced slower than normal login times. Logins completed, but response times were degraded during this period. **Why it happened** An internal configuration item was not renewed on schedule, which caused a background processing job to fall behind. Clearing the resulting backlog created a short load spike that extended the degraded performance before service returned to normal. **What we have done** Restored normal processing and cleared the backlog. Automated the renewal of this class of configuration so it no longer depends on a manual step. Added earlier alerting so the condition is detected before it reaches customers. Added pacing to backlog processing so recovery cannot itself degrade performance. **Timeline \(EEST\)** 30 Aug, evening: first signs of degraded background processing 31 Aug, 09:03: corrective change applied 31 Aug, 09:40: background processing resumes 31 Aug, 10:30: login performance back to normal

Read the full incident report →

Started Jul 15, 2026, 06:22 AM UTC· resolved Jul 15, 2026, 01:52 PM UTC

1. investigating Jul 15, 2026, 06:22 AM UTC

   Dear Customers, We're experiencing an issue where the navigation structure does not show the page groups and pages as intended on employee profiles. We are currently investigating this and will provide an update by 10:30 EEST.

2. monitoring Jul 15, 2026, 06:49 AM UTC

   Dear Customers We've identified and resolved the issue causing the missing pages and groups. We will continue to monitor performance in order to minimise any setbacks. Thank you for your patience. Kind regards Sympa

3. resolved Jul 15, 2026, 01:52 PM UTC

   Dear Customers, The issue affecting page groups has been fully resolved, monitoring is completed, and we have taken steps to prevent it from recurring. No customer action is required. We apologize for the disruption caused by this incident and thank you for your patience and understanding. Your Sympa Team

4. postmortem Jul 16, 2026, 05:11 AM UTC

   **What happened** * Page groups were not displayed on employee profiles **Why it happened** * An internal system that manages feature access reached its capacity limit, preventing page groups from loading **What we did** * We moved the page group configuration to use a more efficient system path, restoring the feature * We're implementing longer-term improvements to prevent this type of failure from recurring * We added automated tests to ensure this feature continues to work

Read the full incident report →

Started Jun 17, 2026, 05:55 AM UTC· resolved Jun 22, 2026, 02:18 PM UTC

1. monitoring Jun 17, 2026, 05:55 AM UTC

   Dear Customers, We have identified an issue affecting approvals on table rows on yesterday 2026-06-16 15:34 EEST and was fixed today 2026-06-17 08:18 EEST. Customers may have had issues to create approvals for affected table rows. Our team applied a fix to restore approval creation for the affected rows. Everything works as expected now. Out team is looking to fix the affected data. We will provide the next update when the affected data is fixed or latest by 12.00 EEST. To summarize everything works now. We apologize for the disruption and appreciate your patience. Your Sympa Team

2. monitoring Jun 17, 2026, 08:58 AM UTC

   Dear Customers, The fix done early in the morning for the issue affecting approvals on table rows remains in place, and approval creation is working as expected. Our team is continuing work on data fixing, to restore any missing approval records and to identify table rows that may require approval review as a result of changes made during the affected period. Customers may still see some approval records that have not yet been fully restored while this work is ongoing. We are actively progressing with the corrective actions and will provide the next update by 14:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

3. monitoring Jun 17, 2026, 11:07 AM UTC

   Dear Customers, Approval creation for table rows continues to work as expected. Our team has prepared a corrective fix for the remaining affected data. Testing has started and is currently ongoing before the fix is applied. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 16:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

4. monitoring Jun 17, 2026, 01:11 PM UTC

   Dear Customers, Approval creation for table rows continues to work as expected. Our team has tested the corrective process in a non-production environment and is completing final adjustments before applying it to production. Once applied, the corrective process is expected to restore the missing approval records for the affected table rows. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 19:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

5. monitoring Jun 17, 2026, 04:12 PM UTC

   Dear Customers, Approval creation for table rows continues to work as expected. Our team has continued preparing the corrective process for the remaining affected approval data. Additional validation and adjustments are still required before the process can be safely applied to production. Customers may still see some approval records that have not yet been fully restored while this work continues. We will continue this work overnight and provide the next update by 09:00 EEST tomorrow, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

6. monitoring Jun 18, 2026, 05:56 AM UTC

   Dear Customers, New approval creation for table rows continues to work as expected. Our team has continued working on the corrective process for restoring the remaining affected approval data from the earlier incident. Testing of the corrective process has not yet completed successfully, and additional adjustments are required before it can be safely applied. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update by 12:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

7. monitoring Jun 18, 2026, 09:29 AM UTC

   Dear Customers, Approval creation for table rows continues to work as expected. Testing of the corrective fix has now been completed in a non-production environment. Our team is preparing to apply the fix to the affected production data after office hours today. Customers may still see some approval records that have not yet been fully restored while this work continues. We will provide the next update after the production corrective action has been completed, or by 19:00 EEST. We apologize for the disruption and appreciate your patience. Your Sympa Team

8. monitoring Jun 18, 2026, 03:12 PM UTC

   Dear Customers, We are pleased to share that we have successfully implemented a fix for the majority of the rows affected during the incident, and these have now been returned to a pending approval state. We are currently working on resolving the remaining few cases. In addition, we continue to investigate and address the rows that were edited during the incident. These rows are currently in an approved state. We will provide our next update after the Midsummer holiday. Thank you for your patience and understanding and apologise for the inconvenience. Your Sympa Team

9. monitoring Jun 22, 2026, 11:38 AM UTC

   Dear Customers, The issue affecting approvals when creating and editing table rows was resolved on 2026-06-17 at 08:18 EEST, as communicated previously. Approval creation for table rows is working as expected, and the corrective fix has been applied. The approval data for rows that were created during the incident have already been fixed 2026-06-18 by setting them to “pending approval” state. We are now completing the remaining data corrections for rows that were edited during the incident period. No customer action is currently required. We will contact affected customers directly if any follow-up actions are needed. We will provide the next update when the remaining corrections have been completed, or by 20:00 EEST. We apologize for the disruption and appreciate your patience. Your Sympa Team

10. resolved Jun 22, 2026, 02:18 PM UTC

    Dear Customers, The data correction work has now been completed, and the affected rows have been returned to the “pending approval” state. This statuspage topic can now be closed as fully resolved. No customer action is required. As communicated previously, the underlying issue was resolved on 2026-06-17 at 08:18 EEST, and approval creation for table rows has been working as expected since then. We apologize for the disruption caused by this incident and thank you for your patience and understanding while we completed the corrective work. Your Sympa Team

11. postmortem Jul 01, 2026, 12:59 PM UTC

    **What happened** Between **16 June 2026 at 14:00 EEST** and **17 June 2026 at 08:30 EEST**, an issue affected approval workflows in table-based forms. During this period: * New rows created in tables with approval fields were saved successfully, but the approval controls were not displayed, preventing users from approving or declining the rows. * Editing existing rows did not correctly reset approval status when required. Previously approved or declined rows retained their existing status instead of returning to a pending state. * Users were unable to complete approval actions for affected rows. After the issue was resolved, we repaired all affected records. Rows created during the incident were restored on **18 June**, and rows updated during the incident were restored on **22 June**. **Why it happened** The incident was caused by an operational error during preparation for a planned release, resulting in an unintended change that affected approval workflows. **What we did** Once the issue was identified, we immediately assembled an incident response team to investigate and resolve the issue. We removed the unintended change, developed dedicated repair tools to restore the affected approval records, and successfully completed repairs for all known impacted data. To help prevent similar incidents, we are strengthening our release processes and enhancing our monitoring and alerting capabilities to detect and respond to similar issues more quickly.

Read the full incident report →

Started Jun 16, 2026, 08:17 AM UTC· resolved Jun 17, 2026, 06:17 AM UTC

1. investigating Jun 16, 2026, 08:17 AM UTC

   Dear Customer, We are currently investigating an issue affecting integrations. Customers may experience failed or delayed integration processing. Our team is actively investigating the root cause and working to restore normal integration processing. We will provide the next update by 13:00 EEST, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience. Your Sympa Team

2. identified Jun 16, 2026, 10:01 AM UTC

   Dear Customer, We have identified the cause of the issue affecting integrations. Customers may still experience delayed integration processing. Our team is continuing mitigation work and manually reprocessing affected files where possible while we work to restore normal processing. We will provide the next update by 15:00 EEST, or sooner if there is significant progress. Your Sympa Team

3. identified Jun 16, 2026, 12:14 PM UTC

   Dear Customer, We are continuing work to restore normal integration processing. Customers may still experience delayed integration processing. Our team is preparing a fix and testing it before applying it. We are also continuing mitigation work and manually reprocessing affected files where possible. We will provide the next update by 16:30 EEST, or sooner if there is significant progress. Your Sympa Team

4. monitoring Jun 16, 2026, 01:36 PM UTC

   Dear Customer, We have applied fixes for the issue affecting integrations and are monitoring their effect. Integration processing has improved, but some data from last night still requires manual handling. Our team is continuing this work and will monitor the results of the fixes throughout the night. We will keep this incident open and provide the next update by 19:00 EEST, or sooner if there is significant progress. Your Sympa Team

5. monitoring Jun 16, 2026, 04:00 PM UTC

   Dear Customer, We have applied mitigation actions for the issue affecting integrations and are continuing to monitor integration processing. Our team is monitoring the evening and overnight processing runs to confirm stability. We are also continuing manual handling of any remaining affected data where needed. We will keep this incident open while monitoring continues and will provide the next update by 09:00 EEST tomorrow, or sooner if there is significant progress. Your Sympa Team

6. resolved Jun 17, 2026, 06:17 AM UTC

   The mitigation actions taken yesterday has fixed the issue. The performance has also improved significantly. We did not detected such issues in integrations during yesterday evening, during the night nor during the morning. We confirm everything is operational and close this ticket. Post-mortem will be released later on.

7. postmortem Jul 01, 2026, 02:12 PM UTC

   ## Post mortem for customers ### What happened Some integrations were delayed or failed during the nightly processing window because Azure Blob Storage operations were slower than usual. The integrations performed more Azure Blob listing/checking operations than expected. The number of `ListBlobs` calls was around double compared to normal days. This affected to one integration application. ### Why it happened Most probably, Azure Blob Soft Delete or increased blob volume caused slower listing operations during the night. This affected integrations that rely on file lookup logic to Azure Blob. ### What we did We optimized Azure Blob existence checks and flows in the integration application that got affected. As a result, the number of `ListBlobs` calls decreased by around 20%, and the next nightly integration runs completed normally, with better performance. The same fix was also applied to other integration applications.

Read the full incident report →

Started Jun 15, 2026, 08:14 AM UTC· resolved Jun 15, 2026, 12:44 PM UTC

1. investigating Jun 15, 2026, 08:14 AM UTC

   We are currently investigating an issue impacting integrations and reporting. Our team is actively working to identify the root cause and restore normal service. We will provide further updates as more information becomes available. We apologize for any inconvenience and appreciate your patience.

2. identified Jun 15, 2026, 08:48 AM UTC

   We have identified the cause of the issue impacting integrations and reporting functionality. Mitigation steps are currently in progress, and our team is continuing to work on a permanent fix. We will provide further updates as soon as more information is available.

3. identified Jun 15, 2026, 09:35 AM UTC

   Immediate mitigation actions have been implemented, and the acute situation has been remedied. We are currently working on a permanent fix to address the root cause and prevent recurrence.

4. monitoring Jun 15, 2026, 09:44 AM UTC

   Dear Customer, Immediate mitigation actions have been implemented, and the acute impact to integrations and reporting has been mitigated. We are continuing to work on a permanent fix to address the root cause and prevent recurrence. Our team will continue monitoring the situation and provide the next update by 15:00 EEST at the latest. Your Sympa Team

5. resolved Jun 15, 2026, 12:44 PM UTC

   The service disruption has been solved. We have identified the root cause of the issue and narrowed down the affected customers. We are contacting them directly to provide any necessary follow-up information.

6. postmortem Jul 02, 2026, 01:42 PM UTC

   **What happened** * Approval information was missing from some customer report data * Small number of customers were affected **Why it happened** * An issue during a data migration process caused approval information to be lost from some records * Records were generated and transferred without the expected approval status attached **What we did** * We corrected the affected data in our systems * We regenerated reports for impacted customers to restore the correct approval information * We are improving our migration process

Read the full incident report →

Started Jun 12, 2026, 09:08 AM UTC· resolved Jun 12, 2026, 01:23 PM UTC

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.

Read the full incident report →

Started May 21, 2026, 06:22 AM UTC· resolved May 21, 2026, 10:57 AM UTC

1. investigating May 21, 2026, 06:22 AM UTC

   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

2. identified May 21, 2026, 06:22 AM UTC

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

3. identified May 21, 2026, 07:50 AM UTC

   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

4. identified May 21, 2026, 08:54 AM UTC

   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

5. identified May 21, 2026, 10:10 AM UTC

   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

6. resolved May 21, 2026, 10:57 AM UTC

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

7. postmortem May 25, 2026, 12:19 PM UTC

   **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.

Read the full incident report →

Started May 08, 2026, 12:55 PM UTC· resolved May 08, 2026, 07:11 PM UTC

1. identified May 08, 2026, 12:55 PM UTC

   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

2. monitoring May 08, 2026, 03:16 PM UTC

   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

3. resolved May 08, 2026, 07:11 PM UTC

   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

4. postmortem Jun 05, 2026, 03:06 PM UTC

   **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.

Read the full incident report →

Started Apr 29, 2026, 09:41 AM UTC· resolved Apr 29, 2026, 03:21 PM UTC

1. investigating Apr 29, 2026, 09:41 AM UTC

   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

2. investigating Apr 29, 2026, 12:57 PM UTC

   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

3. resolved Apr 29, 2026, 03:21 PM UTC

   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

4. postmortem Jun 02, 2026, 08:02 PM UTC

   ### **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.

Read the full incident report →

Started Apr 24, 2026, 08:26 AM UTC· resolved Apr 24, 2026, 12:19 PM UTC

1. identified Apr 24, 2026, 08:26 AM UTC

   We have identified an issue in Sympa that may have impacted some customers. Users may experience errors when attempting to save certain data. We are working to resolve the problem and will provide an update when it is confirmed to be fully resolved.

2. monitoring Apr 24, 2026, 08:55 AM UTC

   We have identified the root cause of the issue and are currently applying a fix. The update is being rolled out, and we expect the issue to be resolved shortly. Our team is closely monitoring the situation to ensure everything returns to normal for affected customers. Your Sympa Team

3. resolved Apr 24, 2026, 12:19 PM UTC

   The issue has now been resolved, and our services are operating normally. We have completed monitoring and can confirm that the fix is working as expected. Thank you for your patience. Your Sympa Team

4. postmortem May 04, 2026, 07:50 PM UTC

   **Customer impact** Some customers experienced errors when attempting to save data in Sympa. This resulted in failed updates with the 5003 error given on the screen while attempting to save the data in the form. **Timeline \(UTC\)** * **April 23, 18:00 UTC** — A configuration change was deployed to production as part of a planned feature rollout. * **April 24, 06:30 UTC** — The issue was detected after customer reports of save errors \(error code 5003\). * **April 24, 08:48 UTC** — The issue was fully mitigated by reverting the configuration change. Total time from detection to resolution: **2 hours 18 minutes**. **What happened** The issue was caused by a recently enabled feature related to how certain changes are processed in the system. This change unintentionally affected normal save operations for some users. **Resolution** We identified the problematic feature configuration, verified the fix in our test environment, and then disabled it in production, which resolved the problem. Normal functionality has been fully restored. **Next steps** * Root cause analysis is underway to determine why this configuration caused permission-related errors. * We will strengthen our pre-deployment validation to catch similar issues before they reach production.

Read the full incident report →

Started Apr 15, 2026, 01:44 PM UTC· resolved Apr 15, 2026, 04:59 PM UTC

1. monitoring Apr 15, 2026, 01:44 PM UTC

   This means that when new information is added, for example a new employee, it may not appear in the system immediately. Some updates may show within seconds or minutes, while others can take longer. We have increased system capacity and are closely monitoring the situation to reduce the delays. We’re sorry for the inconvenience and will keep you updated. Your Sympa Team

2. monitoring Apr 15, 2026, 02:51 PM UTC

   The delays in updating data in Sympa have now returned to normal levels. New information, such as added employees, should now appear in the system as expected, including in reporting. We will continue to monitor the situation closely to ensure everything remains stable before closing this incident. Thank you for your patience, and we’re sorry for the inconvenience. Your Sympa Team

3. resolved Apr 15, 2026, 04:59 PM UTC

   The issue causing delays in updating data in Sympa has been resolved. Data is now updating normally, and new information, such as added employees, is visible in the system as expected, including in reporting. We have monitored the situation and confirmed that everything is stable. Thank you for your patience, and we’re sorry for the inconvenience. Your Sympa Team

4. postmortem Apr 20, 2026, 06:09 AM UTC

   **What happened** * We experienced delays in updating data in Sympa. This meant that when new information was added—such as a new employee—it did not always appear in the system immediately. Some updates were processed within seconds or minutes, while others took longer than expected. Additionally, some customers may have experienced slowness when using reporting features. **Why it happened** * The delays were caused by an unusually high load in the system. This increased volume of updates created a backlog, meaning that new information had to wait longer than usual before being processed and displayed. **What we did** * Increased system capacity to handle the higher load * Scaled up our reporting infrastructure to improve performance * Monitored the system closely to reduce the backlog of updates * Continued to track performance to ensure the situation stabilized

Read the full incident report →

Started Apr 10, 2026, 07:12 AM UTC· resolved Apr 10, 2026, 06:21 PM UTC

1. investigating Apr 10, 2026, 07:12 AM UTC

   Dear Customer, We have identified an issue affecting calculations performed during the night of 09/04/2026 - 10/04/2026. Due to a recent update, certain calculated fields may be incorrect. We are currently assessing the scope of the impact. The system is otherwise operating normally, and no data is lost. Our engineering team is actively investigating the issue and working on a fix. If you notice any discrepancies in your data, please contact our Support team and create a new ticket in the Help Centre. We will assist by re-calculating the affected card bases for your environment. We will provide updates as the investigation progresses. Your Sympa Team

2. identified Apr 10, 2026, 08:57 AM UTC

   Dear Customer, We have identified the main cause of the issue affecting calculation accuracy. The issue is related to certain calculation scenarios, for example: - when calculations combine text and numeric values (for example, building a value that includes both text and numbers) - when conditions check whether a boolean (checkbox) field is empty or not - when conditions check whether an approval-field is 0 or other not supported value As a result, these calculated fields has resulted into empty values. The system has been otherwise operating normally, and no data is lost. Our engineering team is continuing work on a fix for these scenarios. If you notice any discrepancies in your data, please contact our Support team and create a new ticket in the Help Centre. We will assist by re-calculating the affected card bases for your environment. We recommend reviewing recent calculation results before using them for critical processes. We will provide further updates as the fix progresses. Your Sympa Team

3. monitoring Apr 10, 2026, 12:29 PM UTC

   Dear Customer, A fix was implemented by rolling back the recent changes that caused the calculation issue. We have fixed all the cases that have been reported to us so far. We are currently monitoring the situation to ensure everything is working as expected. Any calculation issues that have not yet been noticed will be automatically corrected by next midnight on Saturday at 00:00 UTC. We will continue to monitor closely and provide further updates if needed. Your Sympa Team

4. resolved Apr 10, 2026, 06:21 PM UTC

   Dear Customer, The issue affecting calculation accuracy has now been resolved. We have monitored the situation and confirmed that the fix is stable. If you still notice any discrepancies in your data, please contact our Support team, and we will be happy to assist. Thank you for your patience. Your Sympa Team

5. postmortem Apr 20, 2026, 09:34 AM UTC

   **What happened** During the night of April 9–10, 2026, the calculation engine ran with an updated version that included stricter formula validation. This stricter validation caused formulas that previously produced results to now yield empty values in the report database. Specifically, three categories of formulas were affected: * Formulas that used the `+` operator for string concatenation — all `+` operations were treated as arithmetic * Formulas that compared fields against values of incompatible types \(e.g. boolean compared to null, approval compared to a number\) — previously the engine silently ignored these, now it rejected them * Formulas that contained inline comments using the `#` character **Why it happened** We upgraded the calculation engine to improve diagnostics and enable deeper investigation of calculation issues. The new engine included stricter type validation rules. While the intent was to improve robustness, the stricter rules rejected formulas that the previous engine had accepted. These edge cases were not sufficiently covered by the existing regression tests and were not caught before deployment. **What we did** * **Apr 10, 11:57 EEST** — Root cause identified: three categories of formulas were failing under the new stricter validation * **Apr 10, 15:29 EEST** — Fix deployed by rolling back the calculation services to the previous version; all reported cases corrected * **Apr 10, 21:21 EEST** — Fix confirmed stable after monitoring; incident resolved ‌ **The fixes for the identified edge cases and dedicated regression tests are planned as follow-up work.**

Read the full incident report →

Started Apr 01, 2026, 07:57 AM UTC· resolved Apr 01, 2026, 10:00 AM UTC

1. identified Apr 01, 2026, 07:57 AM UTC

   We are currently experiencing delays in data appearing in reporting after updates are made in Sympa (for example, when adding new employees or modifying existing data). At the moment, updates may take several minutes, and in some cases up to approximately one hour, to be reflected in reports. The system is otherwise operating normally, and no data is being lost. Our team has identified the root cause and is currently deploying a fix to restore normal performance. We will provide updates as the deployment progresses. Your Sympa Team

2. monitoring Apr 01, 2026, 08:37 AM UTC

   Dear Customer, A fix has now been deployed to address the delays in reporting data updates. We are currently monitoring the situation as performance stabilizes. While improvements should already be visible, it may take several hours for the system to return fully to normal. During this time, you may still experience delays in data appearing in reports after updates are made. We will continue to monitor closely and provide further updates. Your Sympa Team

3. resolved Apr 01, 2026, 10:00 AM UTC

   The delays affecting reporting data updates have now been fully resolved. System performance has returned to normal, and new or updated data is appearing in reports as expected. We will continue to monitor to ensure stability, but no further impact is expected. Thank you for your patience. Your Sympa Team

4. postmortem Apr 13, 2026, 12:22 PM UTC

   **What happened** On April 1, 2026, starting at 09:07, customers experienced delays in seeing their data after saving. **Why it happened** The issue was caused by a limitation in the system responsible for handling background processing. It reached its capacity and could not process new and ongoing operations efficiently. In addition, the system did not release memory quickly enough during high usage, which caused delays before saved data was applied. **What we did** We took the following actions to resolve the issue: * Improved how the system releases resources, making it more responsive during high usage * Optimized memory usage to improve overall stability These changes were fully implemented by 10:43, and the disruption was fully resolved by 12:34.

Read the full incident report →

Started Mar 23, 2026, 02:39 PM UTC· resolved Mar 24, 2026, 02:19 PM UTC

1. investigating Mar 23, 2026, 02:39 PM UTC

   Dear Customer, We are currently experiencing issues with the eSign (Scrive) service. Our technical team is actively investigating the problem and working on a resolution. We will provide updates as soon as more information becomes available. Thank you for your patience. Your Sympa Team

2. identified Mar 23, 2026, 03:46 PM UTC

   The issue affecting the eSign (Scrive) service has been identified. Our partner is actively working on resolving it, and the service is expected to be restored within 10–15 minutes. We will continue to monitor the situation and provide updates as needed. Your Sympa Team

3. monitoring Mar 23, 2026, 04:11 PM UTC

   Our partner has deployed a fix, and the eSign (Scrive) service is now operating normally. We will continue to monitor the situation. Your Sympa Team

4. monitoring Mar 23, 2026, 09:02 PM UTC

   The major issues affecting the eSign (Scrive) service have now been resolved, and the service is largely operating normally. However, we are still observing occasional errors in rare cases. Our partner is continuing to work towards a full resolution. We will keep monitoring the situation closely and provide the next update by 12:00 EET tomorrow. Your Sympa Team

5. resolved Mar 24, 2026, 02:19 PM UTC

   Dear Customer, The issue affecting the eSign (Scrive) service has now been resolved, and the service is operating normally. The root cause was identified and corrected by our partner. We apologize for the delay in communication and any inconvenience caused. Your Sympa Team

6. postmortem Apr 20, 2026, 06:12 AM UTC

   **What happened:** * Customers experienced issues with the eSign \(Scrive\) service, preventing some signing requests from being processed successfully * The incident was time-limited but resulted in a number of affected documents requiring manual review **Why it happened:** * The root cause was identified as a configuration error on our partner’s \(Scrive\) side * The issue was resolved once identified, restoring normal service **What we did:** * Worked closely with our partner to identify and resolve the issue as quickly as possible * Monitored the service to ensure stability after the fix was deployed * Identified affected documents and provided customers with a tool to efficiently review and reprocess them where needed

Read the full incident report →

Started Mar 23, 2026, 09:17 AM UTC· resolved Mar 23, 2026, 08:48 PM UTC

1. investigating Mar 23, 2026, 09:17 AM UTC

   Dear Customer, We are currently investigating an increased number of "Something unexpected happened" error messages affecting several customers. Our team is actively working to identify the root cause and mitigate the issue as quickly as possible. At the moment, no action is required from your side. We will keep you updated as soon as we have more information. Best regards, The Sympa Team

2. monitoring Mar 23, 2026, 09:25 AM UTC

   We are seeing system performance return to normal levels, and the error messages are no longer occurring. We will continue to monitor the situation closely to ensure stability. Your Sympa Team

3. monitoring Mar 23, 2026, 12:39 PM UTC

   As a follow-up to this incident, we will perform a planned update later this evening to further improve system stability and reduce the risk of similar errors. No disruption to customers is expected, and we will continue to monitor the system closely. Your Sympa Team

4. resolved Mar 23, 2026, 08:48 PM UTC

   The issue has been resolved and system performance is stable. Additional improvements have been implemented to help prevent similar issues going forward. Thank you for your patience. Your Sympa Team

5. postmortem Apr 13, 2026, 12:29 PM UTC

   **What happened** On March 23rd, some customers experienced an increased number of error messages \("Something unexpected happened"\) and slower system performance. **Why it happened** The issue was caused by an unusually high number of internal requests being processed at the same time. This led to temporary congestion in one of our backend services, which impacted system stability. **What we did** We resolved the situation by increasing system capacity, which restored normal performance. We are now working on improvements to prevent similar situations in the future. These include better handling of unnecessary requests, improved monitoring, and optimizations to reduce system load during peak times. We apologize for any inconvenience caused and appreciate your patience.

Read the full incident report →

Started Mar 09, 2026, 09:55 AM UTC· resolved Mar 10, 2026, 08:37 PM UTC

1. identified Mar 09, 2026, 09:55 AM UTC

   Dear Customer, We have identified an issue where the table row copying feature is not working as expected. Users may be unable to copy rows in certain tables. Our team is investigating the issue and working to resolve it as quickly as possible. We will provide updates through this Statuspage incident. Your Sympa Team

2. identified Mar 09, 2026, 01:14 PM UTC

   Dear Customer, We have identified the root cause of the issue affecting the table row copying feature and prepared a fix. The fix is currently undergoing testing to ensure it resolves the issue without causing any unintended side effects. We are planning to deploy it during tomorrow’s late-night release window. We will provide a further update once the deployment has been completed. Your Sympa Team

3. monitoring Mar 10, 2026, 07:30 PM UTC

   Dear Customer, The fix has now been deployed to production. The table row copying feature should be functioning normally again. We are currently monitoring the system to ensure the issue is fully resolved. We will provide a final update once the situation has been confirmed as stable. Your Sympa Team

4. resolved Mar 10, 2026, 08:37 PM UTC

   Dear Customer, The issue affecting the table row copying feature has been resolved. The feature is now functioning normally. Thank you for your patience. Your Sympa Team

5. postmortem Mar 13, 2026, 01:15 PM UTC

   **What happened** * Table rows -copy option has disappeared, preventing the copying of tablerow -data to new row. **Why it happened** * This issue was inadvertently introduced to production with the update deployed last week \(week 10 2026\). **What we did** * We have fixed the issue, and added additional tests to prevent this situation from occurring again.

Read the full incident report →

Started Mar 09, 2026, 09:29 AM UTC· resolved Mar 09, 2026, 09:03 PM UTC

1. investigating Mar 09, 2026, 09:29 AM UTC

   Dear Customer, We are currently investigating an issue where some pages in Sympa show the message “Content not loaded”, even though user roles and permissions are correctly configured. This may prevent users from seeing data on certain pages. We are working to resolve the issue as quickly as possible and will provide an update as soon as we have more information. Your Sympa Team

2. identified Mar 09, 2026, 01:36 PM UTC

   Dear Customer, The situation has improved, and the number of “Content not loaded” errors has decreased significantly. However, the issue has not yet been fully resolved. We will deploy an additional fix during tonight’s production release, which is expected to address this issue. We will monitor the system closely after the deployment and provide an update once the situation has been confirmed as resolved. Your Sympa Team

3. identified Mar 09, 2026, 02:38 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Mar 09, 2026, 09:03 PM UTC

   Dear Customer, The fix has been deployed to production, and our verification confirms that the “Content not loaded” issue has been resolved. We have validated the solution across affected cases and are continuing to monitor the system to ensure stable performance. Thank you for your patience and understanding. Your Sympa Team

5. postmortem Mar 13, 2026, 12:40 PM UTC

   #### What happened Some users occasionally experienced slower than usual loading times and "content not found" errors when accessing profile pages. #### Why it happened We have identified a suspected issue with an underlying caching component that may be causing delays and occasional failures when loading profile page content. Investigation is ongoing. #### What we did * Identified a potential root cause in the caching layer * Working on migrating to an improved caching solution to address the issue * Continuing to monitor to ensure the issue is fully resolved

Read the full incident report →

Started Feb 04, 2026, 02:05 PM UTC· resolved Feb 04, 2026, 02:10 PM UTC

1. identified Feb 04, 2026, 02:05 PM UTC

   We have identified an issue that may have impacted Sympa. We are working to resolve the problem and will provide an update when it is confirmed to be fully resolved.

2. identified Feb 04, 2026, 02:05 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Feb 04, 2026, 02:10 PM UTC

   The issue that may have impacted Sympa has now been resolved. All services should be fully accessible. If you continue to experience any problems, please contact our support service. Thank you for your patience.

4. postmortem Apr 13, 2026, 12:20 PM UTC

   **What happened** * CDN problems caused customers not being able to login. **Why it happened** * Azure related issue, detected. **What we did** * A fix planned that will solve these issues in the future. This cdn issue is already known in our frontend team.

Read the full incident report →

Started Jan 27, 2026, 07:37 AM UTC· resolved Jan 27, 2026, 08:53 AM UTC

1. investigating Jan 27, 2026, 07:37 AM UTC

   We have noticed degraded performance in Sympa. We are currently investigating the root cause.

2. resolved Jan 27, 2026, 08:53 AM UTC

   The overall performance of Sympa is back to normal. Although this incident is now closed, we will continue monitoring the service closely. Your Sympa Team

3. postmortem Apr 13, 2026, 12:18 PM UTC

   **What happened** * On 27 January, Sympa experienced degraded performance, which caused slower response times and occasional errors for some users. **Why it happened** * A recently updated service caused slowness due to it’s cache. This service was reverted and system returned to normal. **What we did** * Our teams investigated the issue immediately and monitored the system closely. The service stabilized and returned to normal operation. We continue to monitor the system and take steps to prevent similar situations in the future.

Read the full incident report →

Started Jan 20, 2026, 07:07 AM UTC· resolved Jan 20, 2026, 07:56 AM UTC

1. investigating Jan 20, 2026, 07:07 AM UTC

   We’re investigating reports of login issues affecting some users. We’ll share an update as soon as possible.

2. identified Jan 20, 2026, 07:27 AM UTC

   The issue has been identified and our team is working on a fix. Login status by Sympa version: Sympa Classic: OK ✅ Sympa 23: OK ✅ Sympa 25: Login issues ⚠️ Next update as soon as possible. Your Sympa Team

3. monitoring Jan 20, 2026, 07:39 AM UTC

   We’ve improved availability for the Sympa 25 login service and the issue should be resolved. We’re monitoring to confirm all users can log in normally. Your Sympa Team

4. resolved Jan 20, 2026, 07:56 AM UTC

   According to our monitoring, the Sympa 25 login service is operating normally and this incident is resolved. Your Sympa Team

Read the full incident report →

Started Dec 05, 2025, 08:55 AM UTC· resolved Dec 05, 2025, 09:40 AM UTC

1. identified Dec 05, 2025, 08:55 AM UTC

   Dear customer, We are currently experiencing a major outage with Cloudflare that is also affecting our support systems, including the knowledge base and ticketing. Our team is monitoring the situation closely. We will notify you as soon as the issue has been resolved. Error message: "500 Internal Server Error Cloudflare" Thank you for your patience, Your Sympa Team

2. monitoring Dec 05, 2025, 09:17 AM UTC

   Quick update; Cloudflare is already working with the issue according to their statuspage: https://www.cloudflarestatus.com/ --------- Cloudflare System Status Cloudflare Dashboard and Cloudflare API service issues Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed. Dec 05, 2025 - 08:56 UTC --------- Your Sympa Team

3. resolved Dec 05, 2025, 09:40 AM UTC

   Dear Customer, Our services are now fully operational again, so we are closing this incident on our side. Thank you for your patience. Your Sympa Team

Read the full incident report →

Started Nov 19, 2025, 06:43 AM UTC· resolved Nov 21, 2025, 01:15 PM UTC

1. investigating Nov 19, 2025, 06:43 AM UTC

   We are currently investigating an issue where automatic table reminders are not being sent. The issue started on 13 November. The issue doesn't concern approval messages, birthday or well-being notifications or the messages of users requesting for new passwords. We will do our best to send all of the table reminders again, that have been unsent during this time, as soon as the issue is resolved. We apologize for the inconvenience. More information will follow. Your Sympa Team

2. investigating Nov 19, 2025, 11:29 AM UTC

   We are still investigating this issue. Impact is limited to automatic table reminder emails only. Approval messages, birthday and well-being notifications, and password reset emails are NOT affected. We will post another update as we proceed with investigations. Your Sympa Team

3. identified Nov 19, 2025, 05:52 PM UTC

   We are testing a fix, and testing will continue overnight. Impact remains limited to automatic table reminder emails. Approval messages, birthday and well-being notifications, and password reset emails are not affected. Next update by 12:00 EET on Thu 20 Nov 2025.

4. monitoring Nov 20, 2025, 10:35 AM UTC

   We have deployed a fix and are monitoring. Table reminder emails are expected to resume overnight as scheduled. We are evaluating options to resend reminders missed during the incident. Your Sympa Team

5. resolved Nov 21, 2025, 01:15 PM UTC

   The incident is resolved and the service is operating normally in production. We will ensure that all approval notifications missed during the incident are reprocessed, and users will start seeing them as they are handled. Thank you for your patience and understanding. Your Sympa Team

6. postmortem Nov 25, 2025, 11:38 AM UTC

   **Post Mortem: Automatic Table Reminder Emails Not Sent** Incident timeframe: 13–21 November 2025 Resolved: 21 Nov 2025 at 15:15 EET Impact: Automatic table reminder emails were not sent as expected **Summary** Between 13 and 21 November, automatic table reminder emails were not delivered as scheduled in the production environment. Other notification types — such as approval messages, password reset emails, and well-being or birthday notifications — were not affected. The issue was resolved on 21 November, after which normal delivery resumed. All table reminder emails that had been delayed during the incident were successfully reprocessed and delivered during Thursday and Friday \(21–22 Nov\). **Technical Overview** The issue was resolved through a targeted update to our background processing component responsible for handling scheduled messages. We became aware that the internal process responsible for reminder delivery was not executing as intended due to an unintended configuration state. A controlled update has since restored expected behavior, and the system is fully operational. **Recovery Actions** All missed reminder emails were re-sent during 21–22 November. Scheduled reminder email delivery resumed automatically and has remained stable since. Additional monitoring has been implemented to detect irregularities in reminder processing earlier. **Preventive Improvements** To reduce the risk of similar issues in the future, we have: Enhanced monitoring around the scheduled messaging pipeline, allowing us to react more quickly to any abnormalities. Started reviewing the scalability and timeout behavior of reminder queries to ensure they remain reliable even under increased data loads. Initiated fine-tuning of the reminder delivery mechanism, to prevent potential bottlenecks related to query size or performance over time. **Final Notes** We sincerely thank you for your patience during the incident. We're committed to continuous improvement of our notification infrastructure to ensure dependable delivery of all critical messages. — Your Sympa Team

Read the full incident report →

Started Nov 13, 2025, 04:32 PM UTC· resolved Nov 13, 2025, 05:02 PM UTC

1. identified Nov 13, 2025, 04:32 PM UTC

   We have identified a login issue in the system and we are working on fixing the issue.

2. identified Nov 13, 2025, 04:42 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Nov 13, 2025, 05:01 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Nov 13, 2025, 05:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 06, 2025, 08:51 AM UTC· resolved Nov 06, 2025, 06:11 PM UTC

1. identified Nov 06, 2025, 08:51 AM UTC

   We’ve identified an issue with a recent change to our access control logic. Some users can log in successfully but are unable to view data or resources they normally have access to. Our team is actively implementing a fix to restore full visibility and access as soon as possible. Your Sympa Team

2. identified Nov 06, 2025, 12:57 PM UTC

   We’re continuing work on the fix for the access control issue. Final testing is underway before deployment, which may take a few more hours. The fix requires careful validation to ensure a safe and complete resolution. Thank you for your patience and understanding while we complete this work.

3. monitoring Nov 06, 2025, 04:38 PM UTC

   The fix has been deployed to production, and visibility within the system has been restored. We’re monitoring closely to ensure everything is working as expected. Your Sympa Team

4. resolved Nov 06, 2025, 06:11 PM UTC

   The issue has been fully resolved. System visibility and access are now working as expected. Thank you for your patience while we implemented the fix. Your Sympa Team

Read the full incident report →