Sympa HR Outage History

Sympa HR is up right now

Sympa HR had 39 outages in the last 2 years totaling 234h 32m of downtime — averaging 1.6 incidents per month.

There were 39 Sympa HR outages since November 1, 2024 totaling 234h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://sympa.statuspage.io

Major June 16, 2026

Integration processing disruption

Detected by Pingoru
Jun 16, 2026, 08:17 AM UTC
Resolved
Jun 17, 2026, 06:17 AM UTC
Duration
22h
Affected: Integrations
Timeline · 6 updates
  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.

Read the full incident report →

Minor June 15, 2026

Issues with integrations and reporting

Detected by Pingoru
Jun 15, 2026, 08:14 AM UTC
Resolved
Jun 15, 2026, 12:44 PM UTC
Duration
4h 29m
Affected: ReportingIntegrations
Timeline · 5 updates
  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.

Read the full incident report →

Major June 12, 2026

Issues with SFTP file transfers

Detected by Pingoru
Jun 12, 2026, 09:08 AM UTC
Resolved
Jun 12, 2026, 01:23 PM UTC
Duration
4h 15m
Affected: Integrations
Timeline · 3 updates
  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

Read the full incident report →

Minor May 8, 2026

Integration issues with Employee ID

Detected by Pingoru
May 08, 2026, 12:55 PM UTC
Resolved
May 08, 2026, 07:11 PM UTC
Duration
6h 15m
Affected: Integrations
Timeline · 4 updates
  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 →

Minor April 15, 2026

We are currently experiencing a delay in updating data in Sympa

Detected by Pingoru
Apr 15, 2026, 01:44 PM UTC
Resolved
Apr 15, 2026, 04:59 PM UTC
Duration
3h 14m
Affected: Reporting
Timeline · 4 updates
  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 →

Minor April 1, 2026

Performance Degradation - Delays in Reporting Data Updates

Detected by Pingoru
Apr 01, 2026, 07:57 AM UTC
Resolved
Apr 01, 2026, 10:00 AM UTC
Duration
2h 2m
Affected: ReportingIntegrations
Timeline · 4 updates
  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 →

Minor March 23, 2026

Issues with the eSign (Scrive) service

Detected by Pingoru
Mar 23, 2026, 02:39 PM UTC
Resolved
Mar 24, 2026, 02:19 PM UTC
Duration
23h 40m
Affected: Esign
Timeline · 6 updates
  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 →

Minor March 23, 2026

Increased number of "Something unexpected happened" errors for some customers

Detected by Pingoru
Mar 23, 2026, 09:17 AM UTC
Resolved
Mar 23, 2026, 08:48 PM UTC
Duration
11h 30m
Affected: System availability
Timeline · 5 updates
  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 →

Major March 9, 2026

Issue with copying table rows

Detected by Pingoru
Mar 09, 2026, 09:55 AM UTC
Resolved
Mar 10, 2026, 08:37 PM UTC
Duration
1d 10h
Affected: System availability
Timeline · 5 updates
  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 →

Minor March 9, 2026

“Content not loaded” error on some pages

Detected by Pingoru
Mar 09, 2026, 09:29 AM UTC
Resolved
Mar 09, 2026, 09:03 PM UTC
Duration
11h 33m
Affected: System availability
Timeline · 5 updates
  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 →

Critical February 4, 2026

Major outage

Detected by Pingoru
Feb 04, 2026, 02:05 PM UTC
Resolved
Feb 04, 2026, 02:10 PM UTC
Duration
4m
Affected: System availability
Timeline · 4 updates
  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 →

Minor January 27, 2026

Degraded performance

Detected by Pingoru
Jan 27, 2026, 07:37 AM UTC
Resolved
Jan 27, 2026, 08:53 AM UTC
Duration
1h 16m
Affected: System availability
Timeline · 3 updates
  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 →

Major January 20, 2026

Login issue to Sympa

Detected by Pingoru
Jan 20, 2026, 07:07 AM UTC
Resolved
Jan 20, 2026, 07:56 AM UTC
Duration
48m
Affected: System availability
Timeline · 4 updates
  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 →

