Is Sympa HR down?
Last checked 6m agoNo incidents right now.
Sympa HR is operational right now. Last checked 6m ago; the most recent incident resolved 3d ago.
Real-time Sympa HR status, recent outages, and incident history — pulled directly from Sympa HR's official status page at https://sympa.statuspage.io every 5 minutes. Pingoru tracks 8 Sympa HR services and has captured 4 incidents in the last 90 days (99.58% uptime). Get email, Slack, Discord, or webhook alerts the moment Sympa HR reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Integrations
Timeline · 2 updates
- 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
- 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
Latest: 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 an…
-
- System availability
Timeline · 4 updates
- 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
- 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
- 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
- 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
Latest: **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 wer…
-
-
Timeline · 4 updates
- 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.
- 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
- 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
- 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
Latest: **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 …
-
- Started Sep 14, 2026, 06:25 AM UTC · Resolved Sep 14, 2026, 11:45 AM UTC · 5h 20m
- Login taking longer than usual ResolvedStarted Aug 31, 2026, 07:09 AM UTC · Resolved Aug 31, 2026, 09:36 AM UTC · 2h 27m
- Pages not visible ResolvedStarted Jul 15, 2026, 06:22 AM UTC · Resolved Jul 15, 2026, 01:52 PM UTC · 7h 30m