- Detected by Pingoru
- May 08, 2026, 12:55 PM UTC
- Resolved
- May 08, 2026, 07:11 PM UTC
- Duration
- 6h 15m
Affected: Integrations
Timeline · 3 updates
-
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
-
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
-
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
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 09:41 AM UTC
- Resolved
- Apr 29, 2026, 03:21 PM UTC
- Duration
- 5h 39m
Affected: System availability
Timeline · 3 updates
-
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
-
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
-
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
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 08:26 AM UTC
- Resolved
- Apr 24, 2026, 12:19 PM UTC
- Duration
- 3h 53m
Affected: System availability
Timeline · 4 updates
Read the full incident report →
- 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
-
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
-
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
-
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
-
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 →
- Detected by Pingoru
- Apr 10, 2026, 07:12 AM UTC
- Resolved
- Apr 10, 2026, 06:21 PM UTC
- Duration
- 11h 8m
Affected: ReportingIntegrationsEsign
Timeline · 5 updates
Read the full incident report →
- 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
-
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
-
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
-
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
-
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 →
- 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
-
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
-
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
-
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
-
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
-
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
-
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 →
- 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
-
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
-
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
-
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
-
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
-
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 →
- 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
-
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
-
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
-
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
-
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
-
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 →
- 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
-
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
-
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
-
identified Mar 09, 2026, 02:38 PM UTC
We are continuing to work on a fix for this issue.
-
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
-
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 - 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
-
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.
-
identified Feb 04, 2026, 02:05 PM UTC
We are continuing to work on a fix for this issue.
-
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.
-
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 →
- 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
-
investigating Jan 27, 2026, 07:37 AM UTC
We have noticed degraded performance in Sympa. We are currently investigating the root cause.
-
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
-
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 →
- 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
-
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.
-
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
-
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
-
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 - 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
-
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
-
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
-
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 →
- Detected by Pingoru
- Nov 19, 2025, 06:43 AM UTC
- Resolved
- Nov 21, 2025, 01:15 PM UTC
- Duration
- 2d 6h
Affected: System availability
Timeline · 6 updates
Read the full incident report →
- 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
-
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.
-
identified Nov 13, 2025, 04:42 PM UTC
We are continuing to work on a fix for this issue.
-
identified Nov 13, 2025, 05:01 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Nov 13, 2025, 05:02 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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
-
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.
-
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
-
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 →
- Detected by Pingoru
- Oct 29, 2025, 05:35 PM UTC
- Resolved
- Oct 30, 2025, 05:53 AM UTC
- Duration
- 12h 17m
Affected: System availabilityAuthenticationIntegrations
Timeline · 5 updates
Read the full incident report →
- 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
-
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
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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
-
resolved Aug 15, 2025, 08:10 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 08, 2025, 08:28 AM UTC
- Resolved
- Aug 08, 2025, 08:28 AM UTC
- Duration
- —
Affected: Integrations
Timeline · 1 update
-
resolved Aug 08, 2025, 08:28 AM UTC
We experienced an issue affecting file-based integrations, resulting in degraded functionality. Start time: 21:18 (07/08/2025) Resolved: 11:20 (08/08/2025) The problem has now been resolved. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding. If you have any questions or need further assistance, please don't hesitate to contact us.
Read the full incident report →
- Detected by Pingoru
- Jul 08, 2025, 07:07 AM UTC
- Resolved
- Jul 08, 2025, 07:25 AM UTC
- Duration
- 18m
Affected: System availability
Timeline · 2 updates
-
investigating Jul 08, 2025, 07:07 AM UTC
We are currently investigating an increased number of network errors affecting connections from users’ browsers to Sympa. Some users may experience difficulty accessing the service or notice intermittent connectivity issues. Our team is actively working to identify the root cause and resolve the issue as quickly as possible. We apologize for any inconvenience and appreciate your patience. Further updates will be posted here as soon as more information is available.
-
resolved Jul 08, 2025, 07:25 AM UTC
The issue causing network errors and intermittent connectivity for some users has been identified and resolved. The root cause was a broken certificate, which has now been replaced. All services are operating normally again. We sincerely apologize for the disruption and appreciate your patience while we worked to restore full functionality. If you continue to experience any issues, please reach out to our support team.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 08:37 AM UTC
- Resolved
- Jun 23, 2025, 12:56 PM UTC
- Duration
- 4h 19m
Affected: System availability
Timeline · 4 updates
-
investigating Jun 23, 2025, 08:37 AM UTC
There is currently heavy load in our systems and our team is investigating what's causing.
-
monitoring Jun 23, 2025, 08:41 AM UTC
Our team has found the reason behind the slowness and we're now monitoring the situation.
-
monitoring Jun 23, 2025, 09:27 AM UTC
Sympa Performance Notice We have identified performance issues in the Sympa system, which are linked to specific types of data imports affecting database performance. Our team is actively investigating the root cause to ensure a permanent resolution. As a precautionary measure, we have temporarily paused the affected data import processes to prevent further impact. We will provide updates as soon as more information becomes available or once the issue has been fully resolved. We apologize for any inconvenience this may cause and appreciate your patience and understanding. Please note, this is not affecting integrations.
-
resolved Jun 23, 2025, 12:56 PM UTC
System is working again normally.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2025, 12:09 PM UTC
- Resolved
- Jun 04, 2025, 05:42 PM UTC
- Duration
- 5h 32m
Affected: Knowledgebase
Timeline · 2 updates
-
identified Jun 04, 2025, 12:09 PM UTC
We have identified an issue with our Support Knowledgebase provider Hubspot that causes an error for some users when trying to login to the Knowledgebase. We will update you once the issue is solved.
-
resolved Jun 04, 2025, 05:42 PM UTC
The sign in page for knowledge base login was fixed and login into knowledge works again.
Read the full incident report →