Critical December 5, 2025

Our support portal is not working due to Cloudflare issues

Detected by Pingoru
Dec 05, 2025, 08:55 AM UTC
Resolved
Dec 05, 2025, 09:40 AM UTC
Duration
44m
Affected: TicketingKnowledgebase
Timeline · 3 updates
  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 →

Major November 13, 2025

Login issue

Detected by Pingoru
Nov 13, 2025, 04:32 PM UTC
Resolved
Nov 13, 2025, 05:02 PM UTC
Duration
29m
Affected: System availabilityAuthentication
Timeline · 4 updates
  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 →

Minor November 6, 2025

Access control issue causing limited visibility in the system

Detected by Pingoru
Nov 06, 2025, 08:51 AM UTC
Resolved
Nov 06, 2025, 06:11 PM UTC
Duration
9h 20m
Affected: System availability
Timeline · 4 updates
  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 →

Minor October 10, 2025

General Degraded Performance Across Sympa Platform

Detected by Pingoru
Oct 10, 2025, 05:57 AM UTC
Resolved
Oct 10, 2025, 06:59 AM UTC
Duration
1h 1m
Affected: System availability
Timeline · 2 updates
  1. monitoring Oct 10, 2025, 05:57 AM UTC

    Dear Customer, We are currently experiencing general degraded performance across the Sympa platform. Our team has identified increased slowness affecting multiple areas of the system and is actively monitoring the situation. We are working to ensure the performance stabilizes as soon as possible and will provide updates as we make progress. Best regards, Sympa Team

  2. resolved Oct 10, 2025, 06:59 AM UTC

    Dear Customer, The issue causing general slowness across the Sympa platform has now been fully resolved. Our team identified the cause and took corrective actions that have restored normal performance levels. We will still continue to monitor the system closely, but all services are now operating as expected. We apologize for any inconvenience this may have caused and thank you for your patience and understanding. Best regards, Sympa Team

Read the full incident report →

Minor August 26, 2025

Degraded performance - Errors might be visible to some users

Detected by Pingoru
Aug 26, 2025, 05:30 AM UTC
Resolved
Aug 26, 2025, 08:04 AM UTC
Duration
2h 33m
Affected: System availability
Timeline · 3 updates
  1. identified Aug 26, 2025, 05:30 AM UTC

    We have identified an issue at 26.Aug.2025 at 8:15 EEST 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. monitoring Aug 26, 2025, 05:54 AM UTC

    At 26 Aug 2025, 8:52 EEST a fix has been implemented and the system is operational. We're currently monitoring the results.

  3. resolved Aug 26, 2025, 08:04 AM UTC

    The incident has been resolved. There was network disruption between 06:00 - 08:37 that affected small portion of API calls, appearing as randomly failing requests and errors shown to the user.

Read the full incident report →

Major August 15, 2025

Identified issue with opening attachments in Sympa

Detected by Pingoru
Aug 15, 2025, 05:52 AM UTC
Resolved
Aug 15, 2025, 08:10 AM UTC
Duration
2h 18m
Affected: System availability
Timeline · 3 updates
  1. investigating Aug 15, 2025, 05:52 AM UTC

    Our team is currently investigating why attachments can not be downloaded neither previewed in Sympa. At the moment attachments under any person cannot be previewed neither downloaded.

  2. monitoring Aug 15, 2025, 06:52 AM UTC

    We want to inform you about a recent technical issue in our system that occurred between 14/08/2025 at 17:00 EEST and 15/08/2025 at 09:05 EEST. During this period, some attachments uploaded via the Sympa UI (e.g., over the user profile) may not have been saved correctly. The issue has been fully resolved, and the system is now operating normally. Only a limited number of customers were affected. We will contact all affected customers directly with further details and instructions. If you do not hear from us, no action is required on your part. We sincerely apologize for any inconvenience this incident may have caused and thank you for your understanding. Your Sympa Team

  3. resolved Aug 15, 2025, 08:10 AM UTC

    This incident has been resolved.

Read the full incident report →